Previous     Contents     Index     Next     
iPlanet BuyerXpert 4.5 Installation Guide



Chapter 4   Installing BuyerXpert


This chapter describes the tasks needed to install iPlanet BuyerXpert, which you should perform in the following order:



Preparing to Unload the Distribution Media

For some of the installation tasks, you need to work in a temporary directory called a staging area. Extract the contents of the distribution media into this staging area. In the example installation, the staging area is a directory called stage. You can give this temporary area any name that you want.

iPlanet recommends you install the BuyerXpert software behind the firewall.


Note You need approximately 700 MB of available disk space for the staging area.


Your BuyerXpert system package contains CD-ROMs for some of the third-party software. The BuyerXpert software is distributed on one CD-ROM.


BuyerXpert CD-ROM Contents

The following file is on the BuyerXpert CD or is included with the BuyerXpert distribution:

buyerxpert45.tar



Verifying the Database and Server Installations


Make sure you have the following software installed and running:

  • Oracle Server Database 8.1.7 or 9i Standard or Enterprise Edition with interMedia Text (this can be on a separate machine)

  • Oracle Client (if Oracle Database is running on a different machine)

  • iPlanet Web Server (iWS) 4.1, SP9 or higher

  • iPlanet Application Server (iAS) 6.5



Information About Sample Data

During the installation of BuyerXpert, an option to load sample data is available. This sample data is designed to demonstrate various features of BuyerXpert. The sample data includes entries for the Directory Server (LDAP) data storage, as well as the RDBMS data storage. If you choose to include sample data in your installation, the data storage specified is populated with the sample entries.

After you are satisfied with the installation, change the BuyerXpert configuration to point to data storage other than those configured during the sample data installation. These procedures are located in the section, Preparing the Seed Data Storage, located in this chapter. You can now reconfigure the installation to point to this data storage. Also, you can choose to refresh the data storage by cleaning and preparing it with the seed data as described in the previously mentioned section (Preparing the Seed Data Storage).


Sample Data in Directory Server

The sample data in the Directory Server is rooted with a well-known suffix o=iplanet.com. This allows you to use the same Directory Server instance (host:port) for the real data and at the same time keep the sample data separate and away from interfering the real data. When using the real data, you can continue to use the same Directory Server instance and configure BuyerXpert to look at a suffix other than o=iplanet.com as the search root. To use the sample data, configure BuyerXpert to use o=iplanet.com as the search root. It is not required to create the o=iplanet.com suffix during installation of the Directory Server. Loading of sample data automatically creates it.


Sample Data in Oracle

The sample data in Oracle is loaded into the user tables for the specified Oracle database user. When using real data, it is advised to use a different Oracle database SID. This prevents any conflicts with or overwriting or loss of the sample data.

Switching between using the sample data and real data (and vice versa) requires that you only reconfigure the BuyerXpert installation.



Pre Installation Setup for Requisition Archival/Restore


The following sections provide details on setting up, configuring and using the Requisition Archival/Restore feature in BuyerXpert 4.5.


Pre Installation Setup

The Archival implementation in BuyerXpert uses the Global Transaction support available in iPlanet Application Server(iAS) 6.5.


Global Transactions

Global transactions are a set of related operations that must be executed as a unit, though each operation may run in a different process. You can update multiple databases that are distributed over different geographic locations, or update multiple databases of different types (such as Oracle and Sybase) in a single

global transaction. A global transaction typically involves operation on multiple databases.


Running db_setup.sh

iPlanet

Database Connectivity Setup

-------------------------------------------------------------------------

  1. Please enter the iAS installation root directory:

    <IAS_ROOT>

  2. Specify the JDBC driver types to configure:

    • iPlanet Type 2 JDBC Drivers

    • Third Party JDBC Drivers

  3. To accept the default shown in brackets, press the Enter key.

  4. Select the component you want to install ? (1/2) [1]:

    2

  5. Provide following information to configure third party JDBC drivers.

  6. To accept the default shown in brackets, press the Enter key.

  7. Enter the number of Drivers you want to configure ? [1]:

    1

  8. Gather information to configure third party JDBC drivers.

  9. Enter the JDBC Driver name: [Driver1]:

    Archive

  10. Enter Driver Classpath

    For example, /space/nsadmin/817client/jdbc/lib/classes12.zip

    <ORACLE_HOME>/jdbc/lib/classes12.zip

  11. Enter Pooled Datasource Classname

    For example, oracle.jdbc.pool.OracleConnectionPoolDataSource

  12. Enter the XA Datasource Classname (optional)

    For example, oracle.jdbc.xa.client.OracleXADataSource


Enable Global Transactions in IAS

The Global Txns are enabled through the ksvradmin utility. This is found in <IASHOME>/ias/bin. Before running it, ensure that your DISPLAY environment is properly set.

The following screen image of ksvradmin shows how to enable Global transactions.




Verify the configuration details

From the ksvradmin utility you can check that all the data that you entered during db_setup.sh is correct. The following screen shows where to check:



Make sure that the changes are correct. If they are not correct, you can make the changes in kregedit in the following location:

Software\iPlanet\Application Server\6.5\CCSO\DAE3\Drivers\<DRIVER_NAME>

The following screen shows the location.





Installing BuyerXpert Software



Note When you install BuyerXpert, you must use the same UNIX user and group that you used to install iAS.


To install the SellerXpert software from the CD:

  1. Copy the buyxpert45.tar file to a local directory.

  2. Extract the file: tar xvf buyerxpert45.tar

  3. Execute setup.

    Make sure that the DISPLAY environment is set correctly.

    The Welcome screen displays.

Figure 4-1   

Welcome screen

  1. Read the Welcome message.

  2. Click the Next button to continue the installation.

    The Software License Agreement screen displays.

Figure 4-2    Software License Agreement screen

  1. If necessary, increase the window size to make the entire agreement visible.

  2. Review the agreement.

  3. Click the Yes (Accept License) button to accept and continue the installation.

    The Select Type of Install screen appears.

Figure 4-3   

Select Type of Install screen (with Typical option selected)

  1. Select the Typical installation.

Figure 4-4    Select Type of Install screen (with Custom option selected)

  1. Or select the Custom installation option that uses default values to create schemas in the Oracle database for OMS, Auctions, RFx, and so forth, and that allows you to specify the Oracle tablespace options.


    Note
    • If you are familiar with the Oracle database, select a Custom installation that provides options to customize the Oracle schema creation to your requirements.

      The Custom installation allows you to specify the Oracle tablespace options. These page options appear later in this installation.


  2. Click the Next button to continue the installation.

    The Installation Directory screen appears.

Figure 4-5    Installation Directory screen

  1. Enter the iPlanet Application Server Directory name where you want to install BuyerXpert (for example, /export/IPM6). This is typically the directory where the iAS server is located (IASROOT).

    Or, select the Browse... button to search for a new location to install BuyerXpert.

  2. Click the Next button to continue the installation.

    If you enter an existing directory that contains the iPlanet Application Server, the following warning appears after you click the Next button informing you of the existing directory.

Figure 4-6   

Warning screen

  1. Review the components list.

  2. Click the Accept button to continue the installation.

    The installer creates an iPlanet BuyerXpert directory in the specified location and places iPlanet BuyerXpert underneath it.

    The Select Components screen displays.

Figure 4-7    Select Components screen

This page displays the size of the BuyerXpert component.

The BuyerXpert software is installed by default.

  1. Click the Next button to continue the installation.


    Note If there is not enough disk space on the system, a warning message displays.

    In this case, exit the installation and provide enough disk space before installing the BuyerXpert software.


    The Domain Name screen displays.

Figure 4-8    Domain Name screen

  1. To find the hostname and domain name, type hostname or domainname at the UNIX prompt.

  2. Enter the domain name in the following format:

    <hostname>.<domainname>

    For example, colonial.red.iplanet.com.

  3. Click the Next button to continue the installation.

    The User Configuration screen displays.

Figure 4-9    User Configuration screen

  1. Enter the User ID.

  2. Enter the Group ID.

    The user and group IDs should be exactly the same as the user and group IDs that you specified during the iAS installation.

    You can type id at a UNIX prompt to find out your current user and group ID.

  3. Click the Next button to continue the installation.

    The Application Server Administrator and Port Number screen displays.

Figure 4-10    Application Server Administrator and Port Number screen

  1. Enter the Administrator User ID.

    This is the same Administrator User ID that you specified during the iAS installation.

  2. Enter the Admin Password.

    This is the same Admin Password that you specified during the iAS installation.

  3. Accept the default for the Admin Port Number.

    This is the same Admin Port Number that you specified during the iAS installation.

  4. Click the Next button to continue the installation.

    The Encryption Password screen appears.



  5. Enter the encryption password for encrypt/decrypt property file entries and other sensitive data.

  6. Enter the password again to confirm.

  7. Click the Next button to continue the installation.

    The Oracle Connection Configuration screen displays.

Figure 4-11    Oracle Connection Configuration screen

  1. Enter the Oracle SID.

  2. Enter the hostname

  3. Enter the port number

    These values can be found in the tnsnames.ora file in the ORACLE_HOME directory.

  4. Click the Next button to continue the installation.

    The JDBC Connect Sring screen appears.

Figure 4-12   

JDBC Connect String screen

  1. Enter the Oracle user to be created for the buyer.

  2. Enter the Oracle password to be created for the buyer.

  3. Enter the Oracle user to be created for the Catalog Manager DB.

  4. Enter the Oracle password to be created for the Catalog Manager DB.

  5. Click the Next button to continue the installation.

    The LDAP Connection Configuration screen displays.

Figure 4-13   

LDAP Connection Configuration screen

  1. Enter the LDAP hostname.

  2. Enter the LDAP port number

  3. Enter the LDAP root DN.

  4. Enter the LDAP username.

  5. Enter the LDAP password.

    These configurations were specified during the creation of the iDS instance.

  6. Click the Next button to continue the installation.

    The Would you like to set up Archival screen displays.

Figure 4-14   

Would you like to set up Archival screen

  1. Select Yes if you want to set up PO archival.


    Note If you choose to install the Requisition Archival feature, it is installed during the BuyerXpert 4.5 installation.

    The installer can create the BuyerXpert schema in the target database, if you choose that option.

    The target database should also be prepared to be a BuyerXpert database (for example, you should be able to do an sqlplus to the SID as a system/manager).

    The following seven screens only appear if you select the Yes option to set up for archival.


  2. Click the Next button to continue the installation.

    The Specify Source JDBC Connection screen displays.

Figure 4-15    Specify Source JDBC Connection screen

  1. Enter the JDBC user name.

  2. Enter the JDBC password.

  3. Enter the Oracle SID.

  4. Enter the TNS name.

  5. Click the Next button to continue the installation.

    The Specify Target JDBC Connection screen displays.

Figure 4-16    Specify Target JDBC Connection screen

  1. Enter the JDBC user.

  2. Enter the JDBC password.

  3. Enter the Oracle SID.

  4. Enter the TNS name.

  5. Click the Next button to continue the installation.

    The Specify Driver Name, System User and Password screen displays.

Figure 4-17    Specify Driver Name, System User and Password screen

  1. Enter the driver name that is to be used with the XA connection.

  2. Enter the Oracle system user.

  3. Enter the Oracle system password.

    If you have to run db_setup.sh before this step, enter the name of the driver that you gave when you ran db_setup.sh.

    Otherwise, remember the name that you provide here and provide the same name when running db_setup.sh).

  4. Click the Next button to continue the installation.

    The PO Archival Sys User and Password screen displays.

Figure 4-18   

PO Archival Sys User and Password screen

  1. Enter the Oracle source db sys user name for transaction support.

  2. Enter the Oracle source db sys password for transaction support.

  3. Enter the target db sys user for transaction support.

  4. Enter the target db sys password for transaction support.

  5. Click the Next button to continue the installation.

    The Oracle PO Archival Objects Configuration screen displays.

Figure 4-19   

Oracle PO Archival Objects Configuration screen

For a Typical installation:

  1. Verify the Oracle target module user.

  2. Enter the password.

  3. Enter the location of the Oracle datafile directory.

  4. Verify the datafile file name.

  5. Verify the data tablespace name.

  6. Verify the data tablespace file size.

  7. Enter the location of the Oracle indexfile directory.

  8. Verify the indexfile directory file name.

  9. Verify the index tablespace file name.

  10. Verify the index tablespace file size.


    Note
    • For a Custom installation, you can modify the Oracle data and index tablespace name and size, and the location of the datafile.

    • In a Typical or in a Custom installation, if a datafile location is not specified, Oracle uses the default directory location of ORACLE_HOME/dbs.


  11. Click the Next button to continue the installation.

    The Target Schema screen displays.

Figure 4-20    Target Schema screen

  1. Select Yes if you want to create schema data on the target database.


    Note If you select Yes, by creating schema data, the activated requisition is overwritten.


  2. Click the Next button to continue the installation.

    The Attachment Directory screen displays.

Figure 4-21   

Attachment Directory screen

  1. Enter the location of the attachment directory.

  2. Click the Next button to continue the installation.

    The Sample Data screen displays.

Figure 4-22    Sample Data screen

  1. Select No if you do not want to populate the Oracle and LDAP data sources with sample entries.

  2. Or, Select one of the following:

    • LDAP Only (to populate the LDAP sample data only)

    • Oracle Only (to populate the Oracle sample data only)

    • LDAP and Oracle (to populate both the LDAP and the Oracle sample data)

  3. Click the Next button to continue the installation.

    • If you select either No Sample Data (option #0) or LDAP Only (option #1), proceed to the Actuate Report Server screen.

    • If you select either Oracle Only (option #2) or LDAP and Oracle (option #3), the following 13 screens display.

    • If you select either Oracle Only (option #2) or LDAP Only (option #3), a warning message displays.



      The message advises that populating sample data will delete any existing iPlanet BuyerXpert Oracle schema and data, and you are prompted to choose whether or not you would like to proceed.

      The installer recreates the users and tablespaces that you specified earlier, and that you specify in the next 12 screens.

  4. Click Continue to continue with the installation.

    The Oracle Installation Configuration screen displays.

Figure 4-23   

Oracle Installation Configuration screen

  1. Enter the network service name.

  2. Enter the system username.

  3. Enter the system password.

  4. Enter the location of the Oracle home directory.

  5. Click the Next button to continue the installation.

    The Oracle Buyer Objects Configuration screen displays.

Figure 4-24   

Oracle Buyer Objects Configuration screen

  1. For a Custom installation:

    You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

    If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Enter the Oracle module username.

  3. Enter the location of the Oracle datafile directory.

  4. Enter the location of the Oracle indexfile directory.

  5. Enter the password.

  6. Click the Next button to continue the installation.

    The Oracle Common Objects Configuration screen displays.

Figure 4-25    Oracle Common Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the cmn user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle Community Objects Configuration screen displays.

Figure 4-26   

Oracle Community Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the com user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle Catalog Objects Configuration screen displays.

Figure 4-27   

Oracle Catalog Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the cat user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle Pricing Objects Configuration screen displays.

Figure 4-28    Oracle Pricing Objects Configuration screen

  1. Click the Next button to continue the installation.

    The Oracle ESV Objects Configuration screen displays.

Figure 4-29    Oracle ESV Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the esv user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle OMS Objects Configuration screen displays.

Figure 4-30   

Oracle OMS Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the oms user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle Auction Objects Configuration screen displays.

Figure 4-31   

Oracle Auction Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the auc user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle RFx Objects Configuration screen displays.

Figure 4-32   

Oracle RFx Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the rfx user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Oracle Exchange Objects Configuration screen displays

Figure 4-33    Oracle Exchange Objects Configuration screen

  1. For a Custom installation:

    • Enter the password for the exc user.

    • You can modify the Oracle user, data and index tablespace name and size, and the location of the datafile.

      If no datafile location is specified, Oracle uses the default location, ORACLE_HOME/dbs.

  2. Click the Next button to continue the installation.

    The Actuate Report Server screen displays.

Figure 4-34    Actuate Report Server screen

  1. If you do not want to setup Actuate reports, proceed to Ready to Install, Click the Next button to continue the installation..

  2. Select Yes if you want to setup Actuate reports.

  3. Click the Next button to continue the installation.

    The Actuate Report screen displays.

Figure 4-35    Actuate Report screen

  1. Enter the location of the Actuate Reports directory.

  2. Enter the Actuate URL.

  3. Enter the Actuate password.


    Note The Actuate Reports directory, URL, and password were specified during the Actuate Reports installation.


  4. Enter the iWS URL.

  5. Click the Next button to continue the installation.

    The Ready to Install screen displays.

Figure 4-36   

Ready to Install screen

  1. Click Install Now.

    The Installing... screen displays.

Figure 4-37   

Installing... screen

Installation is in progress.


Note The Installation Progress bar displays 100% before installation is complete (this is a known problem).

Click Stop if you want to cancel the installation before it is complete.


The Installation Summary screen displays.

Figure 4-38    Installation Summary screen

The installation is complete in approximately 45 minutes.

If the installation is successful, the Status displays Installed.

If the installation is not successful, the Status displays Failed.

The installation log is in /tmp/BX45install-<username>.

Click Exit to exit the installer.



Post Installation Configuration for PO/Requisition Archival


The following configurations need to be done after the BuyerXpert 4.5 installation for Archival.


PM Related Configuration for Archival

This step needs to be done only after you have configured Process Manager for BuyerXpert 4.5 Installation. This step creates workflow related tables in the target database.

cd <IASROOT>/buyer/admin/config/archive

./archive_pm.sh

-p <PM_USER_CONN_STRING_FOR_SOURCE>

-s <SYSTEM_USER_CONN_STRING_FOR_TARGET>

-t <DATA_SEGMENT_FOR_TARGET>

-i <INDEX_SEGMENT_FOR_TARGET>

-c creates PM Schema on Target

For example, ./archive_pm.sh -p procmgr/procmgr@BX -t system/manager@TARGET -t TS01 -i TS02 -c


Configuring Actuate for BuyerXpert

  1. The Setup Actuate Reports screen displays.

    Enter N if you do not want to configure Actuate with BuyerXpert at this time.

  2. Enter Y if you want to configure Actuate with BuyerXpert at this time.


    Note Actuate must be installed prior to installing BuyerXpert.


    If you entered Y in the previous screen, the Report Server screen displays.

  3. Enter the path where Actuate is installed.

  4. At the next screen, enter the Actuate Server URL.

  5. The Actuate Administrator Password screen displays.

    Enter the Actuate administrator password.

    Allow approximately 30 minutes for BuyerXpert to complete the installation.


Creating Catalogs in Catalog Manager

To create catalogs in Catalog Manager:

  1. Enter the URL:

    http://hostname:port/NASApp/buyer/iMM/imm.jsp

  2. The Login screen displays.

Figure 4-39    Login screen

  1. To enter the sample catalog data, enter the following information:

    • Company ID: buyercompany

    • Username: kevin

    • Password: kevin

    If the company is a buyer and a seller company, the Buyer/Seller login screen displays.

Figure 4-40    Buyer/Seller Login screen

  1. Select one of the following roles:

    • Seller

    • Buyer

    The Catalog : Select a Catalog screen displays.

Figure 4-41    Catalog : Select a Catalog screen

  1. Click Catalog from the menu bar.

    The Browse option displays in the submenu.

Figure 4-42    Browse Option (sub-menu option)

  1. Click Browse.

    The Catalog : Select a Catalog screen displays with a list of existing catalogs.

Figure 4-43    Catalog : Select a Catalog screen

  1. Click a Catalog Name.

    The Catalog : Browse Catalog page appears.

  2. If necessary, click the Return to Catalogs button.

    The Catalog : Select a Catalog page appears.

  3. Click the Create button.

    The Catalog : Create Catalog page appears.

  4. Enter a catalog name.

  5. Click Next.

  6. Enter a brief Catalog Description to provide notes that describe the catalog contents.

  7. Select a company.

    Select catalog categories for this catalog view.

  8. Select a user group for accessing this catalog.

    Verify the configuration.

  9. Confirm

    Bring up this catalog to online mode from offline.


Creating Membership Indexes

For membership performance improvements, you need to create the following indexes in your membership Directory Server if they do not already exist:

iplanetecguild

iplanetecparentorgguid

uid

sn

cn

ou

o

displayname

  1. To create indexes, you need to run startconsole from the iAS home directory.

    % ./startconsole

  2. The console screen displays.



  3. Enter the administrator password you gave when you installed Process Manager.

  4. Click OK.

  5. Double click the Directory Server that you created under the Server Group.



  6. Select the Configuration tab.



  7. Highlight Database, located on the left side.

  8. Click Add Attribute.



    The Select Attribute window displays.



  9. Select iplanetecguid.

  10. Click OK.

    The attribute name iplanetecguid appears under the Addition Indexes column and attribute Equality and Presence is checked.



  11. Add the other attributes by repeating the previous steps.

  12. Click Add Attribute to add all these attributes:

    iplanetecparentorgguid

    uid

    sn

    cn

    ou

    o

    displayname

  13. Click Save.

  14. Restart the server.



Running the Process Builder

To deploy a sample application:

  1. Run the Process Builder:

    % IAS_ROOT/builder/Builder.sh &

    The Process Builder screen displays.



  2. Click Import.

    The Import Application window displays.



  3. Enter the zip file location.

    For example, IAS_ROOT/buyer/sample_data/workflow/bx40_buyercompany_prototype_ req.zip

  4. Click OK.

  5. The cluster that you just set up displays on the left side of the screen.



  6. Double click the bx40_buyercompany_prototype file name on the left side of the screen.

    The Inspector screen displays.



  7. Verify that the corporate directory contains the correct machine name.

    If not, click the side arrow button.



  8. Select Choose Your Corporate User Directory.

  9. Click OK.

  10. Close the Inspector screen.

  11. Click Save.



  12. Click Deploy (in the row of buttons near the top of the screen).

  13. Select the cluster by clicking No Cluster Selected.

    The drop down menu displays with the cluster that you previously created.



  14. Enter your iAS user ID.

  15. Enter your iAS password.

  16. Click OK.

    The Successful Deployment screen displays.

  17. Go to the browser and enter the following URL:

    http://hostname:iwsport/Express.npm

  18. Click the New Process tab.

    The name of the application that you just deployed displays.



Importing Timecard Application

  1. Run the Process Builder again:

    IAS_HOME/builder/Builder.sh



  2. Click Import.

    The Import Application from ZIP File screen displays.



  3. Enter the zip file location.

    For example, IAS_ROOT/buyer/sample_data/timecard/bx40_buyercompany_prototype_ tc.zip

  4. Click OK.



  5. The cluster that you just set up displays on the left side of the screen.

  6. Double click the bx40_buyercompany_prototype file name, located on the left side of the screen.

    The Inspector screen displays.



  7. Verify that the corporate directory contains the correct machine name.

    If not, click the side arrow button.



  8. Select Choose Your Corporate User Directory.

  9. Click OK.

  10. Close the Inspector screen.

  11. Click Save.



  12. Click Deploy (located in the row of buttons near the top of the screen).

    The Database Table name must be changed from the previous deployment.

  13. Click the Database Table field.

  14. Enter a new name for the timecard deployment.

  15. Select the cluster by clicking No Cluster Selected.

    The drop down menu displays with the cluster that you previously created.

  16. Click OK.



  17. Enter your iAS user ID.

  18. Enter your iAS password.

  19. Click OK.

    The Successful Deployment screen displays.

  20. Go to the browser and enter the URL:

    http://hostname:iwsport/Express.npm

  21. Click the New Process tab.

    The name of the application that you just deployed displays.

    The BuyerXpert software installation is complete.



Preparing the Seed Data Storage

You need to install seed data for BuyerXpert to work properly. If your BuyerXpert installation points to data stores populated with sample data, you do not need to install any seed data. Sample data includes the required seed data.

The procedures to install seed data consist of the following steps:

  • Preparing the Directory Server data storage

  • Preparing the Oracle data storage

  • Loading the application seed data


Preparing the Directory Server Data Storage

Before you can install seed data, you need to prepare the Directory Server data storage.

  1. Create a new instance of Directory Server (see Chapter 3, Creating an iPlanet Directory Server (LDAP) Instance, for instructions).

  2. Set the directory root.

    For example:

    o=iplanet.com.

  3. Modify the schema on the Directory Server by one of the following two methods:

    • Include the schema files.

    • Pick your favorite path for these configuration files, located in your BuyerXpert installation directory:

      path to ias/buyer/sample_data/directory_ldif/buyer/iplanet.

      For example:

      /iAS/iPlanet/iPM6/buyer/sample_data/directory_ldif/buyer/iplanet.

    • Include lines similar to those shown below in the

      slapd-instance/config/ns-schema.conf file:

      include path/iplanet-userx-schema.conf

      include path/iplanet-ecommerce-schema.conf

      include path/iplanet-vortex-schema.conf

      include path/iplanet-buyer-schema.conf

    • After these changes to the ns-schema.conf file, restart the Directory Server:

      % slapd-instance/restart-slapd

    • Apply schema modifications specified in the ldif file format.

      Include the schema files:

    • Use the schema.ldif file, located in your BuyerXpert installation directory:

      path to ias/buyer/sample_data/directory_ldif/buyer/iplanet/schema.ldif.

    • Load the schema into a running Directory Server using ldapmodify as:

      # ldapmodify -h host -p port -c -a -D dirMgr -w password\

      -f ./schema.ldif

  4. To load seed data use the loadSeedData script located in the BuyerXpert installation directory:

    path to ias/buyer/sample_data/directory_ldif/buyer/iplanet

    For example:

    /iAS/iPlanet/iPM6/buyer/sample_data/directory_ldif/buyer/iplanet

  5. Run the script loadSeedData.sh:

    # loadSeedData.sh hostname port root_dn bind_dn bind_password ias_root_dir

    Or, you can run the script with an additional parameter of WITH_SCHEMA:

    # loadSeedData.sh hostname port root_dn bind_dn bind_password \

    ias_root_dir WITH_SCHEMA


Preparing the Oracle Data Storage

To prepare the Oracle data storage:

  1. Create your database account

    First verify that you have tablespace to do this.

  2. Verify that iAS has stopped:

    IAS-ROOT/ias/bin/KIVAes.sh stop

  3. Run the create_schema.sh script.

    This script does the following:

    • Creates user accounts

    • Creates all the tables/indexes in the user accounts

    • Loads the seed data for the whole application, including the iPlanet MarketMaker catalog piece

  4. Before running the script, read the following notes:


    Note
    • This script should be run after installation of the product.

    • Do not start the application.

    • This script tries to drop the user if the user already exists.

    • Drop the corresponding user manually before running this script.

    • The tablespace must have already been created before running this script because it uses the tablespace to store all the data.


  5. This script uses the following syntax:

    create_schema.sh parameters [ CONNSTR ]

    CONNSTR — Oracle connect string of the format user/passwd@dbsource

  6. Valid parameters for this script are:

    -b BX_DATA — populate BuyerXpert data only, does not load catalog name

    -r IASRoot — IAS base directory, for example, /export/IAS60/

    -u USER/PASSWORD— Oracle user login and password

    -s SYSTEM USER/PASSWORD— Oracle system user and password

    -d DBSOURCE — Oracle database access name

    -o ORACLE_HOME — Pass this if you want to override the ORACLE_HOME environment variable.

    -t DATA TABLESPACE — data tablespace to be used for the user

    -i INDEX TABLESPACE — index tablespace to be used for the user

    For example:

    cd /export/netscape/server4/buyer/sample_data/impexp_files/

    . /create_schema.sh -r /export/netscape/server4/ -u bx/bx -d deepc -s system/manager -o $ORACLE_HOME -t TS01 -i TS02

    where:

    /export/IAS60/ is the IAS Root , bx is the account to be dropped or created (the schema and data are loaded into this), deepc is the Oracle database instance name, and TS02 is the tablespace in the Oracle data.

  7. The script can be found at:

    IAS-Root/buyer/sample_data/impexp_files/create_schema.sh


Loading the Application Seed Data

To load the application seed data, the following tasks are required:

  • Create the install superuser

  • Import the policy book

  • Clean up the install superuser

To create the install superuser in your BuyerXpert installation (without any sample data):

  1. Log in using -/-/- as your organization, followed by login name and password.

  2. Create a dummy organization for the superuser.

    For example:

    InstallOrg.

  3. Create a user with superadmin privileges.

    For example:

    InstallUser.

    These are conveniences to allow administrative privileges in the event that there is no super administrator available.

  4. To import the policy book, start the application:

    KIVAes.sh start

  5. Log in to the Admin interface as InstallUser.

    For example:

    InstallOrg/InstallUser/InstallUser

    (or -/-/- if the database is empty)

  6. Click the Import/Export tab.

  7. Select the files to be imported.

    Multiple files can be imported in the same screen.

  8. Import the following files in the order shown:

    1. IAS-ROOT/buyer/schema/cleardb.imp

      This file clears the policy tables and objects.

    2. IAS-ROOT/buyer/schema/role.imp

      This file imports roles.

    3. IAS-ROOT/buyer/schema/policy.imp

      This file imports policies.

    After the installation is complete and you are satisfied with the data, it is recommended that you delete the InstallUser and InstallOrg.

    Before doing this, verify that you have other users designated as superadmins.


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

Last Updated June 10, 2002