You use the Smart Composer functionality and server management commands to set up the batch application execution environment. The procedure for setting up the batch application execution environment is as follows:

1. Set up systems by using the Smart Composer functionality.
   You define the system configuration in the Easy Setup definition file and use the commands provided with the Smart Composer functionality to execute the batch setup of systems.
   
2. Set up resource adapters by using the server management commands.
   You implement this process only when connecting to a database from a batch application.
   

For details on the Smart Composer functionality and the server management commands, see 4.6 Setting up a system that executes batch applications in the uCosminexus Application Server System Setup and Operation Guide.

Note

If you want to set up multiple batch servers, you must perform changes in such a way so that the port number of TCP/IP, used with the server, is not duplicated. For the batch server also, you use the port number of TCP/IP that is being used with a J2EE server. If you want to concurrently start multiple batch servers, and concurrently start the batch server and the J2EE server, set up in such a way so that no duplicate port numbers are used. For details on the port numbers, see 3.16 Port numbers of TCP/UDP used by Application Server processes in the uCosminexus Application Server System Design Guide.

Reference note

You can also set up the batch application execution environment by using the management portal. For details on setting up the batch application execution environment by using the management portal, see 5. Setting up and deleting a system that executes batch applications in the uCosminexus Application Server Management Portal User Guide.

The procedure for operating the batch application execution environment is as follows:

1. Starting a system
   You use the commands provided with the Smart Composer functionality and start the entire system including the batch servers. You also start DB Connector, when connecting to resources from batch applications.
   
2. Executing a batch application
   Start a batch application by using the cjexecjob command.
   
3. Stopping a batch server
   You use the commands provided with the Smart Composer functionality and stop the entire system including the batch server.
   

   Reference note

   For details on starting and stopping the batch application execution environment by using the management portal, see 6.1. Starting and stopping a system in the uCosminexus Application Server Management Portal User Guide.

If you integrate a system with JP1/AJS, batch servers and batch applications can start from JP1/AJS. If you integrate the system with JP1/AJS, BJEX, and JP1/Advanced Shell, the batch servers can start from JP1/AJS and the batch applications can start from BJEX or JP1/Advanced Shell.

For details on starting and stopping the systems, see 2.6 Setting the start and stop of systems in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide. For details on how to start the batch applications, see 2.3.2 Executing batch applications.

You can use the following operation functionality with the systems executing batch applications:

(a) Functionality that support daily operations of systems

In addition to start and stop of systems, you can monitor the operation status and resource usage status of batch servers. This subsection gives an overview of the functionality used for supporting the daily operations of the systems.

• Monitoring statistics (statistics collection functionality)
  This functionality regularly monitors the operation status of batch servers and acquires statistics for server performance and resource information.
  
• Output statistics by using management commands
  This functionality monitors the logical servers in management domain and acquires statistics by using management commands.
  
• Monitoring resource exhaustion
  This functionality monitors the resources such as memory and threads with batch servers as the target. The information, related to the resources targeted for monitoring, is output to a file at regular intervals. An alert is generated if the status of resources, targeted for monitoring, exceeds the specified threshold. If an alert is generated, a message is output and the event is reported to Management Server.
  
• Reporting Management event and automatically executing a processing from Management action
  Management events can be issued by considering all the messages output when a batch application is running, as triggers. By defining the operations to be performed, when Management events are reported, on Management Server machine, actions are now automatically executed when Management events occur.
  
• Collecting statistics of CTM
  When using the functionality of scheduling batch applications, you can collect statistics output from CTM. You can analyze processing performance of CTM on the basis of this information.
  

For details on the functionality that support daily operations of the systems, see 1.2.1 Functionality that support daily operations of systems in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

(b) Functionality that support maintenance of systems

You can output the information of processes, started by Administration Agent, such as a batch server as console logs. This subsection gives an overview of console log output.

• Console log output
  You can output console output information such as standard output and standard error output of processes, started by Administration Agent, to the console log. For details on the console log output, see 11. Console log output in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.
  

You can output the logs of batch application as user logs. The user log output is one of the extended functionality. This subsection gives an overview of user log output.

• User log output
  If an exception occurs in a batch application, you can output message and log in the Hitachi Trace Common Library format. For details on user logs, see 9. Output of the user logs of applications.
  

(c) Functionality that support monitoring of a system

With this functionality you can output the history and the operations executed by the system architects and operators for programs of Application Server. You can also record the accounts used when a batch application accessed a database. This subsection given an overview of the functionality that supports the monitoring of systems.

• Output of audit logs
  You can output the operations performed by system architects and operators for the programs of Application Server and the history of program actions associated with the operations. You can use this information for monitoring the systems.
  
• Integrating with the database audit trail functionality
  By integrating a system with the database audit trail functionality provided by a database, you can record the accounts that are used when a batch application access the database.
  

For details on the functionality that supports the monitoring of systems, see the following chapters:

• 6. Audit log output functionality in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide
• 7. Database audit trail integration functionality in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide

(d) Functionality for maintaining a system

You can acquire troubleshooting data when a batch server detects an error. This subsection gives an overview of the functionality used for maintaining a system.

• Troubleshooting
  If you use a command during error detection, you can acquire troubleshooting data when Management Server detects the fault at the logical server. You can also output and collect the snapshot log of component software on Application Server.
  For example, if trouble occurs in a system, the snapshot log is automatically collected as troubleshooting information.
  
• Performance analysis of a system by using performance analysis trace
  The performance analysis trace is the functionality that collects performance analysis information output by the functionality of Application Server. You can analyze system performance and bottlenecks on the basis of this information.
  

For details on the functionality used for maintaining the systems, see the uCosminexus Application Server Maintenance and Migration Guide.

You can integrate the following programs with the systems executing batch applications:

• Integrating with JP1
• Integrating with cluster software

For details on the integration with JP1, see 12. Operations of a system integrated with JP1 in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide. For details on the integration with cluster software, see 16. Integrating with cluster software in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

(a) Overview of the management functionality by integrating with JP1

This subsection gives an overview of the management functionality by integrating with JP1.

• Centralized monitoring of systems (integrating with JP1/IM)
  By performing centralized monitoring of resource status of entire business system, you can understand and examine operation performance, detect trouble occurrences, determine causes, and take countermeasures. You can implement this functionality by integrating with JP1/IM.
  
• Automatically operating a system by using jobs (integrating with JP1/AJS)
  By defining and automating a schedule of starting and stopping servers and applications in advance, you can achieve efficient resource allocation, operation efficiency, and power saving. By integrating with JP1/AJS, you can implement automatic operations of systems by using custom jobs.
  
• Collecting and consolidating audit log (integrating with JP1/Audit Management - Manager)
  You can automatically collect the audit logs used for monitoring systems, and manage the logs in a batch. You can implement this functionality by integrating with JP1/Audit Management - Manager.
  

(b) Overview of node switching functionality by integrating with cluster software

This subsection gives an overview of the node switching functionality by integrating with cluster software. The cluster software that can be integrated is; Windows Server Failover Cluster^# (in Windows) and HA monitor (in AIX, HP-UX, and Linux). For Solaris, you cannot operate a system integrated with the cluster software.

#

You can use Windows Server 2012 and Windows Server 2008 as an OS.

• BASIC authentication
  This is a system configuration where executing node and standby node are set up in one-to-one ratio. In the case of the batch application execution environment, the BASIC authentication operations are supported on Application Server. When an error is detected on the executing node server or maintaining a system, this functionality is used for continuing the business processing by automatically switching to a server that is already kept in the standby state. As a result, you can decrease system downtime and impact on business processing of client.
  In the case of the batch application execution environment, you cannot use BASIC authentication of Management Server, because Management Server is not deployed.
  
• Mutual node switching system
  With the BASIC authentication configuration, two servers operate as active nodes and serve as spare nodes for each other. The operations of the mutual node switching systems on Application Server are supported.
  
• Node switching system that targets host unit management model
  This is a system configuration where N executing nodes and one spare node of the host unit management model are placed. The operations of node switching systems on Application Server of the host unit management model are supported.