Verifying the security settings
For the security changes to take effect, you have to restart Lombardi Edition server1.
- Log out of the Integrated Solutions Console.
- Stop and start the Lombardi Edition servers. At a minimum, you need to restart server1.
- An easy way to do that is via the command line. In a command window, go to <WLE_HOME>/AppServer/profiles/Lombardi/bin.
- To stop, enter
- To start, enter
- Bring up the Integrated Solutions Console again and log in using
tw_useras the user ID and password.
Tip: If you cannot log in, you can replace
>/security.xmlwith the backup copy and restart the server.
Use the wsadmin command:
wsadmin –conntype none. At the wsadmin prompt, enter
- Go to Users and Groups > Manage Users.
- Search for the wild character * on User ID.
- You now see users from all the repositories.
Figure 11 shows the user IDs from both repositories: internal and TDS.
Warning: You cannot have the same user ID in two repositories. In this example, you see that there are two of
tw_runtime_server. You will have to delete one of those duplicate entries, most likely the one in the new LDAP schema. We recommend that to keep the original users in the file-based repository. The other option is to use a standalone LDAP configuration rather than a federated repository.
Figure 11. User search results
- Optionally, as a quick workaround, you can go to Users and
Groups > Administrative user roles.
- Click Add.
- Highlight Administrator role.
- Search for users using the wild character *.
- Choose admin and map it to the administrator role. Click OK.
You see two users (
admin) in Administrator role. That means you can now log into the Integrated Solutions Console using the
adminuser ID from Tivoli Directory Server.
- You may log out and test by logging back into the Integrated
Solutions Console using
adminas the user ID.
- A better test is to bring up Lombardi Process Center
http://<WLE_HOST>:19086/ProcessCenter) or Lombardi Process Portal (
http://<WLE_HOST>:19086/portal), and log in using
admin(or any other user from LDAP). Figure 12 shows a screenshot of
adminlogged into Lombardi Process Portal.
Figure 12. User search results
That is it. The next steps, if necessary, are to configure single sign-on (SSO) between Lombardi Edition and other applications like WebSphere Portal.