Deploying Lotus collaborative portlets

This topic contains instructions for deploying the collaborative portlets that were shipped with your edition of WebSphere Portal. You can deploy the portlets individually, or you can deploy them all.

The portal administrative interface also provides a way for you to install portlets to make them available to users. For more information on installing portlets, see the topic, Install a portlet and adding it to a page.

Use the IBM Web Administration for iSeries Create WebSphere Portal wizard when configuring WebSphere Portal instances. The wizard creates the necessary servers (HTTP and WebSphere Application Server), configures the server for Portal, configures the database for Portal, configures security (LDAP) for Portal, and deploys the portlets installed with the WebSphere Portal product. You can edit the Portal instance configuration manually after you have used the WebSphere Portal wizard.

 

Before you begin

Before you can run the command to deploy portlets, make sure that WebSphere Portal has started. Do the following:

  1. Start a 5250 session on the machine where WebSphere Portal is installed.

  2. Start the Qshell Interpreter by entering the following on an OS/400 command line: 
    STRQSH

  3. Change to the directory /qibm/proddata/webas5/pme/bin

  4. Enter the following command: 
    serverStatus -instance <instance> <app_sever>

    where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

  5. View the output to determine if your WebSphere Portal server is started. If WebSphere Portal is started, continue to the next step. If the application server is stopped, type the following command: 
    startServer -instance <instance> <app_server>

    6. where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

Deploying all collaborative portlets shipped with WebSphere Portal

Follow the instructions provided to deploy the Lotus collaborative portlets.

  1. Make sure that WebSphere Portal has started. For more information, see Before you begin.

  2. Edit the xmlaccess file.

  3. Verify that the values for the JAVA and WPS_HOME variables contain the correct installation directory paths. To change the values, edit and save the file.

  4. Type serverStatus -all to determine if your WebSphere Portal instance is started.

  5. Change to the WebSphere Portal /bin directory.

  6. Deploy the portlets by entering the following command:

    • xmlaccess.sh -in ../config/work/lccportlets.xml -user <admin_name> -pwd <admin_password> -url <server_name>:<port_number>/<portal_server_context_root>/config

         Where:

    • admin_name is an administrator user name and admin_password is the administrator password.

    • server_name is the name of your Portal Server

    • port_number is the port number used to connect to your Portal Server

    • portal_server_context_root is the context root used to connect to your Portal Server

  7. Restart WebSphere Portal for the changes to take effect. Enter the following commands: 
    stopServer -instance <instance> <app_server>
    
startServer -instance <instance> <app_server>

    where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

Deploying a single collaborative portlet

Use the following instructions to deploy a single collaborative porltet.

  1. Make sure that WebSphere Portal has started. For more information, see Before you begin.

  2. Use a text editor to pen the xmlaccess file.

  3. Verify that the values for the JAVA and WPS_HOME variables contain the correct installation directory paths. To change the values, edit and save the file.

  4. Change to the WebSphere Portal /bin directory.

  5. Deploy the portlet by entering the following command:

    xmlaccess.sh -in ../config/work/xml_file -user <admin_name> -pwd <admin_password> -url <server_name>:<port_number>/<portal_server_context_root>/config

    Where:

    • admin_name is an administrator user name and admin_password is the administrator password.

    • server_name is the name of your Portal Server

    • port_number is the port number used to connect to your Portal Server

    • portal_server_context_root is the context root used to connect to your Portal Server

    • xml_file is the name of the XML file name for the portlet. See the following list to map the file name with the portlet.

      • lcc_domdoc_portlet.xml - Domino.Doc

      • lcc_inotes_portlet.xml - Domino Web Access (iNotes) portlet

      • lcc_lotusds_portlet.xml - Lotus Discovery Server Knowledge Map, Lotus Discovery Server Mini-Search Results, Lotus Discovery Server Search Results

      • lcc_notes_portlet.xml - Notes and Domino

      • lcc_quickappointment_portlet.xml - Quick Appointment

      • lcc_quickemail_portlet.xml - Quick e-Mail

      • lcc_quickplace_portlet.xml - Lotus QuickPlace

      • lcc_quickplace2_portlet.xml - Inline QuickPlace

      • lcc_sametime_portlet.xml - Lotus Sametime Connect

      • lcc_webpage_portlet.xml - Web Page

  6. Restart WebSphere Portal for the changes to take effect. Enter the following commands: 
    stopServer -instance <instance> <app_server>
    
startServer -instance <instance> <app_server>

    where instance is the name of the WebSphere Application Server instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.

 

See also