This section describes how to check the behavior of each J2EE1.4 application in the Interstage Application Server J2EE container (IJServer).
To check the behavior of a J2EE application, deploy the J2EE application to the server, then start the server. These operations are performed in the Servers view. Check behavior by invoking the J2EE application from the client. Additionally, perform debugging to interrupt program execution and execute code one line at a time, or to check the value of variables.
Preparations for Operating Servers
To perform operations such as starting and stopping servers in the workbench, add the servers to be operated in the Servers view.
Adding Servers
Behavior check is performed when the Servers view that is the deployment destination of the application is added to the server. To add a server, use the New Server wizard. In the Servers view, from the context menu, select [New] > [Server]. The table below lists the wizard setup items:
Setup Items | Setup Content |
|---|---|
Server's host name | Name of the server host. If using a local machine, specify "localhost". |
Server type | Target version server type. For an Interstage V11 J2EE container, select [FUJITSU LIMITED] > [Interstage Application Server V11.1 IJServer (J2EE)]. |
Server name | The server name can be customized, but modifications made here are not reflected in Interstage Studio, and are in the following format. "IJServer name [server type name] (host name)" |
Server runtime environment | Runtime configuration corresponding to the server type. The server type and server runtime are associated one-to-one, therefore modification is not required. For an Interstage V11 J2EE container, select [Interstage Application Server V11.1 IJServer (J2EE)]. If the server runtime environment is not registered, then the [Server runtime environment] item is not displayed, and the [Interstage Application Server] page is displayed. The server runtime environment is automatically registered. Click the [Next] button. |
HTTPS is used for the connection to the management console | When the Interstage Management Console is displayed, select this if using SSL encoding communication. It must match the server settings. For the SSL encoding communication settings of the Interstage Management Console, "Select Operation Mode" can be selected during Interstage installation. |
Interstage Management Console Port Number | Interstage Management Console port number. Normally, modification is not required. The default port number is 12000. Modify to match the server environment. |
Interstage JMX ServicePort Number | Port number used by the Interstage JMX service to receive requests from the Interstage Management Console. The default port number is 12200. Modify to match the server environment. This item can be set when the host is remote. |
Login | Connects to the server. The states are already connected, or, when the button is clicked and login is successful, the button cannot be clicked. If the connection destination server is not 'localhost', then an authentication dialog box is displayed. Specify the user name and password. However, even in the case of the localhost, if the user does not have administrator permissions, an authentication dialog box will be displayed. Set a username and password with administrator permissions. |
User name | Username used in server connection. Application Server authentication is performed using the username specified here. Operations are restricted depending on the username used in authentication. For details on authentication and restricted operations, refer to "Interstage Application Server Operator's Guide". |
Password | Password used in authentication. |
IJServer Cluster | List of IJServer cluster defined in the connected server. Select the target IJServer cluster. |
HTTP Port Number | HTTP port number of the server. Modify to match the server environment. |
Add and Remove Projects | Project to be deployed to the server. A list of projects is displayed in [Available projects]. Add the project to be deployed to [Configured projects]. Projects can also be added from the context menu after the server is added. |
Note
The only type of IJServer on which Web service applications and EJB 2.1 applications can run is one on which the same Java VM runs EJB applications and Web applications.
If an old version server type is selected in [Server type], an Interstage Application Server client function with the version selected in [Server type] must be installed. Additionally, in the server to be connected, specify the server in the remote environment.
Associating Projects and Servers
The specifications of the project to be deployed to the server are performed by adding the project to the server of the Servers view. To add the project to be deployed to the server, use the Add and Remove Projects wizard. To start the Add and Remove Projects wizard, in the Servers view, select the server, then from the context menu, select [Add and Remove Projects].
The table below lists the dialog box setup items:
Setup Items | Setup Content |
|---|---|
Add and Remove Projects | Project to be deployed to the server. A list of projects is displayed in [Available projects]. Add the project to be deployed to [Configured projects]. |
Note
If applications that have already been deployed in a separate environment exist on the server, then the Servers view will display the module name, instead of the project name. If applications that have already been deployed exist, and those projects are imported and deployed, in the Servers view, both "Project name" and "Module name" will be displayed. However, modules deployed to APS are recognized as one application.
Starting Servers
In the Servers view, select the server, then from the context menu, select [Start] or [Debug].The application can be set to deploy automatically when the server starts.
Point
If a connection to the IJServer cluster has not been made yet, in the Servers view, nothing will display in the IJServer cluster [State] field, and operations such as start and stop cannot be performed. In such cases, in the Servers view, select that IJServer cluster, then from the context menu, select [Connect/Login] to connect to the IJServer cluster.
To stop a server, in the Servers view, select the server, then from the toolbar, select [Stop].
Note
If the Interstage Management Service of the server is stopped while connected to the IJServer cluster, connection to the IJServer cluster will be interrupted, causing failure of operations of the IJServer cluster in the Servers view. If operations fail, in the Servers view, select IJServer cluster, and from the context menu, select [Refresh]. After updating the status of the IJServer cluster, from the context menu, select [Connect/Login] to reconnect to the IJServer cluster.
Executing Applications
To check the behavior of the J2EE application deployed to the server, execute a client application that invokes the J2EE application.
In the case of a Web application, the client application starts a Web browser, and checks the behavior by accessing the URL of the application.
Point
In the case of a Web project, in the Servers view, select the deploying Web project, then from the context menu, select [Web browser] to start the Web browser with the URL internally structured.
Debugging Applications
To debug applications, in the Servers view, select the server, then from the context menu, select [Debug]. To perform debugging, set a breakpoint, interrupt the started program, and then execute code one line at a time, and check the content of variables.
For details on debugging, refer to "6.2.6.1 Debugging".
