Create a Portal application server profile on Windows

The WebSphere Portal installation registers the WebSphere Portal application server profile template with IBM WAS. You can then create new profiles based on the template using either the manageprofiles command or the Profile Management Tool, which is a graphical user interface that guides you through the process. The newly created profile's WAS administrator ID and password are set according to the input given. The portal still has the same security and database configurations, including the portal administrator ID and password, as the initial profile used to run the enable-profiles task. If initial profile was using the Derby database, a fresh copy is automatically created with the new profile. If initial profile was configured to use a non-Derby database, then all the database domains of the new profile will be identically configured. Likewise, any security configurations (like configuration to a stand-alone or federated LDAP) that were made before running the enable-profiles task will be preserved with the new profile.

Create a new profile:

  1. Choose one of the following methods to create a new profile:

      If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

      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, expand WebSphere Portal Server 7.0.0 and select WebSphere Portal Server, 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.

          You can also choose to select the Create the server using the development template check box to enable developer mode for this profile and the Make this profile the default check box to specify that this profile is the default profile in the system.

      6. On the Node, Host, and Cell 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 Administrative Security panel, verify the Enable administrative security checkbox is unchecked. The new profile will then be created using the same security settings that are saved in the Portal profile template. Once the new Portal profile has been created, the security configuration of the new profile can then be modified as required. Click Next to continue.

      8. On the Service Definition panel, specify whether or not the WebSphere Portal server in this profile is to be registered and controlled as a service. Click Next to continue.

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

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

      11. On the Profile Creation Summary panel, review the information collected by the wizard, and then click Create to create the new profile based on the supplied information.

          The port values presented in the summary value will be overridden 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 need to 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, which can be ignored since the application server name was not requested on previous panels and always defaults to 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/default.portal
			-profileName testPortal1
			-profilePath C:/WebSphere/testportal1
			-cellName testCell
			-nodeName testNode

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

      You 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 will default 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 command for a complete list of parameters.

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


Parent

Create or augment profiles on Windows

 


+

Search Tips   |   Advanced Search