Previous     Contents     Index     Next     
BuyerXpert 4.1 SP3 Installation Guide



Chapter 5   Installing Additional Software


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

The following sections are contained in this chapter:



Installing ECXpert

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

See the ECXpert documentation for installation instructions.



Installing iPlanet Portal


Installing iPlanet Portal consists of the following:


Installing iPlanet Portal Server

  1. To install the Portal Server, log in as superuser:

    % su - root

  2. Unzip the file:

    % gunzip 3.0-fcs-image.tar.gz

  3. Untar the file from the archive:

    % tar -xvf 3.0-fcs-image.tar

    % cd 3.0-fcs-image

  4. To 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; then, that entry is shown at the end of the prompt and in bold.

The Welcome screen displays:

Welcome to the iPlanet Portal Server Installer (domestic release)

The software for the iPlanet Portal Server product will run without a license. However, you must have purchased license from Sun Microsystems to use this product.

Do you accept? Y

The ipsinstall log can be found at:

/var/opt/SUNWips/debug/ipsinstall.log.23639

Checking for software compatibility issues...

Checking java version ...

Checking for required patches ...

WARNING: patch 106409-01 is recommended/required for

JDK 1.2.2 on SunOS 5.6

Required/recommended patch(es) not found. Said patches may or may not apply to your system. Only continue if you are sure they do not apply. Test this by attempting to install them. Please see the iPlanet Portal Server Release Notes for information regarding downloading the patches.

Abort installation? N

Checking for existing 2.0.x installation ...done.

Checking for existing 3.0 installation ...done.

Installation of the iPlanet Portal Server software involves installing the following:

iPlanet Portal Server

iPlanet Portal Server Gateway

They do not need to be installed on the same machine.

Select which component to install:

1) Server

2) Gateway

3) Exit

Choice? 1

Installing the iPlanet Portal Server server...

Do you want to use the default settings? N

What should the root of the role tree be named? iplanet.com

What directory do you want to install the server in? [/opt]: /disk0/portal

You must install one Profile Server for each iPlanet Portal Server install group. Please select whether you'd like to install the Profile server on this machine, or whether this iPlanet Portal Server server should reference a Profile server installed on another host.

Should the local machine be the profile server? [y]/n: Y

What is the host name of the machine where the Profile Server will run? [jupiter1] - specify the name of the machine where the profile server should be installed.

What is the sub-domain name ("." for none)? [red]

What is the domain name? [iplanet.com]

What port should the LDAP server use? [389]

What is the Portal Server super admin user name? [root]

Will/Do you have multiple servers in this install group? y/[n] N

Will/Do you have multiple gateways in this install group? y/[n] N

(Even though the installation asks you for information about the gateway, the gateway will not be installed and it is not needed, so use the default values)

What is the host name of the machine where the Gateway Server will run? [jupiter1]

What is the sub-domain name ("." for none)? [red]

What is the domain name? [iplanet.com]

Should this/these gateway(s) use a web proxy? y/[n] N

What port will the gateway encrypting proxy (eproxy) run on? [443]

Do you want to run SSL between the iPlanet Portal Server Gateway(s) and Server(s)? y/[n] N

What is the Profile Server port? [8080]
Note Do not use the iWS and iAS port numbers here or your BuyerXpert installation may be erased.


What is the Admin Server port? [8888]

The iPlanet Portal Server administration password will be used to manage and install certificates on the gateway and the server, to configure the web and LDAP servers, and to allow secure communication between the gateway(s) and server(s).

Please enter the same password for each server/gateway in this iPlanet Portal Server install group.

iPlanet Portal Server admin password (8 chars minimum): adminadmin

Re-enter iPlanet Portal Server admin password: adminadmin

Do you want to start the iPlanet Portal Server when installation is complete? y/[n] N

You have selected not to start the iPlanet Portal Server.

You will need to start it manually prior to accessing iPlanet Portal Server.

Currently selected settings:

Portal Server : http://jupiter1.red.iplanet.com:8080

Portal Server Gateway : jupiter1.red.iplanet.com:443

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

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

Web Proxy : false

Role Tree Root : iplanet.com

Installation Directory : /disk0/portal

Start Portal Server: n

Are all settings correct? [y]/n Y

Installing packages

SUNWwtsdd...

SUNWwtws...

SUNWwtsvd...

SUNWwtdt...

SUNWwtnm...

SUNWwtnf...

SUNWwtrw...

SUNWwtdoc...

SUNWwtsam...

SUNWwtds...

iPlanet Portal Server has been successfully installed. If you would like to use the Netfile application to access PC's running Win95, Win98 or NT (via SAMBA), install the CD entitled 3rd party software, and run the install_3ps script.

Select which component to install:

1) Server

2) Gateway

3) Exit

Choice? [3] 3

  1. To install the Portal Server Service Pack 1:

    % su - root

    % unzip iPS3.0SP1-01.tar.zip

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

    % cd iPS3.0SP1-01

  2. To start the installation of the Service Pack 1:

    % ./installpatch .

The following screens display as the Service Pack is installed.

WARNING: /usr/sbin/patchadd is being used to install this patch.

Installpatch will be removed from Solaris patches in the next release of Solaris.

Checking installed patches...

Executing prepatch script...

Verifying sufficient file system capacity (dry run method)...

Patch number iPS3.0SP1-01 has been successfully installed.

See /var/sadm/patch/iPS3.0SP1-01/log for details

Executing postpatch script...

updating classpath...

updating domain URL list...

Operation completed successfully.

updating iwtGateway schema...

Operation completed successfully.

updating iwtGateway attributes...

Operation completed successfully.

postpatch processing complete.

Patch packages installed:

SUNWwtds

SUNWwtdt

SUNWwtnf

SUNWwtnm

SUNWwtsdd

SUNWwtsvd

  1. After the installation is complete, start the Portal Server:

    % cd portal-server-installation-directory

    % cd SUNWips/bin

  2. Shut down all the Portal Server related processes:

    % ./ipsserver stop

  3. Start up the Portal Server:

    %./ipsserver start


Adding a New Domain

All the Portal integration related files are included when you install BuyerXpert. They are located in the SERVER_ROOT/buyer/buyer/BXPORTAL directory, shown as PORTAL_ROOT in this document. Since the 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 Portal Server is installed.

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

    http://machinename:port/console

Note that machinename is the name of the machine running portal and port is the port number of the Web Server where portal is running.

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

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

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

  4. Enter the buying company name for the domain name, for example, mercury.com, and Buyer for the Default Role. Click Create.

    The message, Successfully Created New Domain, displays.

  5. Click Continue.

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

  7. Log out from the console.


Adding a New Component

BuyerXpert integration in Portal relies on certain BuyerXpert-specific attributes to be created in the user profile, when a new user is created.

  1. Shut down the Portal Server:

    % cd portal-server-installation-directory

    % cd SUNWips/bin

    % ./ipsserver stop

  2. Backup 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. Backup 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 BuyerXpert specific attributes for the user during authentication:

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

  7. Start up the 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

    The message, Operation Completed Successfully, displays.


Adding and Configuring BuyerXpert Channels

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

  1. Copy the properties file to some location and make sure that is accessible by 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, Directory Server (LDAP) and BuyerXpert settings.

  3. Copy the headerNames.properties file to the same directory as your buyerInfo.properties:

    % cp PORTAL_ROOT/config/headerNames.properties same location as 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/iwtReqStatProfileProvider.xml portal-server-installation-directory/SUNWips/sample/desktop/xml/

    % cp PORTAL_ROOT/xml/iwtInboxProfileProvider.xml portal-server-installation-directory/SUNWips/sample/desktop/xml/

  6. Edit both the XML descriptors to reflect the location of the properties file. Open them in your preferred text editor and look for an attribute called "fileLocation". Change the value for this attribute from /export to the location of the properties file, save and close the descriptors.

  7. Import the XML descriptors using ipsadmin:

    % cd portal-server-installation-directory

    % cd SUNWips/bin

    % ./ipsadmin -import portal-server-installation-directory/SUNWips/sample/desktop/xml/iwtReqStatProfi leProvider.xml

    % ./ipsadmin -import portal-server-installation-directory/SUNWips/sample/desktop/xml/iwtInboxProfile Provider.xml

  8. After importing each of the above mentioned descriptors, the message Operation completed successfully displays.

  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 Web Server by editing the jvm12.conf file in the Web Server config directory:

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

  11. Edit the jvm12.conf file, locate the jvm.classpath variable and append:

    portal-server-installation-directory/SUNWips/public_html/servlet

Add the channels to the available channels list by following these steps:

  1. Access the Portal Server Admin console by entering:

    http://machinename:port/console

  2. Log in as root.

  3. Click the Manage Domains link and select the domain that you created.

  4. Expand the Applications link and select Desktop. The Available and Selected Providers list displays.

  5. In the Channel Name field, type:

    iwtReqStatProfileProvider

  6. For the Class Name text box, type:

    com.iplanet.portalserver.providers.buyerx.ReqStatProfileProvider

  7. Click Add and then click Submit, located at the bottom of the page, to update the Profile Server.

  8. In the Channel Name text box, type:

    iwtInboxProfileProvider

  9. In the Class Name text box, type:

    com.iplanet.portalserver.providers.buyerx.InboxProfileProvider

  10. Click Add to add the channels to the available channels list.

  11. Click Submit, located at the bottom of the page, to update the Profile Server.

  12. Click Logout.


Copying the Required Libraries

  1. Shut down the Portal Server.

  2. Copy the oracle jdbc driver, jdbc jar and the ldapjdk jar from the 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/

    % cp IAS_SERVER_ROOT/ias/classes/java/ldapjdk.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

  4. Include these jar files in the CLASSPATH of the ipshttpd script:

    % cd portal-server-installation-directory/SUNWips/bin

  5. Edit the ipshttpd script, locate the IPS_CLASSES variable and add to the list of jar files:

    lib/classes12.jar:lib/jdbc20.jar:lib/ldapjdk.jar


Configuring the Portal Server

  1. Make sure that the Portal Server is shut down.

  2. Edit the obj.conf of the Portal Server to add a redirect:

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

  3. Add the following line to the obj.conf, right below the Object name=default:

    NameTrans fn="redirect" from="/NASApp/buyer/" url-prefix="http://server name of buyer:port num of buyer/NASApp/buyer/"

Since the Portal installation runs on a different server, all the BuyerXpert related images cannot be seen when you perform a single login through Portal. Create a link in the Portal Server's docroot directory to the images to solve this.


Configuring the iPlanet Web Server

Because of security issues with Javascript, it is necessary to configure the iPlanet Web Server.

  1. Copy the track.html, welcome.html and inbox.html templates to the docroot of the Web Server.

    % 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. Make sure that the entries for bxInboxScreen, bxWelcomeScreen, bxTrackScreen in the buyerInfo.properties file reflect the correct URLs for the three files that you just copied.


Testing Channel Viewing

To test to see if you can view the channels:

  1. Log in to the Portal as a user. If you are a new user, click New User to register:

    http://machine_name:port_number/login?domain=/domain_name

  2. Select the Content link and add the listed BuyerXpert Track Requisitions and the BuyerXpert Approval Inbox channels to the desktop. The channel information is displayed.

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


Testing Single Login

Single login is enabled for every user by default, unless you entered no or false during the new user registration. To test the single login function:

  1. Log in to the Portal and click Edit in the User Information channel in the top left corner of the page.

  2. You will see a section called BuyerXpert Information containing all the relevant settings.

  3. If the value for Enable Single-signon field either says no or false, then the single login has been disabled. Type Y or Yes in this field to enable it.

Single login allows you to log in once to Portal and have access to BuyerXpert data without the additional BuyerXpert login screen displaying.



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 on mouse right 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.1)

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

    # 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 © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated October 04, 2001