4.1.4 Notes on setting Component Container administrator (For UNIX)

Note that after setting Component Container Administrator, the super user cannot perform the same operations, except for a few that can be implemented by Component Container Administrator.

The following table describes the operations that can be implemented by the super user and Component Container Administrator when Component Container Administrator is set.

Table 4‒4: Operations that can be implemented on setting Component Container Administrator.

Operation	Super user	Component Container Administrator
Installing Cosminexus Component Container	Y	N
Setting up Component Container Administrator (cjenvsetup command)	Y	N
Migrating the work directory and the user definition file (cjenvupdate command, cjrarupdate command)	N	Y
Setting up/Unsetting the J2EE server or batch server (cjsetup command)	N	Y
Starting/Stopping the J2EE server or batch server (cjstartsv command, cjstopsv command)	N	Y
Executing the server management commands	Y	Y
Acquiring the thread dump (cjdumpsv command)	Y	Y
Acquiring OS status information (cjgetsysinfo command)	Y	Y
Executing the batch application (cjexecjob command)#	Y	Y
Forced termination of the batch application (cjkilljob command)#	Y	Y
Display the batch application information list (cjlistjob command)#	Y	Y

When you do not set a Component Container Administrator, the super user becomes the Administrator and performs the operations of Component Container Administrator as well.

Reference note

There is no effect on the execution of a management command even if Component Container Administrator is set.

You can execute the operations and commands during system operation with the Management user ID set during the Management Server setup.

Notes on the settings of Component Container Administrator and operations of Component Container Administrator are as follows:

• Component Container Administrator Account

  You can register only one Component Container Administrator account on the host for installing Cosminexus Component Container, and therefore you cannot register multiple accounts as Component Container Administrators. You can use only the account for logging in the OS as the account to be used as Component Container Administrator.

• Server to be managed by Component Container Administrator

  Component Container Administrator is the owner of not only the J2EE Server and batch server that is setup with the cjsetup command; but also the server of the host name setup by default during installation. You cannot set up a separate Component Container Administrator for each server.

• Changing port number during operations by Component Container Administrator.

  For starting CORBA naming service with Component Container Administrator (including starting in-process), change the port number settings using the Easy Setup definition file. You must set a value of 1,024 or higher for the port number in the ejbserver.naming.port parameter inside the <configuration> tag for the logical J2EE server (j2ee-server). When starting the CORBA naming service with the default port number (900) or a port number from 0 to 1,023, manually start the CORBA naming service by super user.

  Note that Component Container Administrators without the root permission cannot open the port numbers of 0 to 1,023. Therefore, when you are setting Component Container Administrator, and then operating, change also the port number other than CORBA naming service to 1,024 or above.

• Changing the attributes of the Component Container installation directory

  When you change the attributes (owner/ group) of the Component Container installation directory, do not operate the server (setup/ un-setup, and start or stop) until the execution of the Component Container Administrator setup command is complete.

• Changing Component Container Administrator

  When Component Container Administrator is set, the same user becomes Component Container Administrator even after an update installation. When you want to change Component Container Administrator, change the owner and the group of the installation directory (/opt/Cosminexus/CC) of Cosminexus Component Container, and then set up Component Container Administrator.

  Use the same method when you want to restore Component Container Administrator to the super user.

• Changing owner of directory and file

  You can change and use the following directory in the <configuration> tag of the logical J2EE server (j2ee-server) of the Easy Setup definition file.

  Changeable directory	How to specify
  Output destination directory for the JavaVM log of the product (called JavaVM hereafter)	Specify JavaVM starting parameters. Specification details of the JavaVM starting parameters are as follows: <param-name>tag add.jvm.arg <param-value>tag -XX:HitachiJavaLog:Directory name
  Log output directory of the J2EE server or the batch server	Specify in ejb.server.log.directory parameter.
  Temporary directory for JSP	Specify in Web Server.work.directory parameter.
  Trace output destination directory of Cosminexus TPBroker	Specify in vbroker.orb.htc.tracePath parameter.
  Output destination directory for operation information files	Specify in ejbserver.management.stats_file.dir parameter.

  If you are changing, and then using the directories, execute either of the following after setting up Component Container Administrator.

  • Change the owner of each directory and file to Component Container Administrator.

  • Set the writing permission for Component Container Administrator in each directory and file.

• Property of a directory when Component Container Administrator is set

  When Component Container Administrator is set, the property (owner/group) of the subdirectory and file under the following directory changes to Component Container Administrator/Component Container Administrator group.

  • /opt/Cosminexus/CC

  • Work directory/ejb/

  • Work directory/web/

  Note that the property of certain files under /opt/Cosminexus/CC (such as /opt/Cosminexus/CC/server/bin/cjenvsetup, /opt/Cosminexus/CC/server/bin/cjgetsysinfo and install log) do not change.

• Setting access permission for the log output destination directory of EJB client application

  When Component Container Administrator is set, the property (owner/group) of the file and directory under the installation directory (/opt/Cosminexus/CC) of Cosminexus Component Container change to Component Container Administrator /Component Container Administrator group. Therefore, default /opt/Cosminexus/CC/client/logs are used in the log output destination of EJB client application, and when the account of the executing user of Component Container Administrator and EJB client application differ, errors might occur in the log output of EJB client application. In such cases, set the mode of the log file output to the log output destination directory, such as to allow writing to a group or all other users. For details on setting access permissions, see 3.8.5 Setting access permission of the log output destination directory in the uCosminexus Application Server EJB Container Functionality Guide.

• Setting the access permissions for the Management Agent log file

  Management Agent outputs log files with the following name in the /opt/Cosminexus/manager/log directory:

  • mngagent-domain-name-Agent-name.[n].log

    Note: In the [n] part of the file name, a serial number is allocated from 1 to the specified number of log files.

  After you set up Component Container Administrator, execute one of the following operations:

  • Change the log file owner to Component Container Administrator.

  • Set the write permission for Component Container Administrator in the log file.

• Message when Component Container Administrator is set

  When Component Container Administrator is set and you want to import applications and various resources, the following message might be output if there is no read permission for the files to be imported. In such cases, check the access permission of the files to be imported.

  When the setting of the access permission is invalid, KDJE37324-E is output in the message.

• Setting up the J2EE servers or batch servers when Component Container Administrator is set up

  When Component Container Administrator is set up, do not set up a J2EE server or batch server with the same name as the server name of Management Server. Note that Component Container sets up the J2EE server or batch server using the host name during installation, so do not set up the server name of Management Server in the host name.

  The execution information for the Component Container Administrator setup (cjenvsetup command) is output to the message log and the text file. The following table describes the output contents and the output destination of the execution information.

  Table 4‒5: List of output contents and output destinations of the execution information for the Component Container Administrator setup (cjenvsetup command)

  Command execution information	Output contents	Output destination file name#1
  Command execution message	The following messages are output: KDJE40074-I KDJE40040-I (if normal) KDJE40041-E (if error)	cjenvsetupmessage*.log
  File (directory) information before change	List of files (directories)#2 subject to change of owner before the command is implemented#3.	before_cjenvsetup_files*.txt
  File (directory) information after change	List of files (directories)#2 subject to change of owner after the command is implemented#3. Note that if an error occurs, the results are output during the process of error occurrence (when the command ends).	after_cjenvsetup_files*.txt

#1

The output directory is Component-Container-installation-directory/logs/.

#2

The files (directories) subject to change of owner are all the files beneath Component-Container-installation-directory, beneath work-directory/ejb, and beneath work-directory/web. Note that if the link destination of the symbolic link file is a directory, the files beneath the symbolic link destination directory are also subject to change of owner.

#3

The time at which the file (directory) list is output appears on the first line and the list of files (directories) is output on the second and subsequent lines. An example of output is as follows:

Mon Dec 10 12:00:00 JST 2012 <- Time at which file (directory) list is output
/opt/Cosminexus/CC: <- List of files (directories)
 total 16
drwxr-xr-x 2 0 0 256 Dec 10 11:00 adapters
drwxr-xr-x 2 0 0 256 Dec 10 11:00 admin
 ...
 ...
 ...

Note that the format of the file (directory) list information varies as per the OS version and settings.

To Page Top