Create a Portal application server profile on AIX

Create a Portal application server profile on AIX

Overview

The WebSphere Portal installation registers the WebSphere Portal application server profile template with IBM WAS. We can create new profiles based on this template.
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 the initial profile used 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 using PMT

The Profile Management Tool is not support on 64-bit environments. Use manageprofiles instead.
Start the tool...
cd $WAS_HOME/bin/ProfileManagement
./pmt.sh

go to...
Launch Profile Management Tool | Create | Environment Selection | WebSphere Portal Server 7.0.0 | WebSphere Portal Server | Next

and set...

On the Profile Name and Location 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.
On the Node, Host, and Cell Names panel 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.
On the Administrative Security Make sure that 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.
On the Service Definition Specify whether or not the WebSphere Portal server in this profile is to be registered and controlled as a service. Click Next to continue.
On the Security Certificate (Part 1) Do not modify the default values. Security settings are imported from the configuration archive when the profile is created. Click Next to continue.
On the Security Certificate (Part 2) Do not modify the default values. Security settings are imported from the configuration archive when the profile is created. Click Next to continue.
On the Profile Creation Summary 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.

Create a new profile using manageprofiles.sh
cd WAS_HOME/bin 
manageprofiles.sh -create \
                  -templatePath $PORTAL_HOME/profileTemplates/default.portal \
                  -profileName testPortal1 \
                  -profilePath /usr/IBM/WebSphere/testportal1 \
                  -cellName testCell \
                  -nodeName testNode
In this example, the portal profile template is installed under:
$PORTAL_HOME/profileTemplates/default.portal

The new profile is testportal1 and is located under...
/usr/IBM/WebSphere/testportal1

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.

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 AIX

+
Search Tips | Advanced Search

On the Profile Name and Location	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.
On the Node, Host, and Cell Names panel	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.
On the Administrative Security	Make sure that 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.
On the Service Definition	Specify whether or not the WebSphere Portal server in this profile is to be registered and controlled as a service. Click Next to continue.
On the Security Certificate (Part 1)	Do not modify the default values. Security settings are imported from the configuration archive when the profile is created. Click Next to continue.
On the Security Certificate (Part 2)	Do not modify the default values. Security settings are imported from the configuration archive when the profile is created. Click Next to continue.
On the Profile Creation Summary	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.