Enable your Version 4.0 custom user registry to run with Version 5.0

Use your Version 4.0 custom user registry with Version 5.0. However, it is recommended that you migrate your code to the Version 5.0 implementation.

To enable your custom user registry to run with Version 5.0, perform these steps:

1. In the Version 4.0 documentation, it was recommended that you not place your user registry class files in a directory within the WebSphere Application Server directory structure. This includes the directories that are provided for your WebSphere Application Server instance. If your implementation does not comply with this recommendation, continue to the next step. Otherwise, skip steps 2 through 4, and start with step 5.

2. Copy your user registry class files to an integrated file system directory other than one provided by the product or one that is part of an instance. For example, create a directory that is named /WAS_Sample_Registry, and copy your user registry class files to that directory.

3. Grant Execute (*X) authority to your directory (for example, /WAS_Sample_Registry) for the OS/400 user profile under which your application server runs. (The default user profile is QEJBSVR). For example, on an iSeries command line, enter this command:

   CHGAUT OBJ('/WAS_Sample_Registry') USER(QEJBSVR) DTAAUT(*X)

4. Grant Read and Execute (*RX) authority to each of your class files for the OS/400 user profile under which your application server runs (QEJBSVR). For example, if you are using the Version 4.0 sample custom user registry, enter these commands on an iSeries command line:

   CHGAUT OBJ('/WAS_Sample_Registry/FileRegistrySample.class') USER(QEJBSVR) DTAAUT(*RX)
   CHGAUT OBJ('/WAS_Sample_Registry/RegExpSample.class') USER(QEJBSVR) DTAAUT(*RX)

5. Add the directory that contains your implementation classes to the classpath of each application server that uses your custom user registry by performimg these steps in the administrative console:

   1. In the navigation menu, expand Servers, and click Application Servers.
   2. In the Application Servers page, click the name of your server.
   3. Under Additional Properties, click Process Definition.
   4. Under Additional Properties, click Java Virtual Machine.
   5. Under Additional Properties, click Custom Properties.

   6. If the ws.ext.dirs property has already been defined, click it, append a colon (:) to the value, and add the fully-qualified path of the directory that contains your implementation classes.

      If the ws.ext.dirs property is not listed, click New. Specify ws.ext.dirs as the name of the property, and specify the directory that contains your implementation classes.

   7. Click OK.
   8. Click Save.

   If you are using the Network Deployment product, add the directory to the classpath of the deployment manager and node agent servers.

6. Add the directory to the server.policy file. Edit the server.policy file that is located in the properties subdirectory of your instance. For example, specify the following permission:

     grant codeBase "file:/WAS_Sample_Registry/-" {
       permission java.security.AllPermission;
     };

   For more information, see Configure the server.policy file.