test

Sun Java System Portal Server 7.2 Installation and Configuration Guide

Chapter 6 Creating Multi-Portal Instances

You can create a new Portal Server or an instance of a Portal Server using the same Access Manger and Directory Server that you used to create the first or existing Portal Server instance. Creating a new Portal Server helps you to create Portal Severs for different purposes, for example, for different departments of an organization. Creating a new Portal Server instance enables you to cluster portal instances so that the user can access other instances if one Portal Server instance is down.

Note –

When you create a new portal or Portal Server instance, you need to ensure that Portal Server, Access Manager, and Directory Server on the first installation are running.

This chapter contains the following sections:

Setting Up Portals Using the Administration Console

A portal consists of one or more portal server instances that deliver the same content and are mapped to a single Uniform Resource Locator (URL). The content and services delivered by a portal are common to all its instances.

Multiple portals share the same user set. These portals can be deployed on one or more hosts, but they all share the same user repository — the same Access Manager and the Directory server.

Note –

Portals that use different Access Managers are not multiple portals. They are independent and unrelated portals, each with its own set of users.

Access Manger can be a collection of its own instances, all using the same set of Directory Server instances. Different Access Managers are two unrelated Access Managers, not different instances of the same Access Manager.

This section explains how to complete the following tasks:

ProcedureTo List Portals

You can view a list of Portal Servers that are already set up.

  1. Login to the Portal Server Management Console by using http://hostname.domainname:port/psconsole.

  2. Select the Portals tab.

Equivalent psadmin Command

The equivalent Portal Server administration command to list portals is psadmin list-portals -u amadmin -f ./ps_password_file. The ps_password_file file contains the amadmin password.

For more information on the psadmin list-portals subcommand, refer the psadmin list-portals in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

ProcedureTo Create a Portal

During Portal Server installation, a default portal named portal1 is created. You can also create a new portal server using the Create Portal wizard.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Click the New Portal button to launch the wizard.

  4. Provide a unique name for the Portal Server, for example, portal5.

  5. Type a URI that enables end users to access the Portal Server, for example, /portal.

  6. (Optional) Change the default web container instance properties.

    For information, see Creating a New Portal Using the CLI section in the Sun Java System Portal Server 7.2 Installation and Configuration Guide.

  7. Verify the information you supplied.

  8. Click Finish to create the new portal.

  9. (Optional) View the log file to monitor the process.

    1. Login to the machine where portal is to be created.

    2. Run the psdadmin set-logger command.

      ./psadmin set-logger -u uid -f password -m component-type -O logger-name -L log-level

Equivalent psadmin Command

For more information on the psadmin create-portal subcommand, refer the psadmin create-portal in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Templates for webcontainer.properties for supported web containers are in the portal-install-dir/template directory.

ProcedureTo Delete a Portal

You can delete all existing instances of a portal on all hosts and clean up the portal's data in the Access Manager LDAP directory.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. From the list of portals, select the portal you want to remove, and click the Delete Portal button.

Equivalent psadmin Command

For more information on the psadmin delete-portal subcommand, refer the psadmin delete-portal in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

ProcedureTo Export Portal Data

You can archive the following portal data in a par file:

After you archive data, you can import the data to the same portal or to a different portal. To export a portal from psconsole:

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select a portal from the table.

  4. Click the Export button.

  5. Specify the par file location on the Portal Server machine and what you want to export:

    • All Desktop data — the exported par includes file system data and display profile data

    • File system data only — the exported par file includes only the desktop file system data, which is data deployed into the portal desktop and portal web-src

    • Display profile data only — the exported par includes only display profile data

Equivalent psadmin Command

For more information on the psadmin export subcommand, refer the psadmin export in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Note –

This command does not support user data in the Directory Server.

ProcedureTo Import Portal Data to a Portal

You can import into any portal any portal data that you previously exported.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select a portal from the table.

    The Import Desktop Data page appears.

  4. Click the Import button and specify the following:

    • The par file path for the imported data. The par file must be located on the Portal Server system.

    • Whether to continue if the storage structure of the portal does not match the archived file you want to import.

  5. Redeploy the portal web applications.

    1. Schedule a time to run the psadmin redeploy command.

      Plan to do this step off hours or in system maintenance mode, when your system is not in production. This action redeploys the portal war file, and it logs out users who are running a Desktop, causing them to lose their work.

    2. Run the psadmin redeploy command.

      psadmin redeploy -u amadmin -f passwordfile -p portalID --allwebapps

Equivalent psadmin Command

For more information on the psadmin import subcommand, refer the psadmin import in Sun Java System Portal Server 7.2 Command-Line Reference section in the Sun Java System Portal Server 7.2 Command-Line Reference guide.

Note –

This command does not support user data in the Directory Server.

Creating a New Portal Using the CLI

After creating a Portal Server installation on a node, you can create another Portal Server installation on the same node or different nodes using the same Access Manager and Directory Server. This new Portal Server installation is empty. You can use the sample portals provided to customize the portal for your specific needs. For example, you could create portals for different departments of an organization but still use the same Access Manager and Directory Server.

This section explains about creating a new portal installation on the same node or different node depending on your first Portal Server installation.

Creating a New Portal on the Same Node

When you create a new portal on the same node where you have the first Portal Server installation, you need to create a web container instance. Then, you need to duplicate the Webcontainer.properties file that is available in the Portal Server installation directory and modify the Webcontainer.properties file to direct to the new web container instance. Finally, you can run the psadmin create-portal sub command to create the new portal.

ProcedureTo Create a New Portal on a New Domain of Application Server 9.1

  1. Create a new domain, seconddomain, on port 8100.

    /ApplicationServer_base/appserver/bin/asadmin create-domain --adminport 4850 --adminuser admin --instanceport 8100 seconddomain

  2. Start the new domain.

    /ApplicationServer_base/appserver/bin/asadmin start-domain --user admin seconddomain

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

  4. Edit the following properties in the secondportal.properties file.

    • Host=myhostname.mydomain

    • Port=8080

    • Scheme=http

    • WebContainerType=SJSAS91

    • WebContainerInstallDir=/opt/SUNWappserver/appserver

    • WebContainerInstanceName=server

    • WebContainerDomainName=seconddomain

    • WebContainerInstanceDir=/opt/SUNWappserver/appserver/domains/seconddomain

    • WebContainerDocRoot=/opt/SUNWappserver/appserver/domains/seconddomain/docroot

    • WebContainerAdminHost=myhostname.mydomain

    • WebContainerAdminPort=4850

    • WebContainerAdminScheme=https

    • WebContainerAdminUid=admin

    • WebContainerAdminPassword=Application Server admin password

    • WebContainerMasterPassword=Application Server master password

    • ClusterID=cluster id

  5. Create the new portal.

    PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p -secondportal --uri /portal -w secondportal.properties

  6. Restart the web container.

  7. Verify that the new portal has been created.

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

Creating a New Portal on a Remote Node

This section explains how to create a new portal on a remote node. When you create a new portal on a remote node, you should install Access Manager SDK (AMSDK) and a compatible web container. When you install AMSDK, you need to provide the details of Access Manager and Identity Server that you installed for the Portal Server installation. You need to install Portal Server in the Configure Now or Configure Later mode. All the procedures that are explained in this section use the web container of the first portal installation for the second portal installation on a remote node.

Note –

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

After you install AMSDK and the web container, you can use any one of the following options to create a new portal:

ProcedureTo Create a New Portal on Application Server 9.1 in the Configure Now Mode

Before You Begin

Ensure the following:

  1. Invoke the Portal Server 7.2 GUI installer and select Application Server 9.1, Access Manager SDK, and Portal Server and install them in the Configure Now mode.

  2. Provide the Access Manager host and the Directory Server host information.

  3. Change the name of the portal.

    For example, first portal will be portal1. Change the second portal name to portal2.

ProcedureTo Create a New Portal on Application Server 9.1 in the Configure Later Mode

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 9.1 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 9.1 Administration Server.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

  3. Install Portal Server in the Configure Later mode using the Portal Server 7.2 GUI installer.

  4. Complete the Portal Server installation.

    PortalServer_base/bin/psconfig --config example7.xml

To Configure Common Agent Container When Running as Root and Portal Running as Non-root

Follow these steps when the Common Agent Container process is running as root and Portal Server is running as non-root. If the Common Agent Container process is running as the same non-root user as Portal Server, skip the following steps.

ProcedureTo Create a New Portal on Application Server 9.1 Using the psadmin Command

Before You Begin

Ensure the following:

  1. Install Access Manager SDK and Application Server 9.1 in the Configure Now mode using the Java ES installer.

  2. Start the Application Server 9.1.

    ApplicationServer_base/appserver/bin/asadmin start-domain --user admin_user --password admin_password domain-name

  3. Run the installer and install Portal Server software in the Configure Later mode.

  4. Configure Common Agent Container and Java DB.

    PortalServer_base/bin/psconfig --config example2.xml

  5. Verify that the Common Agent Container is working properly.

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

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

  7. Edit the following properties in the secondportal.properties file.

    • Host=hostname.domain

    • Port=8080

    • 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

  8. Create the new portal.

    PortalServer_base/SUNWportal/bin/psadmin create-portal -u amadmin -f ps_password -p secondportal --uri /portal -w secondportal.properties

  9. Restart the web container.

  10. Verify that the new portal has been created.

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

Deploying Sample Content to a New Portal

When you create a new portal, it does not have any sample portal deployed in it. However, you can deploy sample portals such as community sample, enterprise sample, and developer sample to the new portal.

ProcedureTo Deploy a Sample Content to a New Portal

  1. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/input.properties.template file to the /var/opt/SUNWportal/tmp/input.properties file.

    In the Linux platform, copy to the /var/opt/sun/portal/tmp/input.properties file.

  2. Edit the input.properties file that you created in the /var/opt/SUNWportal/tmp directory with the following values.

    • ps.config.location=%PS_CONFIG_LOCATION%

    • ps.portal.id=%PORTAL_ID%

    • ps.access.url=%PORTAL_ACCESS_URL%

    • ps.webapp.uri=%PORTAL_WEBAPP_URI%

    • search.access.url=%SEARCH_ACCESS_URL%

    • search.id=%SEARCH_ID%

    • am.admin.dn=%AM_ADMIN_DN%

    • default.org.dn=%DEFAULT_ORG_DN%

    • portlet.dn=%PORTLET_DN%

    • ps.profiler.email=%PROFILER_EMAIL%

    • ps.profiler.smtp.host=%PROFILER_SMTP_HOST%

  3. Copy the /PortalServer-base/SUNWportal/samples/portals/shared/password.properties.template file to the /var/opt/SUNWportal/tmp/password.properties file.

    In the Linux platform copy the file to the /var/opt/sun/portal/tmp/password.properties directory.

  4. Edit the /var/opt/SUNWportal/tmp/password.properties file and set proper passwords.

    • amadminPassword=%AMADMIN_PASSWORD%

    • amldapuserPassword=%AMLDAPUSER_PASSWORD%

    • userManagementPassword=%USER_MANAGEMENT_PASSWORD%

      You can ignore this value if you are not setting up Communication channels.

  5. Run the following command.

    export JAVA_HOME=/usr/jdk/entsys-j2se

  6. Run the following command to deploy all the portals.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ -logfile /var/opt/SUNWportal/tmp/log-file.txt

  7. (Optional) Run the following command if you wish to deploy only the enterprise portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ enterprise -logfile /var/opt/SUNWportal/tmp/log-file.txt

  8. (Optional) Run the following command if you wish to deploy only the sand box portal.

    /usr/sfw/bin/ant -buildfile /PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/var/opt/SUNWportal/tmp/ sandbox -logfile /var/opt/SUNWportal/tmp/log-file.txt

  9. Restart the web container.

Setting Up Portal Server Instances Using the Administration Console

A Portal Server instance is a web application deployed to a web container. An instance uses a particular Portal Server context URI to serve requests on a specific network port. Each Portal Server instance is associated with a single Portal.

A server instance listens on a particular port, bound to either one IP address or any IP address of the host. For the Portal Server, a server instance corresponds to a deployment container process listening on a port and running a single Java™ Virtual Machine (JVM™ software).

This section explains how to complete the following tasks:

ProcedureTo List Portal Server Instances

You can view a list of Portal Server instances that are already set up.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Click the name of Portal Server from the table.

  4. Select the Server Instances tab.

    The table displays all the instances of the Portal Server you selected.

Equivalent psadmin Command

psadmin list-portals in Sun Java System Portal Server 7.2 Command-Line Reference

ProcedureTo Create a Portal Server Instance

Before You Begin

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select the name of a Portal Server.

  4. Select the Server Instances tab.

  5. Click on the New Instance button to launch the wizard.

  6. Provide the name of the portal identifier.

  7. (Optional) Change the default web container instance properties.

    For information, see Creating a Portal Instance on the Same Node section in the Sun Java System Portal Server 7.2 Installation and Configuration Guide.

  8. Verify the information you supplied, and click Finish to create the new portal instance.

    A progress bar displays the status of this procedure. When the procedure is complete, a results page is provided.

  9. Click Finish to create your new portal instance.

Equivalent psadmin Command

psadmin create-instance in Sun Java System Portal Server 7.2 Command-Line Reference

ProcedureTo Delete a Portal Server Instance

You can delete an instance of a Portal Server.

  1. Login to the Portal Server Management Console.

  2. Select the Portals tab.

  3. Select the name of a Portal Server.

  4. Select the Server Instances tab.

  5. From the table, select the instance you want to remove.

  6. Click Delete Instance button.

Equivalent psadmin Command

psadmin delete-instance in Sun Java System Portal Server 7.2 Command-Line Reference

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:

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

Before You Begin

Ensure the following:

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

  2. Start the new domain, seconddomain.

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

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

  5. Create the new Portal Server instance.

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

  6. Restart the web container.

  7. Verify that the new portal has been created.

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

  8. Access the new portal instance.

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

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

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

Before You Begin

Ensure the following:

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

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

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

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

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

  6. Create the new Portal Server instance.

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

  7. Restart the web container.

  8. Verify that the new portal instance has been created.

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

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

Setting Up Administration Console and Command-Line Interface on a Remote Host

This section explains how to set up Portal Server Administration Console or command-line interface on a remote host. In this scenario, you can install Portal Server on a node and can set up Administration Console or command-line interface on another node. On the node where you set up Administration Console or command-line interface, you need to install a web container and Portal Server packages. You need to install Portal Server packages in the Configure Later mode.

The psconsole of Portal Server can be installed on Application Server 9.1. If you install Portal Server on any of the compatible web containers, such as BEA WebLogic or IBM WebSphere, you need to install Portal Server Console on Application Server 9.1.

ProcedureTo Set Up an Administration Console on a Remote Host on Application Server 9.1

  1. Install Portal Server 7.2 on Node 1 in the Configure Now mode.

  2. Install Application Server 9.1 on Node 2 in the Configure Now mode.

  3. Install Portal Server in the Configure Later mode on Node 2.

  4. Stop the Common Agent Container on node 2.

    /usr/sbin/cacaoadm stop

  5. Run the following command on Node 2:

    /usr/sbin/cacaoadm create-keys -f

  6. Start the Common Agent Container on Node 2 .

    /usr/sbin/cacaoadm start

  7. Create the following directory structure in your current directory.

    mkdir -p WEB-INF/classes/

    mkdir -p WEB-INF/lib/

  8. Create a property file, WEB-INF/classes/pasconnect.properties, with the property value pair pas.host=node1.domain.com.

  9. Copy the cacao_cacao.jar file into the WEB-INF/lib directory.

    The cacao_cacao.jar file is located in the following directories:

    • For Solaris platform: /usr/lib/cacao/lib

    • For Linux platform: /cacao_base/sun/cacao/share/lib

  10. In the psconsole.war file, add the following content.

    jar -uvf /PortalServer_base/SUNWportal/admin/psconsole.war WEB-INF

  11. Deploy the updated psconsole.war file to the Application Server 9.1 instance.

  12. Add the following in the /domains/domain1/server.policy file.


    grant {
permission java.util.PropertyPermission "*","read,write";
permission java.lang.RuntimePermission "writeFileDescriptor";
permission java.lang.RuntimePermission "createClassLoader";
permission java.io.FilePermission "\${/}-", "read,write,execute,delete";

// Used by psconsole app
permission java.security.SecurityPermission "insertProvider.SunSASL";
permission java.security.SecurityPermission "insertProvider.SunJSSE";
permission java.lang.RuntimePermission "getProtectionDomain";

};

  13. Restart the Application Server 9.1 instance.

    Note –

    Step 12 is not required if the security manager is disabled for the Application Server 9.1 domain where psconsole is deployed. This is achieved by commenting out the following JVM option for security policy in the domain.xml file.


    <jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}
/config/server.policy</jvm-options>

ProcedureTo Setup Command-Line Interface on a Remote Host on Application Server 9.1

  1. Install the Portal Server 7.2 on Node 1 in the Configure Now mode.

  2. Install Application Server 9.1 on Node 2 in the Configure Now mode.

  3. Install Portal Server 7.2 on Node 2 in the Configure Later mode.

  4. In the PortalServer_base/SUNWportal/samples/psconfig/example2.xml file, replace tokens with the node information for Node 2.

  5. Run the following command:

    PortalServer_base/SUNWportal/bin/psconfig --config example2.xml

  6. In the pasconnect.properties file, change the property value as pas.host=node1.domain.com.

    The pasconnect.properties file is located in the following directories:

    • For Solaris platform: /etc/opt/SUNWportal

    • For Linux platform: /etc/SUNWportal