Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Modifying to the federated repository on i5/OS

If you originally configured a standalone LDAP user registry but find that you need a more robust security configuration, you can change to the federated user repository.

1. Use a text editor to open the wkplc.properties file, located in the profiles/wp_profile/ConfigEngine/properties directory.
2. Required: Enter only the following required parameters in the wkplc.properties file under VMM Federated repository properties:

   1. For federated.primaryAdminId, type the user ID of an existing WebSphere Application Server administrator.
   2. For federated.registryClassName, type the registry class name.
   3. For federated.realm, type the name of the realm you want to use for the federated repository. If blank, the default realm is used.
3. Optional: Enter the following optional parameters in the wkplc.properties file under VMM Federated repository properties:

   1. For federated.ignoreCase, type true to ignore case during searches or false to make searches case sensitive.
   2. For federated.serverId, type the user ID for the federated repository.
   3. For federated.serverPassword, type the password for the federated repository user ID.
4. Save your changes to the wkplc.properties file.
5. Run the ConfigEngine.sh -profileName profile_root wp-modify-federated-security task, located in the profiles/wp_profile/ConfigEngine directory to add a new property to the property extension configuration. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
6. Perform the following steps to stop and restart the server1 and WebSphere_Portal servers:

   1. Open a command prompt and change to the wp_profile_root/bin directory.
   2. Enter the stopServer server1 -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Application Server. Note: profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
   3. Enter the stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password command to stop the WebSphere Portal Express server.
   4. Enter the startServer server1 -profileName profile_root command.
   5. Enter the startServer WebSphere_Portal -profileName profile_root command.