6.2.1 Preparing the Deployment Destination for Verifying Application Operation

There are two deployment destinations that verify application operation: IJServer Cluster and the Interstage Java EE DAS service. The advantages of each are explained below, and notes are provided. Perform operation verification at the deployment destination that suits your environment and requirements.

Note

The use of both IJServer Cluster and the Interstage Java EE DAS service for operation verification is not recommended because care is required as indicated below. Use one or the other to perform operation verification.

The Interstage Java EE DAS service is a mandatory service for launching IJServer Cluster. Therefore, operations such as stopping and restarting the Interstage Java EE DAS service also affect IJServer Cluster operation.

IJServer Cluster advantages
- Operation verification can be performed from a remote machine and under conditions that closely match the operating environment.
- If the Interstage Management Service has not been started, a user account control dialog box is displayed to start the service when operation is first attempted, but is not displayed for subsequent operations.

Note

To use IJServer Cluster, refer to "6.2.1.1 Creating an IJServer Cluster (MyDebugJEE)" and create an IJServer Cluster.

Interstage Java EE DAS service advantages
- If the Interstage Application Server functions are installed, the Interstage Java EE DAS service is already created so, unlike IJServer Cluster, no work is required to create it.
- Operation can be verified with reduced memory usage because the Interstage Java EE Node Agent service and IJServer Cluster need not be launched.

Note

The functions of the operating system being used display the user account control dialog box at the time of server view operations such as [Connect(Debug Launch)/Login], [Connect/Login], and [Stop].
Operation cannot be verified using the Interstage Java EE DAS service of a remote machine.
If using the Interstage Java EE DAS service, select "server" when selecting an IJServer Cluster.

The Interstage Java EE Admin Console is usually used to create IJServer Clusters. However, an IJServer Cluster to be used for debugging can be created by executing the command shown below. Refer to the "Interstage Application Server Java EE Operator's Guide" for details.

asadmin create-cluster --newinstances MyDebugJEEInstance --user %Admin_User% --passwordfile %File_Name% MyDebugJEE

For details on the variable information, see below.

Variable Information	Description
%Admin_User%	Specify the admin user ID name.
%File_Name%	Specify the file where the admin password was described. "/" or "\\" characters can be used as the file path separator of the password file Example: c:/password.txt The format of the password file is as follows: AS_ADMIN_PASSWORD=password

Variable Information

Description

%Admin_User%

Specify the admin user ID name.

%File_Name%

Specify the file where the admin password was described.

"/" or "\\" characters can be used as the file path separator of the password file
Example: c:/password.txt
The format of the password file is as follows:
AS_ADMIN_PASSWORD=password

Note

To execute commands, the following is required:

A path must be set to the "bin" folder under the "F3FMisjee" folder of the Interstage Application Server folder.
Example: c:\Interstage\APS\F3FMisjee\bin
Interstage Management Service must be started.