You can create the new deployment manager profile on the
same server as portal or on a remote server.
About this task
If the deployment manager is on a different server than
your portal, the create deployment manager profile process has one
manual step. Based on the information that you provide in the wizard,
the wizard creates custom instructions for the manual step.
Each
potential step in the configuration is included.
Procedure
- Manual Step:
Install the deployment manager software.
- Condition
- Remote server deployment manager
- ConfigEngine task
- None
- Create the
deployment manager profile.
- Condition
- None
- ConfigEngine task
- None
- Start the deployment
manager server.
- Condition
- None
- ConfigEngine task
- None
- Augment the
deployment manager profile with the portal profile template.
- Condition
- None
- ConfigEngine task
- None
- Stop the deployment
manager.
- Condition
- None
- ConfigEngine task
- None
- Start the
deployment manager after the profile augmentation is complete.
- Condition
- None
- ConfigEngine task
- None
What to do next
If you changed the context root during
the installation or configuration of
IBM® WebSphere® Portal, then you must complete
the following steps:
- Log on to the Deployment Manager WebSphere Integrated Solutions
Console.
- Go to Security > Global security > Trust
association > Interceptors > com.ibm.portal.auth.tai.HTTPBasicAuthTAI.
- Edit the urlBlackList and urlWhitelist parameters
with the new context path; for example:
- urlBlacklist: /wpsmodified/myportal*
- urlWhiteList: /wpsmodified/mycontenthandler*
- Click Apply, and save all changes.
- Log out of the Deployment Manager WebSphere Integrated Solutions
Console.
Next, use the Create a Cluster option
to create a static or dynamic cluster.