Previous     Contents     Index     Next     
iPlanet BuyerXpert 4.5 Installation Guide



Chapter 5   Installing Additional Software


Additional software must be installed to operate iPlanet BuyerXpert correctly. Since some of this software is not included in the iPlanet BuyerXpert CD and must be purchased separately, see "Software Requirements" in Chapter 1 "Planning to Install BuyerXpert" for a list of software included in the iPlanet BuyerXpert installation package.

The following sections are contained in this chapter:



Installing iPlanet ECXpert

iPlanet ECXpert handles the exchange of business documents and messages between iPlanet BuyerXpert and other OBI-compliant systems. The primary iPlanet ECXpert services used by iPlanet BuyerXpert are data transmission, a variety of communications protocols, and document tracking.

See the iPlanet ECXpert documentation for installation instructions.



Installing iPlanet Portal Server


Installing the iPlanet Portal Server consists of the following:


Installing iPlanet Portal Server

  1. Log in as superuser to install the iPlanet Portal Server. You should run the installation as root.

    % su - root

  2. Unzip the distribution.

    % gunzip iPS3.0SP3-01.tar.gz

  3. Untar the distribution from the archive.

    % tar -xvf iPS3.0SP3-01.tar

  4. Start the installation process.

    % ./ipsinstall

The rest of this section documents the screens that are displayed during this installation. The default entries are shown in brackets and are recommended unless a specific entry is necessary, in which case that entry is shown in bold at the end of the prompt.

    • Installation log at /var/sadm/install/logs/ipsinstall.5745/install.log

    • The product runs without a license. However, you must purchase a license from Sun Microsystems to use this product.

  1. Do you accept? [y]/n y

    • Inspecting system.

    • Inspecting network.

  2. What is the subdomain ("." for none)? [red]

  3. What is the domain? [iplanet.com]

    • Inspecting iPS components.

    • Preparing to install.

  4. Select which component to install:

    1) Server

    2) Gateway

    3) Exit

    • Choice? [3] 1

  5. What directory to install in? [/opt] /export/portal

  6. Will this be an open portal install? y/[n] y

  7. Use SSL protocol to the server? y/[n] n

  8. Is this a multiple server install? y/[n] n

    The profile server will run on wellspring.red.iplanet.com

  9. What is the port for the profile server? [8080]

    The directory server will run on wellspring.red.iplanet.com

  10. What is the port for the directory server? [389]

  11. What is the root of the role tree? [iplanet.com]

  12. What is the user for the root of the role tree? [root]

  13. What is the administrator port for the web server? [8088]

  14. What is the passphrase (8 chars minimum) : adminadmin

  15. Re-enter passphrase : adminadmin

    Server settings:

    Installation Directory : /export/portal

    Role Tree Root : iplanet.com

    Role Administrator : root

    Server List : http://wellspring.red.iplanet.com:8080

    Profile Server : http://wellspring.red.iplanet.com:8080

    LDAP Server : wellspring.red.iplanet.com:389

    LDAP Admin Port : 8900

    Web Server Admin Port : 8088

    Start Server : y

  16. Are these settings correct? [y]/n y

When the installation is complete, it is necessary to bring up the iPlanet Portal Server using the following steps:

  1. Start the iPlanet Portal Server:

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

  2. Shutdown all iPlanet Portal Server related processes.

    % ./ipsserver stop

  3. Start up the iPlanet Portal Server.

    %./ipsserver start

This concludes the installation of the iPlanet Portal Server.

Refer to the "Portal Deployment" section of this document for instructions on integrating with iPlanet BuyerXpert.


Adding a New Domain

All the iPlanet Portal Server integration related files are included when you install iPlanet BuyerXpert. They are located in the SERVER_ROOT/buyer/buyer/BXPORTAL directory, shown as PORTAL_ROOT in this document. Since the iPlanet Portal Server runs as root on your system, all of the steps have to be performed as the root user of the system on which iPlanet Portal Server is installed.

  1. To access the iPlanet Portal Server admin console, type:

    http://machinename:port/console


    Note The name of the machine running iPlanet Portal Server is machinename and port is the port number of the iPlanet WebServer where iPlanet Portal Server is running.


  2. Type root as the user name, and the root password of your machine as the password.

  3. After you log in, click the Manage Domains Link on the left panel.

  4. Click Add New Domain, located in the right panel.

  5. Enter the buying company name for the domain name (for example, BuyerCompany) and Buyer for the Default Role.

  6. Click Create.

    You should see the following message:

    Successfully Created New Domain

  7. Click Continue.

  8. Choose the domain that you just created, click Authentication, select Membership from the Authentication Screen and click Submit.

  9. Log out from the console.



Portal Deployment

Portal Deployment consists of the following:


Deploying the Authentication Modules

The BuyerXpert integration in portal relies on certain iPlanet BuyerXpert-specific attributes being created in the user profile when a new user is created. This step changes some of the template files used by the portal authentication module to facilitate creation of the specific attributes, and is therefore a necessary step. You need to go through the following sequence to get this to work:

  1. Shut down your portal server:

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

    % ./ipsserver stop

  2. Back up your existing templates.

    % cd /etc/opt/SUNWips/auth/default

    % mv Membership.properties Membership.properties.orig

    % mv register.html register.html.orig

  3. Copy the new templates from the PORTAL_ROOT:

    % cp PORTAL_ROOT/templates/Membership.properties /etc/opt/SUNWips/auth/default/

    % cp PORTAL_ROOT/templates/register.html
    /etc/opt/SUNWips/auth/default/

  4. Back up the template for UserInfo:

    % cd /etc/opt/SUNWips/desktop/default/iwtUserInfoProvider

    % mv edit.template edit.template.orig

  5. Copy the new template for UserInfo:

    % cp PORTAL_ROOT/templates/edit.template /etc/opt/SUNWips/desktop/default/iwtUserInfoProvider/

  6. Add a new component for loading iPlanet BuyerXpert-specific attributes for the user during authentication.

    % cp PORTAL_ROOT/xml/bxAuth.xml /etc/opt/SUNWips/xml/

  7. Start up iPlanet Portal Server:

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

    %./ipsserver start

  8. Import the component:

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

    % ./ipsadmin -import /etc/opt/SUNWips/xml/bxAuth.xml

    If things go well, you should see the following message:

    Operation Completed Successfully

  9. Edit the /etc/opt/SUNWips/xml/iwtTag.xml file, adding the following lines in the <iwt:Att name="iwtTag-tags" section after the line userConfigurable="TRUE">

    <Val>bxAuth-bxUserName|profile</Val>

    <Val>bxAuth-bxpassword|profile</Val>

    <Val>bxAuth-bxsignon|profile</Val>

    <Val>bxAuth-bxName|profile</Val>

  10. Save.

  11. Import the iwtTag.xml file:

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

    % ./ipsadmin -import /etc/opt/SUNWips/xml/iwtTag.xml

  12. To test what you have done so far:

    1. Access the domain that you created after you installed iPlanet Portal Server.

    2. On the login page for that Domain, click New User.

      You should see a form with some iPlanet BuyerXpert specific fields (for example, BuyerXpert User Id).

  13. Complete the form and register.

    If the submission goes through correctly, a disclaimer page is displayed. Otherwise, an error displays on the browser page.


Deploying the Channels

To add the iPlanet BuyerXpert-related channels to the iPlanet Portal Server and configure them:

  1. Copy the buyerInfo.properties file to some location and make sure that is accessible by the portal.

    % cp PORTAL_ROOT/config/buyerInfo.properties <location accesible to portal server>/

  2. Edit the entries in the buyerInfo.properties file so that you point to the correct database, LDAP, and iPlanet BuyerXpert settings.

  3. The headerNames.properties file contains the field names for the track and inbox channels. It can be customized by the administrator to his or her own choice of field names. Copy the headerNames.properties file to the same directory as your buyerInfo.properties file:

    % cp PORTAL_ROOT/config/headerNames.properties <same location as your buyerInfo.properties>/

  4. Customize the headerNames.properties file if you want the field names in the channels to appear differently.

  5. Copy the XML descriptors for the channels:

    % cp PORTAL_ROOT/xml/iwt*.xml <portal-server-installation-directory>/SUNWips/sample/desktop/xml/

  6. Edit all the XML descriptors to reflect the location of the properties file.

    1. Open the descriptors in your preferred text editor.

    2. Look for an attribute called "fileLocation".

    3. Change the value for this attribute from "/export" to the location of the properties file.

    4. Save.

    5. Close the descriptors.

  7. Import the XML descriptors using the ipsadmin script.

    % cd <portal-server-installation-directory>

    % cd SUNWips/bin

    % ./ipsadmin -import <portal-server-installation-directory>/SUNWips/sample/desktop/xml/<XML FILE NAME>.xml

  8. After importing each of the descriptors, you should see the following message:

    Operation Completed Successfully

  9. Copy the class files to the portal:

    % cp -r PORTAL_ROOT/classes/com <portal-server-installation-directory>/SUNWips/lib/

    % mkdir -p <portal-server-installation-directory>/SUNWips/public_html/servlet

    % cp PORTAL_ROOT/classes/*.class <portal-server-installation-directory>/SUNWips/public_html/servlet/

  10. Include the servlet directory in the classpath of the iPlanet WebServer by editing the jvm12.conf file in the iPlanet WebServer config directory:

    % cd <portal-server-installation-directory>/netscape/server4/https-<webserver>/config

    • Edit the jvm12.conf file, locate the jvm.classpath variable and append <portal-server-installation-directory>/SUNWips/public_html/servlet

  11. Add all of the iPlanet BuyerXpert channels to the available channels list:

    1. Access the iPlanet Portal Server admin console by entering the URL: http://<machinename>:<port>/console.

    2. Log in as root.

    3. Click the Manage Domains link.

    4. Select the domain that you created.

    5. Expand the Applications link.

    6. Select Desktop.

      The Available and Selected Providers list windows appear.

    7. In the Channel Name text box, enter:

      iwtReqStatProfileProvider

    8. In the Class Name text box, enter:

      com.iplanet.portalserver.providers.buyerx.ReqStatProfileProvider

    9. Click Add.

    10. Click Submit to update the Profile Server.

    11. In the Channel Name text box, enter:

      iwtInboxProfileProvider

    12. In the Class Name text box, enter:

      com.iplanet.portalserver.providers.buyerx.InboxProfileProvider

    13. Click Add.

    14. Click Submit to update the Profile Server.

    15. In the Channel Name text box, enter:

      iwtReqTrackProvider

    16. In the Class Name text box, enter:

      com.iplanet.portalserver.providers.buyerx.ReqTrackingProvider

    17. Click Add.

    18. Click Submit to update the Profile Server.

    19. In the Channel Name text box, enter:

      iwtTCTrackProvider

    20. In the Class Name text box, enter:

      com.iplanet.portalserver.providers.buyerx.TCTrackingProvider

    21. Click Add.

    22. Click Submit to update the Profile Server.

    23. In the Channel Name text box, enter:

      iwtInboxTrackProvider

    24. In the Class Name text box, enter:

      com.iplanet.portalserver.providers.buyerx.InboxTrackingProvider

    25. Click Add.

    26. Click Submit to update the Profile Server.

    27. Click the Logout link to logout of the console.


Copying the Required Libraries

  1. Shut down the iPlanet Portal Server server

  2. Copy the Oracle JDBC driver and JDBC jar files from the iPlanet BuyerXpert installation directory to the portal server lib directory

    % cp <IAS_SERVER_ROOT>/buyer/lib/classes12.jar <portal-server-installation-directory>/SUNWips/lib/

    % cp <IAS_SERVER_ROOT>/ias/classes/java/jdbc20.jar <portal-server-installation-directory>/SUNWips/lib/

  3. Expand the classes12.jar that you just copied

    % cd <portal-server-installation-directory>/SUNWips/lib/

    % jar -xvf classes12.jar


Configuring the iPlanet BuyerXpert Webserver

Due to security issues with Javascript, we changed the way content is rendered after a user is authenticated in iPlanet BuyerXpert. So it becomes necessary for us to configure the iPlanet WebServer that iPlanet BuyerXpert uses. This step requires copying some HTML template files to the docroot of the iPlanet BuyerXpert webserver (usually the directory called docs).

  1. Copy the inbox.html, welcome.html and track.html templates to the docroot of the iPlanet BuyerXpert webserver.

    % cp PORTAL_ROOT/templates/track.html <BUYER_WEB_SERVER_DOCROOT>/

    % cp PORTAL_ROOT/templates/welcome.html <BUYER_WEB_SERVER_DOCROOT>/

    % cp PORTAL_ROOT/templates/inbox.html <BUYER_WEB_SERVER_DOCROOT>/

  2. Verify that the entries for bxInboxScreen, bxWelcomeScreen, and bxTrackScreen in the buyerInfo.properties files reflect the correct URLs for the three files that you just copied.


Adding the Channels to the User's Profile

All the required configuration steps have now been completed and you should test to see if you can view the channels as follows:

  1. Log in to the iPlanet Portal Server as a user by accessing the following URL (if you are a new user, click the new user button to set yourself up):

    http://<machine-name>:<port-number>/login?domain=/<domain-name>

  2. Select the Content link and add one or all of the iPlanet BuyerXpert channels to the desktop.

    The channel information is displayed.

If there are requisitions in iPlanet BuyerXpert that you created, or if there are any in your inbox, they are summarized in the appropriate channels.

The thin channels also display iPlanet BuyerXpert-specific information for the user in a much more concise fashion. For example, instead of displaying all the open requisition IDs, the thin channel for Open Requisitions only displays a count of the number of requisitions that are incomplete, pending approval, and so forth.


Testing Single Sign-on

Single sign-on is enabled for every user by default unless "no" or "false" was entered during new user registration.

If you are not sure what your settings are:

  1. Log in to the iPlanet Portal Server.

  2. Click Edit in the User Information channel (top left corner of the page).

    There is a BuyerXpert Information section that contains all relevant settings.

    If the value for "Enable Single sign-on" field is either "false" or "no", then it has been disabled for you.

  3. If you want to change your BuyerXpert settings:

    • Edit the relevant fields.

    • Click Finished.

    If single sign-on has been enabled for you:

    • Click the Requisition ID in the iPlanet BuyerXpert Track Requisition channel to automatically log in to iPlanet BuyerXpert. The Track Requisitions screen displays in a separate browser window.

    • Click the Requisition ID in the BuyerXpert Approval Inbox channel to automatically log in to iPlanet BuyerXpert. The Approval Inbox screen displays in a separate browser window.

    • Click any link in the thin channels to go to its relevant screen in iPlanet BuyerXpert.



Installing Reuters Multi-Currency Live Feed

With the Reuters (TM) multi-currency live feed, you can retrieve prices on multi-instrument and multi-field quote lists in a single request. You send a list of the instruments and the fields to the Reuters Investor portfolio server. The latest available prices for these instruments are returned in XML or HTML format. Optionally, you may specify a single base currency to convert all prices to that currency.

Up to twenty fields may be included in each request. The valid list of fields is included in the Reuters Investor Data Guides. By contract, you may not use any fields not included in the Data Guides.

Features of the multi-currency live feed include:

  • Investor dataset is designed for private investors

  • Lets you integrate Reuters investor data within your own web sites

  • Data delivered from Reuters Geneva or New York web farms through the internet

  • No Reuters hardware or software required

  • Simple-to-use URL syntax for programmers

  • "Ready-to-go" Reuters HTML templates for immediate use

  • "As-you-want" XML for integrating in your own applets

  • Authentication to protect you and Reuters

  • Page-view pricing model


HTML Format

The HTML format is ready for immediate display in a browser. Using stylesheets, you can modify the Reuters default colors to match your web site's style.


XML Format

The XML format is for parsing using your server and reusing in new templates or applets. (To view the XML format in Netscape, select the right frame, click the right mouse button, and select View Frame Source.) You must respect Reuters online branding guidelines.


Before Installing

Your web site and server software that access Reuters Investors must have access to the public internet.

More information can be found at:

http://www.reuters.com/onlinemedia


Installation of Multi-Currency Live Feed

The file is located on Buyer CD $BX_HOME/currconv directory.

  1. Contact Reuters to get the license.

  2. Configure CCLoad.Properties file (sample below):

    ###############################

    # Properties file that sets variables to pull data from Reuters

    ###############################

    currConv.load.PullData.servername=webcache.sfbay.sun.com (PROXY_HOSTNAME_NULL_IF_DIRECT_INTERNET_CONNECTION)

    currConv.load.PullData.serverPort=8080

    currConv.load.PullData.reutersHostname=ri2.rois.com

    currConv.load.PullData.reutersPort=80

    currConv.load.PullData.reutersSession=SESSION_ID

    currConv.load.PullData.reutersFormat=XML

    currConv.load.PullData.reutersRICs=JPYX FX (CURRENCY)

    currConv.load.PullData.outDir=YOUR_OUT_DIR

    currConv.load.CCLoad.CCFFile=YOUR_DIR/euro_fixed_rates.xml

  3. Configure variables in getData.csh file (sample below):

    #!/bin/csh

    ##########

    ################################################################### ###

    # This scripts pulls data from Reuters and populates the currencyconversion table

    # in billerXpert

    ################

    ################################################################

    #########

    # sets JAVA_HOME, LD_LIBRARY_PATH, CLASSPATH

    #########

    source $BX_HOME/billxpert_env.csh (NEED MODIFY FOR BX4.5)

    ######################################

    # Please change the values accordingly

    ######################################

    setenv DATABASEPROPFILE $BX_HOME/currconv/database.properties

    setenv REUTERS_PROP $BX_HOME/currconv/CCLoad.properties

    # Pull data

    $JAVA_HOME/bin/jre com.iplanet.ecomm.currconv.load.PullData $REUTERS_PROP

    # here get the OUTPUTDIR from the properties file.

    setenv OUTPUTDIR `grep currConv.load.PullData.outDir ${REUTERS_PROP} | sed 's/.*=//'`

    # load data

    if ( -d $OUTPUTDIR/.Pulldata ) then

    ${JAVA_HOME}/bin/jre com.iplanet.ecomm.currconv.load.CCLoad $OUTPUTDIR/.Pulldata

    $DATABASEPROPFILE reuter ${REUTERS_PROP}

    else

    echo $OUTPUTDIR

    echo " Data Pull FAILED \!\!\! "

    endif

  4. Verify variable currConv.load.CCLoad.CCFFile, what is euro_fixed_rates.xml file (sample below):

    <?xml version="1.0" standalone = 'no'?>

    <CurrencyConversion>

    <source>Reuters</source>

    <convDate>2000.11.29 11:48:34 GMT+05:30</convDate>

    <Convert>

    <From>EUR</From>

    <To>BEF</To>

    <Factor>40.3399</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>DEM</To>

    <Factor>1.95583</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>ESP</To>

    <Factor>166.386</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>FRF</To>

    <Factor>6.55957</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>IEP</To>

    <Factor>0.787564</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>ITL</To>

    <Factor>1936.27</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>LUF</To>

    <Factor>40.3399</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>NLG</To>

    <Factor>2.20371</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>ATS</To>

    <Factor>13.7603</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>PTE</To>

    <Factor>200.482</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>FIM</To>

    <Factor>5.94573</Factor>

    </Convert>

    <Convert>

    <From>EUR</From>

    <To>GRD</To>

    <Factor>340.750</Factor>

    </Convert>

    </CurrencyConversion>

  5. Run the script getData.csh.

  6. Check the logs.

    The Error logs are kept in /tmp directory (for example, CCLoadErr<date>_<time>.log).


Previous     Contents     Index     Next     
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated June 10, 2002