Appendix A: Screenshots

David Bunker for the practical implementation of Sun ONE Portal Server with the Grid Engine Portal code and significant documentation contributions.

Eric Sharakan for adding & documenting (single-sign-on) X-window support to Grid Engine Portal.

Please note that this version of the portal server software has the following hardware and software requirements:

    Hardware
    1 450 MHz UltraSparc II cpu or better
    512 MB of Random Access Memory (RAM)
    1 GB of swap space
    1 GB of disk space

    Software
    A user distribution of either the Solaris 8 or Solaris 9 operating system.

    Solaris 8 requires the following patches:
    109326-03 (or later)
    108434-03 (or later)
    108827-15 (or later)

Since the exact questions that are asked when installing Sun ONE Portal Server vary with the type and version of installation, the following is only a general guide. During the installation of the various components, certain questions are asked repetitively.  Most demo users can take all the defaults except for hostname, sub-domain name, domain name, IP address, organization name and passphrase.  Before starting the installation process, check to ensure that none of the ports that you will specify is being actively used by another software component.  You can do this by executing the command: netstat -na | grep port#.  If a port is already being used, select another one in its place.

For the purposes of this installation guide, it will be assumed that all of the Sun ONE Portal Server components will be installed on a server with a fully qualified name of mercury.sun.com, having an IP address of  129.146.60.220.

What follows is a description of how to install the Directory Server, the Portal Server and the Gateway components of Sun ONE Portal Server individually.  It is also possible (and perhaps simpler) to install all of these components at once by selecting option 4 in the installation script.

Using the pssetup script, first accept the licensing agreement by answering yes to the Do you accept? question. Then install the Directory Server (option 5).  The script may list the default settings that it will use.  Review these parameters and determine whether they are appropriate for this installation.  If any of them need to be specifically defined, then answer no to the Use these settings? question.  Following is an example dialog that will follow if you answer no or if a list of default settings was not proposed by the Portal Server installation script:

  What is the Directory Server base directory?               /usr/ldap
  What is the hostname of this server?                       mercury
  What is the sub-domain name for mercury?                   .
  What is the domain name for mercury?                       sun.com
  What port should be used to access the Directory Server?   389
  What is the Directory Server Administration port?          8900
  What is the root suffix of the directory tree?             o=isp
  What is the directory manager?                             cn=Directory Manager
  What is the organization name?                             GridEnginePortal
  What is the passphrase for this server?                    ********
                                          Again?             ********

The settings you just supplied will then be listed.  Answer yes to Use these settings?.  The Directory Server will then be installed.

Now you can install the Portal Server (option 4 in the pssetup script).  Once again, check the default settings that may be listed by the script and decide whether to accept them or to specify new settings.  If you answer no to the Use these settings? question, or if no settings were proposed by the script, the following example dialog will occur.  Note that for the question on JDK below, the recommended version of JDK is 1.31.1_04.  Using other versions may result in instability or lowered performance.  The dialog for this portion of the installation is as follows:

  Do you want to use an existing JDK?                        n
  What is the installation base directory?                   /opt
  What is the hostname of this server?                       mercury
  What is the sub-domain name for mercury?                   .
  What is the domain name for mercury?                       sun.com
  What is the ip address of mercury.sun.com?                 129.146.60.220
  Run SSL on mercury?                                        n
  What port should be used to access the Portal Server?      80
  What is the organization name?                             GridEnginePortal
  Use an existing Directory Server?                          y
  Use the local Directory Server?                            y
  What is the Directory Server administration port?          8900
  What is the Directory Server base directory on mercury?    /usr/ldap
  What is the root suffix of the directory tree?             o=isp
  What is the directory manager?                             cn=Directory Manager
  What is the Web Server administrator?                      admin
  What is the Web Server Administration port?                8088
  What is the passphrase for this server?                    ********
                                          Again?             ********
  What is the deployment URI?                                /portal
  Install the sample portal?                                 y
  What is the hostname of the gateway?                       mercury
  What is the sub-domain name for mercury?                   .
  What is the domain name for mercury?                       sun.com
  What is the ip address of mercury.sun.com?                 129.146.60.220
  Will gateway be running SSL?                               y
  What port will gateway listen on?                          443
  Will the gateway be using a web proxy?                     n
  What is the name of the gateway profile?                   default

The settings you just supplied will then be listed.  Answer yes to Use these settings?.  If you answered no to the question regarding JDK, a new JDK will then be installed.  Then the Identity Server, the Portal Server and Secure Remote Access support  will be installed.  This process can take 25 to 30 minutes.

Now, the Gateway can be installed (option 1 in the pssetup script).  Once again, check the default settings that may be listed by the script and decide whether to accept them or to specify new settings.  If you answer no to the Use these settings? question, or if no settings were proposed by the script, the following example dialog will occur:

    What is the gateway base directory?                        /opt
  What is the hostname of the gateway?                       mercury
  What is the sub-domain name for mercury?                   .
  What is the domain name for mercury?                       sun.com
  What is the ip address of mercury.sun.com?                 129.146.60.220
  Will gateway be running SSL?                               y
  What port will gateway listen on?                          443
  What is the name of this gateway profile?                  default
  Do you want to create a self-signed certificate?           y
  What is the name of your organization?                     ORGNAME
  What is the name of your division?                         DIVNAME
  What is the name of your city or locality?                 CITYNAME
  What is the name of your state or province?                STATENAME
  What is the two-letter country code?                       US
  What is the password for Certificate Database?             ********
                                                 Again?      ********
  What is the deployment URI?                                /portal
  Start the gateway after installation?                      y

The settings you just supplied will then be listed.  Answer yes to Use these settings?.  Once the installation has completed, you can exit from the pssetup script.

You should check the installation log file for any errors that might have occurred.  This can be done by viewing the setup.log file in the directory:  /var/sadm/install/logs/pssetup-<pid>, where <pid> is the process id under which the pssetup command was executed.  If any errors occurred, reconcile them before continuing.  You can also check the setup.log file in both /usr/ldap/setup and /opt/SUNWam/servers/setup for installation errors.

If, for any reason, you want to de-install Sun ONE Portal Server, follow this procedure:

1. Stop the portal server and gateway by executing: /etc/init.d/amserver stop and /etc/init.d/gateway stop.

2. Execute pssetup and de-install all components.

3. Exit pssetup.

4. Ensure that the following directories have been removed (assuming that /opt is the base directory):
    /opt/SUNWam, /opt/SUNWps, /etc/opt/SUNWam, /etc/opt/SUNWps, /var/opt/SUNWam,
    /var/opt/SUNWps.

5. Ensure that all ports that were being used are no longer active, using: netstat -na | grep port#.

(Experience has shown that the LDAP port (389) is often still active.  If this is the case, first ensure that
the /usr/ldap directory has been removed.  Then execute: ps -eaf | grep slapd to find any processes that
may be waiting for connection to port 389.  Kill any such processes.)

You can then re-install Sun ONE Portal Server following the steps outlined previously.
 

                    http://hostname.sub-domain.domain:port/amconsole

or, for the example being used in this document:

                    http://mercury.sun.com:80/amconsole

 If there is an error, try restarting Sun ONE Portal Server by typing:

                    /etc/init.d/amserver start

Sun ONE Portal Server allows for a variety of authentication methods, including LDAP, Unix, Safeword, RADIUS, etc.  For the purposes of this installation guide, Unix authentication is all that is required.  To configure Sun ONE Portal Server for Unix authentication, perform the following steps from the DSAME console window:

1. From the Navigation pane, click on the organization name (GridEnginePortal).

2. In the pull-down menu of the Navigation pane on the ensuing screen, select Services.

3. The Navigation pane now contains a list of DSAME Configuration Authentication options, including Core, LDAP and Membership.  Click on the arrow to the right of Core.

4. The Data pane will be refreshed to show an Authentication menu with a list of authentication methods.  Select only Unix from this list (de-select any others that had been previously selected).

5. Still in the Data pane, just below the Authentication menu, check the box entitled Dynamic User Profile Creation.

6. Scroll back to the top of the Data pane and click Save.

7. Click on logout at the top right of the overall console window.

8. From a terminal window, logged in as root, restart the portal server and gateway via: /etc/init.d/amserver start and /etc/init.d/gateway start.

You should now be able to login to the portal server via the gateway as follows:

                    https://mercury.sun.com

Normal users will access the portal server and Grid Engine Portal using the gateway.

For the purposes of this guide, it will be assumed that you have logged in successfully using two different user ids: gepuser (typical user) and gepadm (administrative user).  This will be important when Roles are assigned later in this document.

Step 3: Grid Engine Portal Integration Package.

First, download the Grid Engine Portal  installation package here.  The download file is named geportal.tar.gz.  As an alternative, authorized users of the Grid Engine Open Source Project can login to CVS and checkout the latest files in gridengine/gep/glue. Further hints can be found below.  From this directory, the geportal.tar.gz file can be generated as follows:

make distclean
make dist

Next, after carefully reading the license conditions, download the O'Reilly Servlet package - cos-27May2002.zip - (or later version) at http://www.servlets.com/cos.

Now you are ready to install Grid Engine Portal.  The Grid Engine Portal distribution comes with an install.defaults file that contains values for several parameters that are needed for the Grid Engine Portal installation.  The parameter values in this file should be changed (by editing the file) to reflect the actual values for the current installation or the values can be changed during the question and answer dialog that occurs during the installation process.  The parameters defined in the file are (the values inside the parentheses reflect the values suggested in this installation guide):

IPS - the Sun ONE Portal Server root directory (/opt)
IPS_DOMAIN - the Grid Engine Portal domain (GridEnginePortal)
IWS_HOST_INSTANCE - the Sun ONE Web Server host instance (https-mercury.sun.com)
IWS_HOST_VS - the Sun ONE Web Server host virtual server (https-mercury.sun.com)
VNC_ROOT - the VNC root directory (/export/GridEnginePortal/vnc-3.3.5_sparc_solaris_2.5)
APP_HOME - the home directory for Grid Engine Portal applications (/export/GridEnginePortal/apps)

Following is an example installation session.

Finally, set the PATH variable as follows:

                      SGP_PATH=/export/GridEnginePortal
                               PATH=$PATH:$SGP_ROOT/vnc-3.3.5-sparc_solaris_2.5:/usr/openwin/bin
                                export PATH SGP_PATH

[For debugging purposes, the output logs from the VNC software are stored in this user's directory under the hidden directory ".vnc".]

Test the gethomedir script :

                               # $SGP_ROOT/bin/gethomedir $SGP_ROOT username

This should return the following output:

                             /export/GridEnginePortal/workspace/username

To make the Grid Engine Portal channels available to the user the following steps have to be performed.  See also the Screenshots in the appendix.
 

Create the GEPUserRole

1. Login as amadmin to http://mercury.sun.com:80/amconsole as described earlier.
2. Select the organization name (GridEnginePortal) in the Navigation (left) pane.
3. Select Roles in the pull-down menu that appears in the ensuing Navigation  pane.
4. Click New, and on the Data (right) pane, Create Role appears. Enter the name GEPUserRole, enter a description and leave the rest untouched. Finally, press Create, and in the Navigation (left) pane, the new role appears.
5. Click on the link for the new role; choose Users in the GEPUserRole panel and click Add.  In the Data (right) pane a Search form appears. Press Search at the bottom right of the Data pane and add the user that will access Grid Engine Portal user channels by checking the box to the left of one of the default users. Then press Submit. . The selected user is added in the Navigation (left) panel. Make sure that you have selected the correct default user - you want to have created a user role for gepuser.  You can see the user name that was assigned by clicking on the right arrow next to default and then checking the Data (right) pane, which will display the user name. If you chose the wrong default user, you will see the gepadm user name displayed instead of the gepuser name. If this happens, Remove the user and start again. (See the SunONE Portal Server documentation for additional information how to add users to roles and to setup users for the default organization)
6. Click the arrow next to the default user in the Navigation (left) pane and enable Netlet in the Data (right) pane by checking the box next to Netlet under Services (if you plan to use Xvnc). Save your settings.
7. In the GEPUserRole Navigation pane, choose Services and click on the arrow next to Portal Server Configuration -> Desktop. Continue on the right (Data pane) to add the GEPTableContainer to the default Desktop Container. If there is no template available already you might have
   to press Create in the right pane.
   
8. In the Data (right) pane, select Channel and Container Management in the Dynamic section.
9. Select JSPTabContainer in the Container Channels list in the Data pane.
10. In the Channel Management section of the Data pane, select GEPTableContainer in the Existing Channels list.
11. In the Data pane, click Add to place GEPTableContainer  in the Available And Visible list.
12. Click Save in the Channel Management section of the Data pane and then logout in the upper right corner of the overall display.

Create the GEPAdminRole

To create the GEPAdminRole repeat the steps above by replacing GEPUserRole with GEPAdminRole in the description.  The GEPAdminRole should be assigned to user gepadm.

Customize the channels that are displayed for GEPUserRole:

1. Login as amadmin to http://mercury.sun.com:80/amconsole as described earlier.
2. Select the organization name (GridEnginePortal) in the Navigation (left) pane.
3. Select Roles in the pull-down menu that appears in the ensuing Navigation  pane.
4. Click GEPUserRole.
5. In the GEPUserRole panel choose Services and click on the arrow next to Portal Server Configuration -> Desktop.

Continue in the Data (right) pane to add the GEPTableContainer to the default Desktop Container.
6. In the Data (right) pane, select Channel and Container Management in the Dynamic section.
7. Select GEPTableContainer in the Container Channels list in the Data pane.
8. Check the *Admin* channels and Delete them from the list of channels and then logout from the console.

1. Login as amadmin to http://mercury.sun.com:80/amconsole as described earlier.
2. Select the organization name (GridEnginePortal) in the Navigation (left) pane.
3. Select Services in the pull-down menu that appears in the ensuing Navigaion  pane.
4. After the Navigation pane has been refreshed, click on the right arrow next to Desktop under Portal Server Configuration.
5. In the Data (right) pane, select Channel and Container Management in the Dynamic section.
6. Click on Edit to the right of JSPTabContainer under the Container Channels list of the Data pane.
7. Click on Edit to the right of TabProperties in the Properties section of the Data pane.
8. In the Data pane, click Add in the Properties section, choose Collection from the Type pull-down menu and enter GEPTableContainer in the Name box.  Then click Add.
9. Click Edit to the right of GEPTableContainer in the Properties section of the Data pane.
10. Click Add under Properties in the Data pane and then type in the following entries (after finishing each entry, click Add at the bottom of the section, then click Add under Properties to go to the next entry).

Type: string        Name: title           Value: Grid Engine Portal
Type: boolean       Name: removable       Value: true
Type: boolean       Name: renamable       Value: true
Type: boolean       Name: predefined      Value: true
Type: string        Name: desc            Value: Grid Engine Portal Tab
11. Click Save under Properties in the Data pane.
12. Click Save at the top of the Data pane.
13. Click logout at the top right corner of the portal page.

Setup Netlets

1. Login as amadmin to http://mercury.sun.com:80/amconsole as described earlier.
2. Select the organization name (GridEnginePortal) in the Navigation (left) pane.
3. Select Services in the pull-down menu that appears in the ensuing Navigation  pane.
4. Click the arrow under SRAP Configuration -> Netlet.
5. In the Data (right) pane, press Add under the Dynamic section.
6. For Rule Name enter: Xvnc:1

For Encryption Algotithms select Other.
For URL enter: /portal.vnc
For Download Applet check the box and enter: 5801:mercury.sun.com:5801
For Extend Session check the box
For Port - Host - Port remove any entry that is already in the list, then for Client Port, enter 5901, for Target Host(s), enter mercury.sun.com and for Target Port(s), enter 5901.  Then click Add to List.
7. Press Save to save these settings
8. Repeat the steps 1 to 7 by replacing 5801 with 580n and 5901 with 590n, where n is 2, 3, ...n, and then logout as before.

 

 

To use netlets the user profile must have access to Netlets.

• Register as a sunsource.net member
• Join the Grid Engine project as Observer
• Setup the cvs environment for Grid Engine
  with ssh tunneling (inside SWAN a SOCKS enabled ssh version has to be used)
  % ssh -f -x -L 2401:localhost:2401 tunnel@cvs.gridengine.sunsource.net echo hallo
       password: tunnel
  % setenv  CVSROOT  :pserver:<yourusername from registration>@localhost:/cvs
  
  without ssh tunneling
  % setenv  CVSROOT  :pserver:<yourusername from registration>@cvs.gridengine.sunsource.net:/cvs
  
  this applies to both versions
  % cvs login     enter  <yourusername from registration> as username and your corresponding web password
  % cvs co gridengine/gep        if you only need the Grid Engine Portal sources
  % cvs co gridengine               if you want to get the complete Grid Engine source distribution
  
  additional information explaining the concepts and command of cvs can be found under www.cvshome.org 
• To build the distribution package it might be necessary to adjust the paths in gridengine/gep/glue/Makefile to your site
  % make distclean             removes everything
  % make                               rebuilds any changed classes
  % make dist                        creates a new installable geportal.tar.gz package
• The same steps apply for the iPS3 version in the corresponding iPS3 subdirectory
  
  

Appendix A - Screen shots