Chapter 5   Installing Additional Software


Additional software must be installed to operate SellerXpert correctly. Some of this software is not included in the SellerXpert CD and must be purchased separately. See the "Requirements" in Chapter 1 for a list of software included on the SellerXpert installation package.

The following sections are contained in this chapter:

• Installing ECXpert

• Deploying the Portal Channel

• Installing Reuters™ Multi-Currency Live Feed

Installing ECXpert

---

ECXpert handles the exchange of business documents and messages between SellerXpert and legacy systems. The primary ECXpert services used by SellerXpert are data transmission, a variety of communications protocols, and document tracking.

See the ECXpert documentation for installation instructions.

Deploying the Portal Channel

---

All the files related to portal integration have been packaged along with SellerXpert and they will be present in the SERVER_ROOT/seller/seller/BXPORTAL directory, which is referred to as PORTAL_ROOT here, 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 the portal server is installed.

To deploy the SellerXpert portal channel and other functionality, the following steps are required:

• Deploying the Authentication Modules

• Deploying the Channels

• Adding the Channels to the Available Channels List

• Configuring the Portal Server

• Adding the Channels to the User Profile

• Anonymous Logon to Portal and Enabling SellerXpert Channel to Anonymous Portal Users

• Configuring Portal Server URLs for SellerXpert

• Miscellaneous Tips

Deploying the Authentication Modules

SellerXpert integration in portal relies on certain SellerXpert-specific attributes that are set up in the user profile when a new user is created. This changes some of the template files used by the portal authentication module to facilitate creation of the specific attributes. You will need to perform the following steps:

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/config/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. Add a new component for loading buyer-specific attributes for the user during authentication:

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

6. Start up the portal server:

   % cd <portal-server-installation-directory>

   % cd SUNWips/bin

   %./ipsserver start

7. Import the component:

   % cd <portal-server-installation-directory>

   % cd SUNWips/bin

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

If you are successful, the following message displays: Operation Completed Successfully.

To verify success, access the domain that you created after you installed portal server. On the logon page for that domain, click New User. You will see a form with some SellerXpert-specific fields, such as SellerXpert User ID. Complete the form and register. If the submission proceeds correctly, a disclaimer page, or an error, displays on the browser page.

Deploying the Channels

Add the SellerXpert-related channels to the portal server, then configure them as follows:

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

   % cp PORTAL_ROOT/config/sellerxinfo.properties /etc/opt/SUNWips/config

2. Edit the entries in the sellerxinfo.properties file and define all the SellerXpert-related URLs appropriately.
   

   ---

   Note	Create the configuration directory before copying.

   ---

   
   

3. Copy the XML descriptors for the channels:

   % cp PORTAL_ROOT/xml/iwtSSOSellerXProvider.xml

<portal-server-installation-directory>/SUNWips/sample/desktop/xml/

4. Edit both XML descriptors to reflect the location of the properties file using your preferred text editor:

   A. Look for an attribute called fileLocation.

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

   C. Save and close the descriptors.

   
   

   ---

   Note	Keep the sellerxinfo.properties file in /etc/opt/SUNWips/config ONLY.

   ---

   
   

5. Import the XML descriptors using ipsadmin:

   % cd <portal-server-installation-directory>

   % cd SUNWips/bin

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

After importing each of the descriptors, the following message displays: Operation completed succesfully.

6. 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/

7. Edit the jvm12.conf file in the webserver config directory to include the servlet directory in the classpath of the webserver:

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

8. Edit the jvm12.conf file by locating the jvm.classpath variable and appending the following:

   <portal-server-installation-directory>/SUNWips/public_html/servlet:

   <portal-server-installation-directory>/SUNWips/public_html.

Adding the Channels to the Available Channels List

Add the channels to the available channels as follows:

1. Access the portal server admin console by entering the following URL:

   http://<machinename>:<port>/console.

2. Log on 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 windows appear.

5. In the Channel Name text box, type:

   iwtSSOSellerXProvider

6. In the Class Name textbox, type:

   com.iplanet.portalserver.providers.buyerx.SSOSellerXProvider

7. Click Add, then click Submit to update the profile server.

8. Click Logout to log out of the console.

Configuring the Portal Server

Configure the portal server as follows:

1. Verify that the portal server is shut down.

2. Edit the obj.conf of the portal webserver to add a redirect:

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

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

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

Because the portal installation runs on a different web server, all SellerXpert-related images cannot be seen when you do a single sign on through portal. A workaround is to create a link in the portal server docroot directory to the images directory on the SellerXpert web server.

Adding the Channels to the User Profile

Configuration is now complete. Test to see if you can view the channels as follows:

1. Log into the portal as a user by accessing the following URL:

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

   
   

   ---

   Note	If you are a new user, click New User.

   ---

   
   

2. After you log on, select the Content link and add the listed SellerXpert channel.

Anonymous Logon to Portal and Enabling SellerXpert Channel to Anonymous Portal Users

Anonymous logon to portal means you are allowed to enter portal without registering. iPlanet Process Server 3.0 SP2 provides the option to enable the guest entry.

The following link provides the steps for installing SP2:

http://docs.iplanet.com/docs/manuals/portal/30/REL_NOTEiPS3SP2.html

Follow the steps at this link using an anonymous authentication section (which helps you to go directly to the desktop page), then follow these steps:

1. Log on to the portal server as admin at the following location:

   http://<host.domain.subdomain>:port/console)

2. Add the required channel to the anonymous user.

3. Provide the root user ID and password.

4. Click Manage Domains and expand your domain link.

5. Expand the defaultRole link.

6. Expand the application link.

7. Click the desktop link.

8. Add the channel name (iwtSSOSellerXProvider) and classname (com.iplanet.portalserver.providers.buyerx.SSOSellerXProvider) in the respective text fields.

9. Move the added channel to the "Selected Channels" list box.

10. Submit the changes.

11. Log out of admin.

12. Enter portal as an anonymous user. The channels that have been added under the anonymous user displays.

Configuring Portal Server URLs for SellerXpert

As a part of integrating portal server and SellerXpert, SellerXpert needs various URLs of portal server to communicate and transfer information to the portal server.

These URLs are added in the NTV file $IAS_HOME/seller/seller/config/membership/appInfo.ntv. Modify the NTV file by replacing <portalserver-hostname>:<port> with the actual value. After changing the values, the NTV file should be:

"portal" NTV {

"logout" Str "http://buyer04.india.sun.com:8080/DesktopServlet",

"URL" Str "http://buyer04.india.sun.com:8080/servlet/PortalUpdater",

},

Miscellaneous Tips

If both SellerXpert and portal are installed on the same machine, they must have unique port numbers.

If you restart the portal server, it stops the LDAP process of SellerXpert; therefore, you need to explicitly restart the SellerXpert LDAP process.

Installing Reuters™ Multi-Currency Live Feed

---

With this product, 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 can 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, right click click 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 SellerXpert CD $SX_HOME/currconv directory.

1. Contact Reuters to get the license.

2. Configure the 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 the getData.csh script (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 $SX_HOME/billxpert_env.csh (NEED MODIFY FOR SX4.1)

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

   # Please change the values accordingly

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

   setenv DATABASEPROPFILE $SX_HOME/currconv/database.properties

   setenv REUTERS_PROP $SX_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 getData.csh script.

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