Installing the application

Installing the application project module is the last step of the deployment process. When you install the application and start it, the adapter, which is embedded in the project module, starts as part of the installed application.

Why and when to perform this task

Perform the following steps to install the application.

Steps for this task

  1. Before you install the application, you must create an authentication alias for use with your SAP instance. Once an authentication alias has been created, other SAP application project modules may use it as well.
    1. In the administrative console, click Security > Global security.
    2. On the right-side, under Authentication, click JAAS Configuration > J2C Authentication data.
    3. If an alias named SAP_Auth_Alias does not already exist, create it now.
    4. Click New. The General properties window appears.
    5. In the Alias field, specify SAP_Auth_Alias.
    6. Specify the userID and password for connecting to SAP.
    7. Click OK.
    8. Click Save.
  2. To begin the installation process, click Applications > Install New Applications.
  3. Under Path to the new application, specify the path of the EAR file, then click Next.
  4. Continue to click Next through the various Step windows, until you reach the window titled with the step Map resource reference to resources.
  5. Under Specify authentication method:
    1. Select the authentication alias you created earlier.
    2. Select the check box for the module.
    3. Click Apply.
  6. Click Next. The Application Resource Warnings window appears.
  7. Click Continue. The Install New Application window appears.
  8. Click Next. The Ensure all unprotected 2.x methods have the correct level of protection window appears.
  9. Click Next. A summary of all the installation options appears. Verify that all options are as you intended.
  10. Click Finish.
  11. A list of installation messages appears. Confirm that the message Application installed successfully is included at the end of the list.
  12. Click the Save to Master Configuration link that appears at the end of the list of installation messages. The Enterprise Applications window appears.
  13. Click Save to save the application. The application is now deployed and the Enterprise Applications window for the deployed application appears.
  14. If the application is an inbound application, edit the J2C activation specification (ActivationSpec) properties. If the application is an outbound application, edit the J2C connection factory properties:
    1. Click the deployed application and on the right-side column, under Related Items, click Connector Module. The Enterprise Application > Name of Application > Connector Modules window appears.
    2. Click the name of the RAR file. The Enterprise Application > Name of Application > Connector Modules > Name of RAR file window appears.
    3. Under Additional properties, click Resource adapter.
    4. For inbound applications: Click J2C Activation specifications under Additional properties. For outbound applications, click J2C connection factories under Additional properties
    5. For outbound applications: Click the factory instance created with the JNDI name specified in the EJB project.
    6. Under Additional properties, click Custom Properties.
    7. Update the desired property values.
    8. For inbound applications only: Select the Password property you want to update, enter the password in the Value field, and click OK.
    9. For inbound applications only: Click the > button to navigate to the next page and click the userName link.
    10. For inbound applications only: Enter the username in the Value field and click OK.
    11. Click the Save link in the Messages box at the top of the window.
  15. Click the Save button to save the edits.

What to do next

The application is now deployed and properly configured. The next step is to start the application.

Related reference
J2C activation specification properties
J2C connection factory properties

Terms of use |

Last updated: Sun Mar 12 11:15:16 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)