The CA Chorus Application Server startup creates files and folders by unzipping the element bin/CHORDIR. The CA Chorus Application Server also creates a number of folders and files in <chorus_home>/jboss/standalone/tmp. If someone other than the CA Chorus administrator, for example: CHORADM, runs the CA Chorus Application Server, those files and folders will be owned by the person who ran the CA Chorus Application Server. Later, when starting the CA Chorus Application Server as a started task running under the CA Chorus admin ID, the CA Chorus Application Server will fail to start successfully. This is because of the exceptions that the permission problems cause. You will see errors such as follows:
To identify the permission problems, check the USS file permissions by running the following command in <chorus_home>:
ls -lR >chorusfiles.txt
To view files that do not have the owner of CHORADM, run the following command:
find <chorus_home> ! -user CHORADM | xaarqs ls -l
To resolve the permission problems, rerun ETJI0100. This action sets the ownership of the files back to CHORADM.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|