Step 13: Configuring the WebSphere database registry

When to use this procedure

The WebSphere database registry enables you to manage users from the Axway EBICS Server GUI.

This procedure is only necessary if you are using the WebSphere database registry for authentication.

WebSphere allows only one Authentication module. Because this may conflict with an already existing Authentication module, the database registry does not need to be installed if an Authentication module is already provided.

Procedure

Configure the server security to use the database registry as the server Authentication module:

1. Open a session in the WebSphere Administration Console.
2. Navigate to the menu Security > Secure administration, applications, and infrastructure.
3. In the User account repository menu, from the Available realm definition drop-down list, select Standalone custom registry.
4. Once it is set as the current, you must stop and re-start the Web Application Server.
5. Open a session in the WebSphere Administration Console.
6. Navigate to the menu Security > Secure administration, applications, and infrastructure.
7. In the Administrative security menu, enable administrative security.
8. In the Application security menu, enable application security.
9. In the Java 2 security menu, do not select the option to use Java 2 security to restrict application access to local resources.
10. Click Configure.
11. Enter the following parameters:
    • Primary administrative user name: Enter admin
    • Select Automatically generated server identity.
    • Custom registry class name: Enter de.businesslogics.bankrechner.websphere.DatabaseRegistry
    • On the Custom Properties menu:
      • Add a variable named DBDRIVER and give it the value oracle.jdbc.driver.OracleDriver
      • Add a variable named DBUSER and give it the value of the database user name.
      • Add a variable named DBPASSWORT and give it the value of the database user password. The password can be in clear text or encrypted.
      • Add a variable named DBPASSWORT_ENC and give it the value of the password encryption algorithm. It can be one of three values:
        • NONE: password is in clear text
        • B64: password is encoded in Base64
        • AES: password is ciphered with AES algo and encoded in Base64
      • Add a variable named DBURL and give it the value jdbc:oracle:thin:@ORACLEHOST:ORACLEPORT:INSTANCE (updated depending on the real values).
12. Click Save.
13. Set the current realm definition to Standalone custom registry.
14. Click Apply and then Save.
15. Stop and then restart the WebSphere server as follows:
    • Go to <WebSphere installation dir>/profiles/<profile name>/bin
    • Run the script: stopServer <server name>
    • Run the script: startServer <server name>

Related topics

Installing EBICS Server on WebSphere: general implementation procedure