> Installation and Upgrade Guide > Installation - Windows

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Installation - Windows

This chapter describes how to install AquaLogic Interaction JSR-168 Consumer on a Windows operating system for use with AquaLogic Interaction.

Before installing, confirm that your system meets the requirements. For details, see Installation Prerequisites.

The installation process includes three steps:

 

Install Files on Remote Server

Follow the steps below to install the JSR-168 Consumer on your remote server (host computer).

  1. Check to see if the PT_HOME variable has been set.
    1. On the desktop, right click on My Computer and select Properties.
    2. Go to the Advanced tab and click Environment Variables.
    3. Look under System Variables for the PT_HOME variable. If the portal is installed on the server, this variable will point to the portal installation folder.
      If the PT_HOME variable exists, make a note of the value and close the window.
    4. If the PT_HOME variable does not exist, click New to create a variable with the following properties: Variable Name: PT_HOME Variable Value: C:\bea\alui
      (The variable can be set to any location if the portal is not installed on the same server. Make a note of the location you enter; it is required in multiple steps below.)
  2. Unzip the jsr-168_java.zip file to the PT_HOME location.
  3. Deploy the PtPortletContainer.war file in the <PT_HOME>/ptjsr168/1.1/webapp folder using the method appropriate for your application server.

 

Configure Remote Server

The steps required to configure the remote server are different depending on the results of step 1 under Install Files on Remote Server above.

If the PT_HOME variable was previously set:

  1. Navigate to the directory referenced by PT_HOME and open pthome.xml in a text editor.
  2. Add the following code within the pthome element (between <pthome> and </pthome>).
    3. Note: Replace <PT_HOME> with the location referenced by the PT_HOME variable (i.e., the portal installation directory). 
    <product name="ptjsr168">
    <install version="1.1">
    <path><PTHOME>/ptjsr168/1.1</path>
    <configpath><PTHOME>/ptjsr168/1.1/settings/config</configpath>
    </install>
    </product>

If you created the PT_HOME variable:

Copy the pthome.xml file from <PT_HOME>/ptjsr168/1.1/settings/config to the root PT_HOME directory.

 

Import Resource Package (Web Services and Portlets)

Follow the steps below to import the JSR-168 Consumer Web Services and Portlets into the portal:

  1. Launch the Migration Wizard (Start | Programs | BEA | Migration Wizard). In previous installations, this utility is found under Start | Programs | Plumtree.
  2. Login as an administrator and click Next.
  3. Choose Import and click Next.
  4. Confirm that the Import object ACLs is the only option selected. Click the choose file button and browse to <PT_HOME>/ptjsr168/1.1/serverpackages/jsr-168.pte. Click Next.
  5. The contents of the migration package will be listed. Click Next, then click Migrate to import the package.
  6. When the migration successful popup appears, click OK to close the Migration Wizard.

After importing the resource package, a JSR-168 folder will appear in portal administration that includes the JSR-168 Remote Server, three Web Services (GooglePortletWebService, RSSPortletWebService and JspPortletWebService), and three portlets (GooglePortlet, RSSPortlet and JspPortlet). These portlets do not require any configuration.

Note: Before placing the portlets on a page, edit the JSR-168 Remote Server object and change the Remote Server URL to the correct address of the host computer.

The RSSPortlet can be edited to add additional RSS files and set proxy settings. The proxy host and port are set in the administrative settings (RssPortlet- Configure this portlet) and the proxy username, password, and domain (if required) are set in portlet preferences. Note that the proxy password is only obfuscated with Base64 Encoding; it is left to the developer to provide encryption.


  Back to Top       Previous  Next