Creating a Portal Server Instance Using the CLI

This section explains how to create a new instance of Portal Server. When you install Portal Server, it creates an instance of Portal Server on the default instance of the web container. For example, if you install Portal Server on Sun Java System Application Server 9.1, a Portal Server instance is created on the default instance of Application Server 9.1 that listens on port 8080. You can also create several instances of the web container and create instances of the Portal Server that are already installed. A new instance of Portal Server that you create will have all the portals that are deployed on your first Portal Server.

After creating instances of Portal Server, you can use clustering or load balancing to serve the users effectively. Portal Server instances can be created on a node where you installed Portal Server or on a remote node where you installed a web container, AMSDK, and Portal Server packages.

Creating a Portal Instance on the Same Node

This section explains how to create a Portal Server instance on different web container instances or domains on the same node, where you installed Portal Server. When you create a Portal Server instance, you can create the instance on a new configuration or a new domain of the web container. You can also create a Portal Server instance on the existing configuration or domain of the web container where you have installed Portal Server.

This section explains the following:

Creating a Portal Instance on a New Domain of Application Server 9.1
Creating a Portal Instance on a New Instance of Application Server 9.1

To Create a Portal Instance on a New Domain of Application Server 9.1

Before You Begin

Ensure the following:

Portal Server is installed on Application Server 9.1. Name of the first portal is portal1.
Access Manager is installed on Application Server 9.1.
Application Server 9.1 is installed in the default directory.

Create a domain, seconddomain, and a server instance on the port 8100.

/opt/SUNWappserver/appserver/bin/asadmin create-domain --adminport 4850 --adminuser admin --instance-port 8100 seconddomain

Start the new domain, seconddomain.

Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS91 file to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.

Edit the following properties in the secondinstance.properties file.
- Host=hostname.domain
- Port=8100
- Scheme=http
- WebContainerType=SJSAS91
- WebContainerInstallDir=/opt/SUNWappserver/appserver
- WebContainerInstanceName=server
- WebContainerDomainName=domain1
- WebContainerInstanceDir=/opt/SUNWappserver/domains/domain1
- WebContainerDocRoot=/opt/SUNWappserver/domains/domain1/docroot
- WebContainerAdminHost=hostname.domain
- WebContainerAdminPort=4850
- WebContainerAdminScheme=https
- WebContainerAdminUid=admin id
- WebContainerAdminPassword=Application Server Administrator password
- WebContainerMasterPassword=Application Server master password
- ClusterID=cluster id

Create the new Portal Server instance.

PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties

Restart the web container.

Verify that the new portal has been created.

PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password

Access the new portal instance.

http://hostname.domain.com:8100/portal

Restart the Common Agent Container.

On the Solaris platform:

/usr/share/bin/cacaoadm stop 
/usr/share/bin/cacaoadm start

On the Linux platform:

/opt/sun/cacao/bin/cacaoadm stop
/opt/sun/cacao/bin/cacaoadm start

To Create a Portal Instance on a New Instance of Application Server 9.1

Before You Begin

Ensure the following:

Portal Server is installed on Application Server 9.1. Name of the first portal is portal1.
Access Manager is installed on Application Server 9.1.
Application Server 9.1 is installed in the default directory.

Create a node agent, nodeagent1, in the same domain in which the first Portal Server instance exists.

ApplicationServer_base/appserver/bin/asadmin
create-node-agent --host hostname.domain
--port 4848 --user ApplicationServer_admin_user
--password ApplicationServer_admin_password nodeagent1

Create an instance in the node agent.

ApplicationServer_base/appserver/bin/asadmin 
create-instance --host hostname.domain 
--port 4848 --user ApplicationServer_admin_user
--password ApplicationServer_admin_password
--nodeagent nodeagent1 --systemproperties HTTP_LISTNER_PORT=3870 server2

Start the node agent and the instance.

ApplicationServer_base/appserver/bin/asadmin
start-node-agent --user admin --password password nodeagent1

ApplicationServer_base/appserver/bin/asadmin
start-instance --port 4848 --user admin --password password server2

Note –

When you start the instance after starting the node agent, the start-instance CLI may fail stating that the server instance is already started. In this case, ignore the message. This is due to the server instance being started while starting the node agent. This behavior is controlled by the start-servers-in-startup attribute, located in the domain.xml and if it is set to true, all the server instances which are not running are started during node-agent startup.

Copy the PortalServer_base/SUNWportal/template/Webcontainer.properties.SJSAS91 to a PortalServer_base/SUNWportal/bin/secondinstance.properties file.

Edit the following properties in the secondinstance.properties file.
- Host=hostname.domain
- Port=3870
- Scheme=http
- WebContainerType=SJSAS91
- WebContainerInstallDir=/opt/SUNWappserver/appserver
- WebContainerInstanceName=server
- WebContainerDomainName=domain1
- WebContainerInstanceDir=/opt/SUNWappserver/appserver/domains/domain1
- WebContainerDocRoot=/opt/SUNWappserver/appserver/domains/domain1/docroot
- WebContainerAdminHost=hostname.domain
- WebContainerAdminPort=4848
- WebContainerAdminScheme=https
- WebContainerAdminUid=admin id
- WebContainerAdminPassword=ApplicationServer admin password
- WebContainerMasterPassword=ApplicationServer master password
- ClusterID=cluster id

Create the new Portal Server instance.

PortalServer_base/SUNWportal/bin/psadmin create-instance -u amadmin -f ps_password -p portal1 -w secondinstance.properties

Restart the web container.

Verify that the new portal instance has been created.

PortalServer_base/SUNWportal/bin/psadmin list-portals -u amadmin -f ps_password.

Access the new Portal Server instance.

http://hostname.domain.com:3870/portal

Creating a Portal Server Instance a Remote Node

This section explains how to create a Portal Server instance on a remote node. In this scenario, you have Portal Server installed on a node. You are creating an instance of Portal Server on another node. You need to install Access Manager SDK, web container, and Portal Server packages on the node where you wish to install Portal Server instance. Then, you need to run the psadmin create-instance command to create a new Portal Server instance.

Note –

When you install Access Manager SDK, provide the same encryption key, am password, and LDAP password that are used for Access Manager on Node 1.