When you set up a system without using Management Server, to use CTM in the system, you must create the execution-environment directories for CTM and the performance tracer, and then specify them for environment variables.

For details about creating execution-environment directories and specifying environment variables, see Appendix H. System Environment Variables in the uCosminexus Application Server Command Reference Guide.

Note that if you use Management Server to set up a system, you do not need to set the environment variables for using CTM.

Note

In AIX, note the following points when setting environment variables:

• In the execution environment for Component Transaction Monitor, set early for the PSALLOC environment variable. If you do not set early, correct operation cannot be guaranteed when memory becomes insufficient.
• The PSALLOC environment variable, which specifies early paging space allocation mode in AIX, is set to early. In this mode, paging space estimation needs to be considered. For details, see System Management Concepts: Operating System and Devices, which is documentation for AIX.
• In the execution environment for Component Transaction Monitor, set true for the NODISCLAIM environment variable. If PSALLOC is early, NODISCLAIM must be true. If you do not set true, the response, throughput, and CPU usage rate might be severely degraded.
• To expand the user data area and shared memory area used by Component Transaction Monitor, set MAXDATA=0x40000000 for the LDR_CNTRL environment variable. Then, specify 1 GB as the size of memory to be allocated.
• In the execution environment for Component Transaction Monitor, set ON for the EXTSHM environment variable. If you do not set ON, shared memory might not be accessible.

To schedule requests by using CTM, in the Easy Setup definition file, set the properties shown below in the <configuration> element for the logical J2EE server (j2ee-server). For details about the Easy Setup definition file, see 4.6 Easy Setup definition file in the uCosminexus Application Server Definition Reference Guide.

• ejbserver.ctm.ActivateTimeOut
  Specifies the time for which the J2EE server can wait before the schedule queue is activated at startup of the J2EE application that uses CTM.
  
• ejbserver.ctm.DeactivateTimeOut
  Specifies the time for which the J2EE server can wait before the schedule queue is de-activated (before requests being executed are completed) at termination of the J2EE application that uses CTM.
  
• ejbserver.ctm.QueueLength
  Specifies the length of the CTM queue generated by the J2EE server at startup of the J2EE application that uses CTM.
  
• ejbserver.client.ctm.RequestPriority
  Specifies the priority level of requests that the J2EE server sends to CTM.
  

This subsection describes the settings that can be specified by using server management commands. For details about operations that can be performed by using server management commands, see Chapter 3. Basic Operations of Server Management Commands in the uCosminexus Application Server Application Setup Guide.

• Settings for each J2EE application
  You use the application properties file to specify the following settings:
  
  • The <managed-by-ctm> element can be used to set whether to use CTM.
  • The <scheduling> element can be used to set the name, length, and other attributes of the schedule queue.
  • The <scheduling-unit> element can be used to select the schedule queue deployment basis (on a J2EE application basis or bean basis).
• Settings for each stateless session bean
  You use the session bean properties file to specify the following settings:
  
  • The <enable-scheduling> element can be used to specify the scheduling-target stateless session bean included in the J2EE application.
  • The <maximum> or <minimum> element in the <pooled-instance> element in the <stateless> element can be used to set the maximum or minimum number of instances to be pooled. Note that to dynamically change the degree of parallelism of CTM during operation, you must set 0 (indefinite) as the maximum.
  • The <scheduling> element can be used to set the name, length, and other attributes of the schedule queue.

After you use the cjgetappprop command to obtain a properties file, edit the file, and then use the cjsetappprop command to apply the new contents to the J2EE applications.