Step 16: Deploying the web application on WebSphere

Overview

To deploy the web application, you must:

• Deploy the EAR file
• Configure the web application
• Configure SSL access

Deploying the EAR file

WebSphere 6.1

Add and deploy the new EBICS Server on the WebSphere Application Server as follows:

1. Open a session in the WebSphere Administration Console using the credentials admin/start.
2. Navigate to Applications > Install New Application.
3. In the Path to the new application menu, select the full path to the bankrechner.ear file from your local file system or from the remote file system, depending on where it is located. Example of path to the EAR file: <EBICS Server installation directory>/data/deploy/<EBICSServer_EAR_file.ear>.
4. Click Next.
5. In the Select installation options screen, set the following parameters:
   • Distribute application: Select this option
   • Deploy enterprise beans: Select this option
   • Application name: Enter AxwayEbicsServer
   • Create MBeans for resources: Select this option
   • Allow EJB reference targets to resolve automatically: Select this option
6. Click Next.
7. Click Next.
8. Click Finish.
9. The IBM WebSphere Application processes the modifications.
9. Once the changes have been made successfully, click Save.
10. Go to the section: Configuring the web application.

WebSphere 8.0

Add and deploy the new EBICS Server on the WebSphere Application Server as follows:

1. Open a session in the WebSphere Administration Console using the credentials admin/start.
2. Navigate to Applications > Install New Application.
3. Select the WebSphere Enterprise Application.
4. In the Path to the new application menu, select the full path to the bankrechner.ear file from your local file system or from the remote file system, depending on where it is located. Example of path to the EAR file: <EBICS Server installation directory>/data/deploy/<EBICSServer_EAR_file.ear>.
5. Click Next.
6. Select Fast Path and click Next.
7. In the Select installation options screen, set the following parameters:
   • Distribute application: Select this option
   • Deploy enterprise beans: Select this option
   • Application name: Enter AxwayEbicsServer
   • Create MBeans for resources: Select this option
   • Allow EJB reference targets to resolve automatically: Select this option
8. Map modules to Servers: Click Next.
9. Map virtual hosts for Web Modules: Click Next.
10. Metadata for modules : Click Next.
11. Summary: click Finish
12. The IBM WebSphere Application processes the modifications.
12. Once the changes have been made successfully, click Save.

Configuring the web application

1. Open a session in the WebSphere Administration Console using the credentials admin/start.
2. Navigate to Applications > Enterprise Applications.
3. Click the AxwayEbicsServer application.
4. In the Detail Properties section, click Class loading and update detection.
5. In the Class loader order section, select the option:
   WebSphere 6.1: Classes loaded with application class loader first, or
   WebSphere 8.0: Classes loaded with local class loader first.
6. For WAR class loader policy, set Single class loader for application.
7. Set WAR class loader policy to Single class loader for application.
8. Click OK and then Save.
9. In the Modules / Manage Modules section, for each of the following modules:
   
   • Bankrechner Admin
   • BL-Bankrechner Startup
   • BL-Bankrechner Web Connector
10. Perform the following operations:
    • Select the module
    • Change the Class loader order from Classes loaded with parent class loader first to:
      WebSphere 6.1: Classes loaded with application class loader first, or
      WebSphere 8.0: Classes loaded with local class loader first (parent last).
    • Click OK and then click Save
10. In the Detail properties / Security role to user / group mapping section:
    • Click Select all items to select all roles.
    • WebSphere 6.1: For each role, select the option All Authenticated ?, or
      WebSphere 8.0: From the drop-down menu, select Map Special Subjects and choose All Authenticated in Application’s Realm.
    • Click OK and then click Save.
11. This step enables all WebSphere registered users to connect to the Axway EBICS Server administration tool with full privileges. To manage user access by roles and groups, see Creating WebSphere user lists.
11. For WebSphere 8.0: From Applications > Application types > Websphere enterprise applications -> AxwayEbicsServer -> JSP and JSF Options For JSF Implementation, select the drop-down value SunRI 1.2 (Sun Reference Implementation 1.2).

Configuring the web Server

1. From the main menu, navigate to:
   WebSphere 6.1: Servers >Application Servers > server1, or
   WebSphere 8.0: Servers > Server Types > WebSphere application servers > server1
2. In the Server Infrastructure section, select Java and Process Management > Process Definition.
3. WebSphere 6.1: Click Java Virtual Machine and select the Configuration tab, or
   WebSphere 8.0: Go to Additional Properties > java Virtual Machine > Configuration tab.
4. Set the following values:
   • Set Initial Heap Size to 512 (minimum value)
   • Set Maximum Heap Size to 1024 (minimum value)
5. Click Custom Properties and then click New.
6. Create and set the value of the following variables:
   • bankrechner.dataDir: directory that contains the persistent data of the EBICS Server. If this directory does not exist, create it manually: <EBICS Server installation directory>/data/dataDir
   • dataStorePath: path of the repository (<EBICS Server installation directory>/data/dataStore)
   • configurationPath: absolute path of the configuration.properties file (<EBICS Server installation directory>/data/conf/configuration.properties)
   • de.businesslogics.bankrechner.bank.ebicsKeyMode: default security format to be used for banks, possible values are SELF_SIGNED_CERTIFICATE or PLAIN_KEY or PKCS12_IMPORT
   • de.businesslogics.bankrechner.bank.ebicsKeyLength: default keylength to be used for key generation (default value of the key length box in bank creation screen). With certificates, any value under 2048 is rounded up to 2048
7. Important note for cluster installations: The following files and directories must be located on the shared disk:
   • The directory defined by bankrechner.dataDir
   • The directory defined by dataStorePath
   • The configuration.properties file defined by configurationPath
7. After you have created all three variables, click Save.

Configuring SSL access

The default SSL setting for the WebSphere Application Server is adequate to handle SSL from the Server side.

However, for an EBICS Client to initiate the SSL connection, you should export and update the SSL certificate used by WebSphere in the EBICS Client keystore configuration. Refer to the Security policy for information about how to generate, store, export and send this certificate. For details of the command for updating the EBICS Client certificate, see EBICS Client administration.

Related topics

Installing EBICS Server on WebSphere: general implementation procedure

Creating WebSphere user lists

Installing WebSphere EBICS Server in a Veritas cluster configuration