Create a Portal custom profile on Windows

Custom profiles do not contain any servers or applications; they are used as runtime environments to create additional cluster members. After creating the profile, the node needs to be federated into an existing cell. The portal server will be added when you add the additional nodes to an existing cluster.

Create a new profile that will be used as an additional node:

Choose one of the following methods to create a new profile that will be used for additional cluster members: If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

Choose between the Profile Management tool and the manageprofiles task to create a new profile that will be used for additional cluster members.

Option Steps
Profile Management Tool To use the Profile Management Tool:

  1. Run the pmt.bat command from the WAS_HOME/bin/ProfileManagement directory.

  2. Click Launch Profile Management Tool.

  3. Click Create to create a new profile.

  4. On the Environment Selection panel, select the WebSphere Portal 7.0.0 -> Custom Portal profile, and then click Next.

  5. On the Profile Name and Location panel, provide the name for the new profile and its location in the file system. The name and location must be unique from other existing profiles. Click Next to continue.

  6. On the Node and Host Names panel, provide the node name and TCP/IP host name for the new profile. If you plan to federate this profile, the node name must be unique from other profiles in the same management cell (under Deployment Manager control). The host name must be a valid and reachable over the network. Click Next to continue.

  7. On the Federation panel check the Federate this node later check box to federate the node in the future.

      CAUTION: Do not enter the values for the Dmgr to federate now as this will cause an unusable portal node.

  8. On the Security Certificate (Part 1) panel, do not modify the default values because the security settings are imported from the Portal configuration archive when the profile is created. Click Next to continue.

  9. On the Security Certificate (Part 2) panel, do not modify the default values because the security settings are imported from the Portal configuration archive when the profile is created. Click Next to continue.

  10. If you choose to federate the profile now, the Port Values Assignment panel displays. Change any necessary port values and then click Next.

  11. On the Profile Creation Summary panel, review the information collected by the wizard, and then click Create to create the new profile with WebSphere Portal.

  12. Click Finish to exit PMT.

manageprofiles command Run the following command from the WAS_HOME/bin directory: 

    manageprofiles.bat -create -templatePath C:/WebSphere/PortalServer/profileTemplates/managed.portal
			-profileName testManagedPortal1
			-profilePath C:/WebSphere/PortalServer/profiles/testManagedPortal1
			-cellName testCell
			-nodeName testNode
			-hostName myportal.myco.com

In this example, the portal profile template is installed under the C:/WebSphere/PortalServer/profileTemplates directory. The new profile is named testManagedPortal1 and is located under the C:/WebSphere/PortalServer/profiles/testManagedPortal1 directory.


Parent

Create or augment profiles on Windows


Related tasks


Install WebSphere Portal

 


+

Search Tips   |   Advanced Search