TWiki . OpenPortal . PortalInstallInstructions

In the instructions below, $PSBUILD refers to the location of the built Portal Server source code as produced by the build instructions. Installer image includes Portal, AM-SDK and common dependencies(JDK not included !!). Containers supported are AS9.1 and GF v2. Installer is available for Solaris sparc, X86 and Linux for B8.

Clean System

$ /opt/SUNWappserver/uninstall
...
$ $PSBUILD/install/bin/scrub_portal.sh
$ $PSBUILD/install/bin/scrub_jes5.sh

$ rm /var/tmp/* and /tmp/* 
pkgrm -n -Y sims-product

Pre-requisites

Install 32-bit JDK1.5.0_09 or above on the system. Set JAVA_HOME to this jdk directory. The installer requires JRE5 to run.

Note: AS9.1 has JDK bundled with it. If you are using AS9.1 as the web container then you install jdk while installing AS9.1. The AS9.1 installer gives an option to install jdk or use an already existing jdk. For Glassfish installations, jdk has to be installed manually. Also the jdk installed has to be package based as otherwise cacao will not start. * If you are using JDK 1.6, you need to have at least JDK 1.6.0_05 (Update 5) or later in order for the PS cacao module to work properly.

Single host or PS/AM/DS on single host

Install Web Container

Application Server 9.1

* See JDK and other pre-requisites above *
%%(color:#3366ff;)Application server9.1 location is INTERNAL to Sun and not available to external users %%
IEC: /net/pradeep/space/AS91ifrb57
SCA: /net/koori.sfbay/onestop/glassfish/9.1/archive/fcs/latest/bundles

$ cd /var/tmp
$ cp /net/koori.sfbay/onestop/glassfish/9.1/archive/fcs/latest/bundles/<osname>-<osarch>-ifr.zip . 
$ unzip <osname>-<osarch>-ifr.zip
$ cd installer-ifr 
$ ./setup

Start the Application Server after installation is over

Glassfish

Download glassfishv2 b57 from [https://glassfish.dev.java.net/downloads/v2-b58g.html] and install.
Start the default domain instance

Install Access Manager (and Directory server)

Application Server 9.1

Note: With JES5 installer, Access Manager can only be installed on AS9.1 in configure later mode, whereas with JES5U1^? installer Access Manager can be installed on AS9.1 in configure now mode. Steps for both cases are given below.

Invoke the Jes5U1^? installer. Install Access Manager and Directory Server in configure now mode.
Make sure you select Application Server in the Access Manager: WebContainer^? Selection Panel and in the Access Manager: WebContainer^? Panel appropriate values are given. instance and docroot should point to the right values. default values being /opt/SUNWappserver/appserver/domains/domain1 and /opt/SUNWappserver/appserver/domains/domain1/docroot.
Proceed with the installation.
Start the Directory Server after installation is over and restart AS9.1.
Login to the AM console (http://server/amserver/console) as amadmin to make sure that the installation is working to this point.

Glassfish

Install Directory Server and Access Manager using JES5u1 installer in configure now mode. DO NOT START DIRECTORY SERVER AND GLASSFISH.
Modify AMConfig.properties to point to JSSE instead of JSS. com.iplanet.security.SecureRandomFactoryImpl=com.iplanet.am.util.SecureRandomFactoryImpl com.iplanet.security.SSLSocketFactoryImpl=netscape.ldap.factory.JSSESocketFactory com.iplanet.security.encryptor=com.iplanet.services.util.JCEEncryption
Start Directory server and Glassfish and access /amconsole

Install Portal Server 7.2

Using ant based scripts - NOT SUPPORTED

Follow the manual set of instructions used until Build 5 to install portal.
*OR*

Application Server 9.1

WARNING: The Text field values are not validated in B6, please double check all entered values

Run $PSBUILD/image/build/PS7.2_<os>_<cpu>/installer where <os> is Solaris or Linux and <cpu> is sparc or x86
If JAVA_HOME is not set, then the installer will prompt for the jdk directory. Optionally the installer may be called with the -j option e.g ./installer -j /usr/jdk/instances/jdk1.5.0
The installer will bring up the
- Welcome and License panel
- System Resources - patch, memory requirements. Please ignore warnings for B6
- Install Home - Set the portal install directory. Default is /opt
- Configuration Mode - Choose configure now or configure later
- AM|DS Panels - AM-SDK Configuration Panel - Enter AM Server information.
  - Host
  - Port
  - Password
  - Cookie Domain
  - Encryption password
  - LDAP Password
- DS Sub-Panel
  - DS Host
  - Directory Manager Password
  - Root Suffix (please double check this)
  - Directory Manager DN
- WebContainer^? Admin Server Panel - Local Container values
  - Host - Default is localhost, please change it to hostname.domainname
  - AS location - Default value is set to /opt
  - Admin User
  - Admin Password
  - Master Password
  - Admin Port - Default is 4848
  - Admin Protocol - Default https - WARNING should be changed to http on Glassfish
  - Note: For Glassfish Admin Protocol should be http
- SRA
- SRA Gateway
- Accept defaults. Enter log user password
- SRA Netlet Proxy
- SRA Rewriter Proxy
- Accept most default values
- Portal Server has 3 subpanels PS|Portal|DeployInstance - PS
  - Host
  - Domain
  - User
  - Group
- Portal Subpanel
  - PortalID^? - Default is portal1
  - SearchID^? - Default is search1
  - URI - Default is /portal
  - Instance ID - instancename
  - DeployURL^? - Default is host^?:8080
- DeployInstance^? Subpanel (WebContainer^? Instance information) - Accept defaults
  - Container Instance Config Directory - Change default value for Glassfish
  - Instance name - server
  - Docroot - Default is /opt/SUNWappserver/appserver/docroot - Change default value for Glassfish
- Ready to Install
- Progress
- Summary - Should display 'COMPLETE'
Restart container and access /portal/dt
Portal install logs are at /var/opt/SUNWportal/logs/install
Portal config logs located at /var/opt/SUNWportal/logs/config * Configure samples if required http://wiki.java.net/bin/view/OpenPortal/PortalInstallInstructions^?
Checkout the latest Sample Portals at http://server:port/portal/dt
Configure portal add-on features such as
Mirage / CMS portlet
SGD portlet^?
SAW / JCAPS Portlet

Glassfish

Same instructions as on AS91 except that the default locations for Glassfish, instance config directory have to be changed and Admin Protocol should be http

Install sample portals

Copy PortalServer-base/SUNWportal/samples/portals/shared/input.properties.template to /tmp/input.properties. NOTE: You can copy the input.properties file to any directory. The input.properties file and the password.properties file must, however, exist in the same directory.
Edit the input.properties file and replace the tokens that begin and end with "%".
Copy PortalServer-base/SUNWportal/samples/portals/shared/password.properties.template to /tmp/password.properties.
Edit the password.properties file and replace the tokens that begin and end with "%".
Run /usr/sfw/bin/ant -buildfile PortalServer-base/SUNWportal/samples/portals/build.xml -Dconfig.location=/tmp -logfile /tmp/log-file.txt to install all the samples (enterprise, sandbox, welcome). NOTE: -logfile is optional.

PS-AM separated Installation

Note: Please see the limitations section before proceeding

Host 1 - Install AM and DS

Install JES5 GA up to Access Manager: SJSWS7+ DS6 + AM7.1. In the installer, only select AM 7.1 and the web container; everything else is selected automatically. Do not select any of the shared components. Select "configure now" and in the option, select the runtime user for DS to be root.

After the JES installer completes, start the LDAP Server instance and web container instance. Login to the AM console (http://server/amserver/console) as amadmin to make sure that the installation is working to this point.

Host 2 - Install Portal Server

Follow the above Pre-requisites, and steps to install container and portal on a single host.

Integrate with SAW or JCAPS portlet

Create a new java project
Add the saw-api-0.2.jar, saw-impl-jcaps-0.2.jar to the project's classpath for compilation only. If deployment is being carried out on OpenPortal^? then the saw-api-0.2.jar is already in runtime classpath
Make sure that one has the client stubs(WorkflowServiceClient^?.jar) generated out of the workflow service deployed on Sun Java CAPS.
Make sure that javaee.jar is in class path
saw-api-0.2.jar has to be in compile time classpath. If deployment is being carried out on OpenPortal^? then the saw-api-0.2.jar is already in runtime classpath, otherwise one has to bundle the saw-api-0.2.jar as well
saw-impl-jcaps-0.2.jar, WorkflowServiceClient^?.jar need to be bundled along with the application
Add the WorkflowConfig^?.properties and JCAPSWorkflowConfig^?.properties files in the project classpath.
Sample entries for WorkflowConfig^?.properties
- businessProcess = com.sun.saw.impls.jcaps.JCapsWorkflow(This means that we are using JCAPS business process and the implementation class is JCapsWorkflow^?.)
logFileLocation = E:\work\jaw\logs\log.txt(The location where the log file has to be created.)
Sample entries for JCAPSWorkflowConfig^?.properties
- appserverhost =points to the machine where the JCAPS business process is deployed.
appserverport =port on the machine where the JCAPS business process is running.
appserverusername =admin user id and password for the server on which JCAPS business process is running.
appserverpassword =admin user id and password for the server on which JCAPS business process is running.
contextfactory = com.sun.jndi.cosnaming.CNCtxFactory
serviceJndi =jndi name of the deployed JCAPS business process.
ImplementationType.properties is required to run SAW Application when created via Netbeans plugin. The ImplementationType^?.properties should contain the key "ImplementationType=JCAPS"
SAW Implementation for JCAPS can be downloaded here
SAW WorkflowPortlet can be downladed here
Understanding SAW Guide can be found here
Detailed Workflow Portlet guide can be found here
Detailed SAW User guide can be found here

Integrate with Mirage or CMS Portlets

%%(color:#3366ff;)Mirage/CMS integration is available to INTERNAL users in Build 10 %%%

Download and Start Repository (Jackrabbit) Server

Download and Unzip JCR Repository at some convenient location on your system

Delete earlier release repository server.(If any)
Edit config/repository.properties to change REPOSITORY_DIR property
Start repository using run.bat/run.sh

Configuring Glassfish for accessing repository from deployed portlets

Go to appserver's admin console and add a custom JNDI resource.
Set JNDI Name = jcr/Repository ,

ResourceType^?="javax.jcr.Repository"
Factory Class = org.apache.jackrabbit.rmi.client.ClientRepositoryFactory .
Add 2 properties:
- url=rmi://hostA:1101/jackrabbit
- auth=container

Restart Glassfish.

Deploying CMS portlets:

Download and deploy CCD Portlet
Download and deploy Document Library Portlet
Download and deploy Article Creation Portlet
Download and deploy Article Viewer Portlet

CMS-Workflow Integration

Security roles for cms:

Consumer = Read Content
Editor = Read+Edit
Contributor = Read+Add
Facilitator = Read+Edit+Add
Administrator= Read+Edit+Add+Delete

These security roles should be mapped with the AM roles.
Use roleMaps.properties file to assign roles.

Download and deploy DL-workflow portlet

Using Google Gadgets in the Portal

OpenPortal^? now provides support for Google gadgets. Users can browse, search, and add from the Google Gadgets Repository. Users will see a link "Add Google Gadgets" on their portal pages. Clicking on the link will show them a page where they can browse gadgets by categories, or search for gadgets, and add gadgets to their pages.

In order for this feature to work, administrators are first required to configure a Google API key. For the key go to http://code.google.com/apis/ajaxfeeds/signup.html and get a key for your portal URL. To configure the key in the portal,

login to the Portal Console and navigate to "Manage Containers and Channels" section for your portal.
Select the
```
TopLevel [[Global]]
```
DN
Click on "GoogleGadgetContainer" in the left side frame.
In the property sheet on the right side, enter your Google API key in the apiKey property value and click on Save.

The Google Gadgets feature is now ready to use. But users still won't see the "Add Google Gadgets" link on their portal pages. This link can be enabled at the global level, organizational level, role level or at a user level for page containers based on JSPTableContainerProvider^? and AJAXTableContainerProvider^?. This can be done by setting the property "isGoogleGadgetsEnabled" to true from Portal Console for a page container. Setting "isGoogleGadgetsEnabled" to true will automatically display the link "Add Google Gadgets" on the portal page for users with appropriate permissions, who can then click on the link to add gadgets to their pages.

While most gadgets should work, some gadgets will not work because they are inbuilt gadgets that work only in iGoogle. And there are some third party gadgets which are not properly maintained and could be down.