4.3.4 Notes on the definitions of linkage job information

(1) About definitions used for job execution

The service linkage job definitions, service linkage monitoring job definitions, and authentication definitions defined in JP1/AJS3 for Cloud Service Applications are used by JP1/AJS3 as service linkage jobs or service linkage monitoring jobs in JP1/AJS3. Therefore, job execution of JP1/AJS3 may be affected if the definition of service linkage job information or service linkage monitoring job information is updated or deleted.

Whether or not the job execution of JP1/AJS3 is affected is displayed on the Web screen of JP1/AJS3 for Cloud Service Applications as follows.

• When updating or deleting the service linkage job definition, service linkage monitoring job definition, or authentication definition used for a job that has once been executed, the message KNBB2407-Q or KNBB2408-Q is displayed in a dialog.

• When editing each definition on the Web screen of the JP1/AJS3 for Cloud Service Applications, the upper part of the screen shows a message !This is a definition that has a job execution history.

Note that the period of time when such dialog or message is displayed depends on the value specified for USED_DEF_LIMIT in the environment setting file. For details on the environment setting file, see 3.4.1 Details of setting items of the environment setting file (ajs3csaweb.conf).

For service linkage monitoring jobs, note that:

• Regarding authentication definition, the history information will be updated after the monitoring starts or when the monitoring processing runs for each monitoring interval. Therefore, the timing for displaying a message is different from other definitions.

In addition, when creating new service-linkage job definitions, service-linkage monitoring job definitions, or authentication definitions, if you perform registration by using a definition name that has previously been executed, even if the job has not executed even once, the aforementioned display processing is performed.

To check the details of a user's job in JP1/AJS3, use one of the following methods:

• Check the unit name and host name of the job by referencing server job logs of JP1/AJS3 for Cloud Service Applications. For details about server job logs, see 9.2.4 Server Job Logs.

• From the content of the unit definitions output by the ajsprint command or by JP1/AJS3 - Definition Assistant in JP1/AJS3, search for and check the service linkage jobs or service linkage monitoring jobs. For details about unit definition parameters, see 4.5 Unit definition parameters of service linkage jobs and 4.6 Unit definition parameters of service linkage monitoring jobs. For details about how to check the name of service linkage jobs and service linkage monitoring jobs, see the description of the ajscsajoblist (Windows only) in 8. Commands.

To Page Top

(2) About definitions used in the service linkage job definitions

For service linkage job definitions, the connection definition and execution definition are specified to execute a job as the service linkage job. Therefore, job execution of JP1/AJS3 may be affected if the connection definition and execution definition are updated or deleted.

Whether or not the service linkage job definitions are affected is shown on the Web screen of JP1/AJS3 for Cloud Service Applications as follows.

• When updating or deleting the connection definition or execution definition used for the service linkage job definitions, the message KNBB2409-Q or KNBB2410-Q is displayed in a dialog.

• When you edit a connection definition on the Web screen of the JP1/AJS3 for Cloud Service Applications, the upper part of the screen shows a message stating !This is the definition used in the service linkage job definition or the service linkage monitoring job definition. When you edit an execution definition, it shows a message stating !This is the definition used in the service linkage job definition.

To Page Top

(3) About definitions used in the service linkage monitoring job definitions

For service linkage monitoring job definitions, the connection definition and monitoring definition are specified to execute a job as the service linkage job. Therefore, job execution of JP1/AJS3 may be affected if the connection definition and monitoring definition are updated or deleted.

Whether or not the service linkage monitoring job definitions are affected is shown on the Web screen of JP1/AJS3 for Cloud Service Applications as follows.

• When updating or deleting the connection definition or monitoring definition used for the service linkage monitoring job definitions, the message KNBB2409-Q or KNBB2410-Q is displayed in a dialog.

• When you edit a connection definition on the Web screen of the JP1/AJS3 for Cloud Service Applications, the upper part of the screen shows a message stating !This is the definition used in the service linkage job definition or the service linkage monitoring job definition. When you edit an monitoring definition, it shows a message stating !This is the definition used in the service linkage monitoring job definition.

To Page Top

(4) About handling of authentication information

Information that is registered with Protect specified in the authentication definitions is stored in the database file (AJSCSA.db) and backup file (AJSCSA.db.back) in the data directory in a non-plain-text, protected state.

No authentication information is output to a log file, the standard output or standard error output of a job, nor the detailed execution results screen of JP1/AJS3 - View and JP1/AJS3 - Web Console.

Consider the notes below while taking into account the operations above when building an environment and designing security measures.

• Communication is performed by using protected non-plain-text information. However, authentication information is included in communication data. For this reason, we recommend that you build an SSL communication environment, unless your environment has no security risks, such as the risk of data being read on the communication path.

• JP1/AJS3 for Cloud Service Applications does not output protected authentication information to the standard output, standard error output, logs, and the detailed execution results screen of JP1/AJS3 - View and JP1/AJS3 - Web Console, but may output authentication information to the command line used for definition. Before specifying definitions, check and verify the specifications of the command lines to be used.

To Page Top

(5) Other notes

• To check with the changed service linkage job information about whether the job has been executed, take either of the following methods.

  • Open the service linkage job log file on the job execution host, and check if the command line with changed details has been output on the CLI.

  • When details have been changed in the standard error output or standard output of the service linkage job, check the execution result details check screen of JP1/AJS3 - View and JP1/AJS3 - Web Console or the data in the standard output file.

• To check with the changed service linkage monitoring job information about whether the job has been executed, take either of the following methods.

  • Open the log file for a monitoring job on the job execution host, and check if the command line with changed details has been output on the CLI.

  • When execution result setting details have been changed on a service linkage monitoring job, check the execution result details check screen of JP1/AJS3 - View and JP1/AJS3 - Web Console.

To Page Top