Portal, V6.1

---

 

Enable user provisioning

When users are created in WebSphere Portal, they are not automatically imported into Tivoli Access Manager.

Enabling automatic user provisioning to Tivoli Access Manager changes this behavior. Once this feature is enabled, users are automatically imported into Tivoli Access Manager whenever they are created in WebSphere Portal. When user provisioning to Tivoli Access Manager, anyone with access to the public URL can become an active user in Tivoli Access Manager as long as the self-registration feature remains enabled.

There are two ways to create users in WebSphere Portal:

• Self-registration: This feature is enabled by default.

• Manage Users and Groups portlet: Administrators can use this portlet to create WebSphere Portal users.

To enable user provisioning within Tivoli Access Manager:

1. Run the following validation task to validate that the AMJRTE properties exists:

   Option	Description
   Windows	ConfigEngine.bat validate-pdadmin-connection -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE\ConfigEngine directory
   UNIX	./ConfigEngine.sh validate-pdadmin-connection -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE/ConfigEngine directory
   i5/OS	ConfigEngine.sh validate-pdadmin-connection -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE/ConfigEngine.

   If this task fails, run the run-svrssl-config to create the properties file; see "Creating the AMJRTE properties file" for information about running this task.

2. Run the following task to enable user provisioning:

   Option	Description
   Windows	ConfigEngine.bat enable-tam-userprov -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE\ConfigEngine.
   UNIX	./ConfigEngine.sh enable-tam-userprov -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE/ConfigEngine.
   i5/OS	ConfigEngine.sh enable-tam-userprov -Dwp.ac.impl.PDAminPwd=wpsadmin from the WP_PROFILE/ConfigEngine.

3. To stop and restart the server1 and WebSphere_Portal servers:

   1. Open a command prompt and change to the following directory:

      • Windows: WP_PROFILE\bin

      • UNIX: WP_PROFILE/bin

      • i5/OS: WP_PROFILE/bin

   2. Stop the WAS:

      • Windows: stopServer.bat server1 -username adminid -password passwd

      • UNIX: ./stopServer.sh server1 -username adminid -password passwd

      • i5/OS: stopServer server1 -username adminid -password passwd

   3. Stop the WebSphere_Portal server:

      • Windows: stopServer.bat WebSphere_Portal -username adminid -password passwd

      • UNIX: ./stopServer.sh WebSphere_Portal -username adminid -password passwd

      • i5/OS: stopServer WebSphere_Portal -username adminid -password passwd

   4. Start the WAS:

      • Windows: startServer.bat server1

      • UNIX: ./startServer.sh server1

      • i5/OS: startServer server1

   5. Start the WebSphere_Portal server:

      • Windows: startServer.bat WebSphere_Portal

      • UNIX: ./startServer.sh WebSphere_Portal

      • i5/OS: startServer WebSphere_Portal

 

Parent topic

Configure Tivoli Access Manager

---