IBM Support

Installing ITDS WebAdmin Tool into WebSphere Application Server Network Deployment V7.0

Question & Answer


Procedure to deploy the ITDS WebAdmin Tool into WebSphere Application Server Network Deployment V7.0.


The deploy_IDSWebApp script or batch file can only be used in an embedded WebSphere environment as per the design of the script. deploy_IDSWebApp script's current design does not allow it to work with WebSphere Application Server Network Deployment Environment.

Refer to Recommended Fixes for latest recommended level of WAS for a given version of Tivoli Directory Server.

More info on various tested versions of WAS can be found in latest Fix Pack README files of the Tivoli Directory Server.


This document provides the procedure to install ITDS WebAdmin Tool into a Full WebSphere Application Server Network Deployment V7.0 environment via Deployment Manager.

The applicable ITDS WebAdmin Tool versions for the following procedure are as below:
Web Application version: 4.00nn provided with ITDS 6.1.0.x
Web Application version: 5.00nn provided with ITDS 6.2.0.x
Web Application version: 6.00nn provided with ITDS 6.3.0.x

The following procedure is written using WebSphere Application Server Network Deployment at V7.0.0.5 level.

1. Make sure the required WebSphere ND processes are up and running. Connect to the “Integrated Solutions Console” of the WAS ND.
Typical http URL is:

2. Login to the console using a known WebSphere user id. If you have WebSphere enabled for security, you will be required to provide user id along with password.

3. After successful login, Click expanding the “Applications” on the left hand side navigator and Click on “New Application”:

4. From the main panel which shows “New Application”, Click on “New Enterprise Application”:

5. In the “Preparing for the application installation” panel, choose either “Local file system” OR “Remote file system” based on where exactly your ITDS WebAdmin Tool (IDSWebApp.war) file is located. Here below its assumed that you have installed the ITDS WebAdmin Tool on the same system as that of the WebSphere Cell/Node.

Select “Remote file system”, Click on “Browse” button.

6. Browse to appropriate path (in this case /opt/ibm/ldap/V6.2/idstools/) and select IDSWebApp.war file and Click OK button.

7. Verify the “Full path” of the IDSWebApp.war file and Click “Next” button:

8. Select “Fast path” and Click “Next” button:

9. In “Step 1: Select installation options” scroll down to the bottom part of the page and Click “Next” button (leaving all default values):


10. In “Step 2: Map modules to Servers”, specify the application server or cluster or servers where you want to install the Web application.
a. First select the “Check box” from the table for the module “IBM Tivoli Directory Server Web Application v2.0”
b. Then select appropriate Servers and/or Clusters from the “Clusters and servers” text box / drop down box.
c. Finally Click on “Apply” button.
d. Verify “Server” Column in the table getting updated appropriately.

e. Now Click on “Next” button at the bottom part of the panel.

11. In “Step 3: Map virtual hosts for Web modules”, If necessary, specify the appropriate “Virtual host”, otherwise just take the defaults from this step and Click “Next” button:

12. In “Step 4: Map context roots for Web modules”, Update “Context Root” Value to be “/IDSWebApp” and Click “Next” button:

13. In “Summary” page, verify the values and Click Finish.

14. The following messages gets displayed:


If there are enterprise beans in the application, the EJB deployment process can take several minutes. Do not save the configuration until the process completes.
Check the SystemOut.log on the deployment manager or server where the application is deployed for specific information about the EJB deployment process as it occurs.
ADMA5016I: Installation of IDSWebApp_war started.
ADMA5067I: Resource validation for application IDSWebApp_war completed successfully.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5005I: The application IDSWebApp_war is configured in the WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5005I: The application IDSWebApp_war is configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/wstemp/3506402/workspace/cells/tdsx6404Cell01/applications/IDSWebApp_war.ear/IDSWebApp_war.ear
ADMA5005I: The application IDSWebApp_war is configured in the WebSphere Application Server repository.
SECJ0400I: Successfully updated the application IDSWebApp_war with the appContextIDForSecurity information.
ADMA5005I: The application IDSWebApp_war is configured in the WebSphere Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application IDSWebApp_war is complete.
ADMA5013I: Application IDSWebApp_war installed successfully.

Application IDSWebApp_war installed successfully

To start the application, first save changes to the master configuration.

Changes have been made to your local configuration. You can:
Save directly to the master configuration.
Review changes before saving or discarding.

15. Click “Save” link.

16. Goto “Applications”, “Application Types”, click on “WebSphere enterprise applications”:

17. From “Enterprise Applications”, Notice the “IDSWebApp_war” is in “Stopped” status. Select check box for “IDSWebApp_war” from the table and Click “Start” button:

18. A message gets displayed about the application start and application status gets updated in the table:

19. Now Open another browser window and connect to the application using the http URL as below:
Note: Update the appropriate port number as per the selection of “Virtual host in step 11 above. In this case we have selected “default_host”.
The following gets displayed in the browser:

Enter User ID: superadmin
Password: secret
Click “Login” button.
Customize the user id and password after first login.

20. Notice the Web application version in the bottom right hand side of the “Introduction” panel

21. Click on “Manage console servers” link – then click on “Add...” button:

22. Add appropriate ldap server Hostname for the ITDS ldap server (with same version as that of web application), Update Port and Administration port (if necessary). Then click OK button: (Also click OK on the resulting panel again).

23. “Manage console servers” table shows the newly added “ldaphost” in a row:

24. Click on Logout link from Navigator and again goto Login page to see login option for ldaphost: (Login using admin dn and password of ldap server).

The same info from this document is also available as a pdf document:
IDSWebApp_WAS_ND_7.0.pdf IDSWebApp_WAS_ND_7.0.pdf

[{"Product":{"code":"SSVJJU","label":"IBM Security Directory Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.1;6.2;6.3;6.3.1","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018