The WebSphere Application Server – Deployment plug-in provides a number of steps for deploying application files to and performing administrative tasks for WebSphere Application Server. The plug-in also contains a number of steps that are related to configuration management, such as creating data sources and JMS requests. These configuration steps are deprecated; instead, use the WebSphere Application Server – Configure plug-in for all configuration-related activities.
This plug-in supports WebSphere Application Server capabilities that are incorporated from WebSphere Virtual Enterprise (WVE) such as application editioning and dynamic clustering.
- You can configure impersonation for the WebSphere Discovery step if the IBM UrbanCode Deploy server is at version 184.108.40.206 or later.
- The impersonating user must have access rights to both the WebSphere Application Server profile directory and the IBM UrbanCode Deploy agent directory. For example, if the WebSphere user is named wasusr with the group wasgrp, and the agent user is named ucdusr with the group ucdrgp, the user wasusr must be a member of the group ucdgrp. You can restrict the WebSphere Application Server profile directory so that only the WebSphere user has read, write, and execute permissions; the group and other users do not need any permissions. In this case, the WebSphere user starts all WebSphere processes. You can restrict the agent directory in the following ways:
- The agent user has read, write, and execute permissions everywhere.
- The group has read and execute permissions everywhere and write permissions in the var/ subfolder.
- Other users have no access.
By default, set the impersonation settings as follows:
- User: WebSphere user
- Password: [empty]
- Group: WebSphere group
- You do not need to select the Always use default impersonation check box unless a Resource overrides it in an incompatible way.