Importing resources from WebSphere Portal

With the WebSphere® Portal plug-in, you can discover resources for a portal cell and use plug-in steps to deploy artifacts.

Before you begin

Create a top-level resource group to contain your agents. See Creating groups.
Install an agent on the system that hosts the Portal Node.
IfIBM® WebSphere Application Server is deployed in a directory other than the default directory, specify the following property on the agent:
1. Click Resources > Agents > agent name > Configuration > Agent Properties.
2. Add a property named wsadmin.path.
3. Set wsadmin.path to the fully qualified path to the wsadmin script (including the script name).
  The default location of the wsadmin file on Linux is /opt/IBM/WebSphere/AppServer/bin/wsadmin.sh. The default locations on Windows are C:\IBM\WebSphere\AppServer\bin\wsadmin.bat and C:\Program Files\IBM\WebSphere\AppServer\bin\wsadmin.bat.
Install the WebSphere Portal plug-in.
Install the WebSphere Application Server - Deploy plug-in.

Procedure

On the IBM UrbanCode™ Deploy server, click Resources to view the Resource Tree tab.
Next to the top-level group, click Actions and then click Add Agent.
In the Create Resource window, select the agent and then click Save. The new agent resource is displayed in the resource tree. Eventually, another resource is displayed under the agent resource. This resource is named WebSphereCell and represents the WebSphere Application Server cell. You might need to click Refresh to see the cell resource, and it can take several minutes for the cell resource to be displayed.
Click the WebSphere Application Server cell resource and then click Configuration > Basic Settings. This resource has the WebSphereCell role, which includes several properties that are related to the cell.
In the section that is labeled Role Properties for the WebSphereCell role, specify the connection information for the cell, including the locations of the profile and wsadmin file and the user name and password for the WebSphere Application Server system, as in the following figure:

Note: Leave the Cell Name property blank.
Click Save.
On the Resources tab, next to the cell resource, click Actions and then click Configure using WebSphere Topology Discovery. The discovery step runs. This step might take several minutes. A log is displayed to show progress.
Click Save to close the Auto Configure window.
Wait 30-60 seconds, then click Refresh. A twisty is now next to WebSphereCell. Expand it and make sure the resource tree matches your WebSphere Application Server topology. It will contain deployable artifacts for WebSphere Portal (theme, PAA, WAR, ConfigEngine command, XMLAccess script)
On the WebSphereCell entry, click Edit and check that Cell Name was filled in and is correct.
Define properties for resources. Click the resource, then the Configuration tab, then Resource Properties.
- For ND topology, define the properties for Portal Cluster, Portal Primary Node, and Portal Secondary Node resources.
- For stand-alone topology, define the properties for the Portal Node resource.
Define the following properties:
- portal.home: Portal installation directory
- portal.profile.home: Portal profile directory
- portal.admin.user: Portal administrator user name
- portal.admin.password: Portal administrator password
- portal.config.port: Portal configuration port
- websphere.password: WebSphere administrator password
Create components for the resources. You need one component for each resource to deploy.
Add the components to the resources.
1. Go to the resource.
2. Choose Actions > Add Component
3. Select the component to use.
Create the application.
1. Go to Applications.
2. Click Create Application (if one does not exist). You can also use an existing application that is attached to the cell to manage.
3. Enter an application name, then click Save.
4. Click the Components tab, then add the component that was created by the template generation procedure.
Create an application environment.
1. In the Environments tab, click Create Environment.
2. Enter an environment name, then click Save.
3. Go to the environment editing page.
4. Click on the environment name, then click Add Base Resource. Choose the group for your exemplar cell and environment.
5. Edit the environment properties for the component. Click Configuration > Environment Properies. In the Component Environment Properties list, enter values for each property shown. Note that values are already filled in with default values if you provided them above.
Create an application process of type Deployment for configuration and deployment.
1. Click the Processes tab.
2. Add a deploy step.
3. Drag and drop the Install Component step onto the process editor.
  1. Select the component to use. You created this component for the resource. For example, you created a component to contain a Portal WAR file to be deployed.
  2. Choose the process for the component. For example, you would choose Deploy Portal WAR file for a Portal WAR file component.
4. Click Save.
5. Save the process.
Run the process to test the newly created component.

Feedback