Create a Portal application server profile on Linux

pmt.sh

1. Run...
   cd WAS_HOME/bin/ProfileManagement
   ./pmt.sh

2. Click Launch Profile Management Tool

3. Click Create to create a profile.

4. On the Environment Selection panel, expand...
   WebSphere Portal Server 8.0.0 | WebSphere Portal Server | Next

5. On the panel...
   Profile Name and Location

   ...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.

   We can choose to select the check box...

   Create the server using the development template

   ...to enable developer mode for this profile.

   We can choose to select the check box...

   Make this profile the default

   ...to specify that this profile is the default profile in the system.

6. On the panel...
   Node, Host, and Cell Names

   ...provide the node name and TCP/IP host name for the new profile.

   To federate this profile, the node name must be unique from other profiles in the same management cell (under dmgr control). The host name must be valid and reachable over the network. Click Next to continue.

7. On the Administrative Security panel, uncheck the checkbox...
   Enable administrative security

   The new profile is then created using the same security settings that are saved in the Portal profile template. After the new Portal profile is created, the security configuration of the new profile can then be modified as required. Click Next to continue.

8. On the panel...
   Service Definition

   ...specify whether the WebSphere Portal server in this profile is to be registered and controlled as a service. Click Next to continue.

9. On the panel...
   Profile Creation Summary

   ...review the information collected by the wizard, and then click Create to create the profile based on the supplied information.

   The port values presented in the summary value is overwritten by the port values used by the servers present in the configuration archive provided as part of the portal profile template. These port values will must be adjusted after profile creation if they are in conflict with other ports on the local system.

   The creation summary shows a "server name" value of null. We can ignore this summary since the application server name was not requested on previous panels and always defaults to WebSphere_Portal.

10. Click Finish to exit PMT.

manageprofiles.sh

cd WAS_HOME/bin
./manageprofiles.sh -create \
                    -templatePath /opt/IBM/WebSphere/PortalServer/profileTemplates/default.portal
                    -profileName testPortal1
                    -profilePath /opt/IBM/WebSphere/testportal1
                    -cellName testCell
                    -nodeName testNode

In this example, the portal profile template is installed under

/opt/IBM/WebSphere/PortalServer/profileTemplates/default.portal

The new profile is testportal1 and is located under...

/opt/IBM/WebSphere/testportal1

We can also use the following parameters:

• -isDefault

  signifies that this profile is to serve as the default profile for the installation

• -isDeveloperServer

  indicates that WebSphere Portal is to be configured for development mode in this profile.

• -nodeName

  provides a node name for the new profile; if not provided, the node name defaults to a value based on the local host name. Required if federating this profile into a managed cell because this value must be unique from other nodes in the cell.

See manageprofiles.sh for a complete list of parameters.

Because all database domains are identically configured for each profile, modify the database configuration for database domains that cannot be shared on that you do not want to share.

Parent: Create or augment profiles on Linux