What scripts are supplied, and what do they do? (Sun B2B Suite eXchange Integrator User's Guide)

Sun B2B Suite eXchange Integrator User's Guide

What scripts are supplied, and what do they do?

eXchange Integrator supplies the file oracle510.zip in the Project Explorer tree under SeeBeyond⇒eXchange⇒Download Scripts. The oracle510.zip file contains a collection of command scripts (.cmd files) and SQL scripts (.sql files).

You install the eXchange Integrator schema on the database by doing one of the following:

Edit setenv.cmd so it reflects your system environment (see Table 2–2), and then run the two other command scripts (see Running Database Scripts to Set Up the eXchange IntegratorDatabase);— or—
Run the SQL scripts directly, supplying system information at run time; see Running Database Scripts to Set Up the eXchange IntegratorDatabase.

Assumptions

The scripts assume they are run on a machine whose command path includes sqlplus. The network\admin\tnsnames.ora file must include a stanza such as the following:

eXchange_myOracleHostname.domain
  (DESCRIPTION =
    (ADDRESS_LIST =
       (ADDRESS =
         (PROTOCOL = TCP)
        (HOST = myOracleHostname)
        (PORT = 1521))
        ...
     ) )
    (CONNECT_DATA =
       (SID = ORCL)
      ...
  ) )

Some scripts and samples assume defaults or supply values as shown in Table 2–2.

Table 2–2 Typical, Default, or Presupplied Values for eXchange Integrator Database Setup


Item	Typical or presupplied value
UserID/password combination for Oracle system	sys/manager or system/manager
Name of eXchange database instance (see Creating and Configuring the eXchange Integrator Database Instance)	eXchange
SID (also called service ID, servicename, or database name)	ORCL (or not presupplied)
TNS name	(not presupplied)
UserID/password for administering the eXchange database	ex_admin/ex_admin
UserID/password for first generic eXchange end user	ex510a/ex510a
UserID/password for second generic eXchange end user	ex510b/ex510b

To extract the scripts

In Enterprise Explorer, in the project tree, expand the following folders: SeeBeyond⇒eXchange ⇒Download Scripts

Right-click oracle510.zip and, on the popup context menu, click Export; then use the Save dialog box to save the file to a local directory, such as C:\JC512\Exported\Oracle510\.

Extract the files in oracle510.zip into this local directory, yielding:
- CleanTrackData.sql
- Cleanup.sql
- cleanup_coreServices_tables.sql
- create_coreServices_tables.sql
- createdb.cmd
- createdb.sql
- createtablespaces.cmd
- createtablespaces.sql
- createuser.sql
- eXchange50Runtime.sql
- in_user_seq.sql
- setenv.cmd

To edit the setenv command script

Open a command prompt and change directories to the local directory where you saved the scripts in the previous procedure.

Use a text editor to edit the as-supplied version of setenv.cmd:

@REM SET YOUR DATABASE CONNECTION INFORMATION HERE
*
echo * This file should be edited to use appropriate
echo * database connection settings. *
echo * SETENV.CMD

 @REM TNS_NAME
@set TNS_NAME= TNS NAME        

@REM ORACLE_SID
@set ORACLE_SID=  SID  

@REM Oracle system login password
@set SYSTEMPWD=  PWD  

@set USERID=ex_admin
@set USERPWD=ex_admin

Supply the appropriate values for TNS_NAME, ORACLE_SID, and SYSTEMPWD. For example:

@set TNS_NAME=eXchange_myOracleHostname
@set ORACLE_SID=ORCL
@set SYSTEMPWD=manager
@set USERID=ex_admin
@set USERPWD=ex_admin

If your Oracle location is not c:\oracle\oradata, or if your database instance name (SID) is other then eXchange, then open the createtablespaces.sql file and make the appropriate change or changes in the first line.

Note –
The database user who runs the SQL scripts must have permission to create tables.