
After you have successfully generated the CallbackApplication.ear file, you must deploy the application to the J2EE Engine. You do this in two phases:
We recommend that you deploy the CallbackApplication to an J2EE Engine installation that is used as a development environment rather than as a productive system.
Deploying the CallbackApplication to J2EE Engine Running on a Remote Host
To do this, you must first set up the SAP NetWeaver Developer Studio to use a particular installation of the J2EE Engine:
| Field Name | Information to Enter |
|---|---|
|
Message Server Host |
The IP address or the hostname of the host the message server instance of your J2EE Engine instance is running. |
|
Message Server Port |
The port number the message server listens to. The default one is 3601. |
Now, you can go on and deploy the CallbackApplication to the J2EE Engine instance that you have just set up.
When the deployment process finishes, you will see a success message on the screen. This means the CallbackApplication is deployed on the J2EE Engine. It is automatically started after deployment.
Generating IIOP Support for the CallbackApplication
During the update process, the EJB Container first stops the application, and after the update is completed, it starts it again.
At the end of this procedure, you have the CallbackApplication deployed on the J2EE Engine with the required IIOP communication support. Now you can develop a remote client application that can call methods of the UtilCallback bean from the CallbackApplication application.