- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- CSWS_JAVA standalone doesn't define environment
Operating System - OpenVMS
1753902
Members
9290
Online
108810
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2011 11:41 AM
тАО01-06-2011 11:41 AM
CSWS_JAVA standalone doesn't define environment
So I did an install a couple of months back of CSWS along with CSWS_JAVA (Apache & Tomcat). Everything works fine. However, I don't use any of the features in CSWS (Apache) and only need the Tomcat container.
So on a new machine, I tried to install CSWS_JAVA by itself. It runs just fine (startup, shutdown, etc) but the tomcat install doesn't create any of the directory shortcuts that are used by the system such as apache$root, apache$common, etc. Thus, no log files get created either since they are written to apache$root:[000000]. Am I going to have to install CSWS on top of CSWS_JAVA to get this capability?
So on a new machine, I tried to install CSWS_JAVA by itself. It runs just fine (startup, shutdown, etc) but the tomcat install doesn't create any of the directory shortcuts that are used by the system such as apache$root, apache$common, etc. Thus, no log files get created either since they are written to apache$root:[000000]. Am I going to have to install CSWS on top of CSWS_JAVA to get this capability?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2011 12:44 PM
тАО01-06-2011 12:44 PM
Re: CSWS_JAVA standalone doesn't define environment
Some additional information... log files do get created, but they are being created under sys$sysroot:[sysmgr]
Where in tomcat can I change this? In a windows tomcat install logs go under $catalina_home/logs, but this is not the case in openvms. I'd like to set it up to work this way if possible.
Where in tomcat can I change this? In a windows tomcat install logs go under $catalina_home/logs, but this is not the case in openvms. I'd like to set it up to work this way if possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2011 07:26 AM
тАО01-07-2011 07:26 AM
Re: CSWS_JAVA standalone doesn't define environment
So I discovered that in OpenVMS, CSWS_JAVA/Tomcat uses the user's default login directory as the location of its log files. Since I was using the SYSTEM account, it was placing the logs under sys$sysroot:[sysmgr].
The documentation says you only need the apache$www user if you want to share data between CSWS (Apache) and CSWS_JAVA (Tomcat), so I didn't create it. Yet when patching CSWS_JAVA it specifically looks for the user APACHE$WWW (it will show parsing error messages during the "Product install CSWS_JAVA301_UPDATE".
So before the installation of CSWS_JAVA and patching CSWS_JAVA301_UPDATE, i created a user account apache$www with a default directory of sys$common:[apache] and changed the permissions of tomcat using option [1] under the @sys$manager:apache$jakarta tool like you would if you would use Tomcat along with Apache web server after installing the base CSWS_JAVA install. Then when I patched to CSWS_JAVA301_UPDATE, there were no parsing errors, and upon startup, i could see logs under the sys$common:[apache] folder.
The documentation says you only need the apache$www user if you want to share data between CSWS (Apache) and CSWS_JAVA (Tomcat), so I didn't create it. Yet when patching CSWS_JAVA it specifically looks for the user APACHE$WWW (it will show parsing error messages during the "Product install CSWS_JAVA301_UPDATE".
So before the installation of CSWS_JAVA and patching CSWS_JAVA301_UPDATE, i created a user account apache$www with a default directory of sys$common:[apache] and changed the permissions of tomcat using option [1] under the @sys$manager:apache$jakarta tool like you would if you would use Tomcat along with Apache web server after installing the base CSWS_JAVA install. Then when I patched to CSWS_JAVA301_UPDATE, there were no parsing errors, and upon startup, i could see logs under the sys$common:[apache] folder.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP