3Installing and Configuring the Integration

Installing and Configuring the Integration

This chapter describes how to install and configure Siebel CRM Integration to Oracle FLEXCUBE Universal Banking. It contains the following topics:

• Roadmap for Installing and Configuring the Integration

• Accessing the Integration Files

• Installing Oracle Data Integrator

• Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment

• Process of Configuring Oracle Data Integrator in a Development Environment

• Process of Implementing the Integration in an Oracle Data Integrator Production Environment

• Process of Configuring Siebel Business Applications

• Configuring Oracle FLEXCUBE Universal Banking Integration Components

Roadmap for Installing and Configuring the Integration

This topic describes the tasks involved in installing and configuring Oracle Data Integrator, and configuring Oracle FLEXCUBE Universal Banking and Siebel CRM to enable the Integration.

Note: In this guide, the term, the Integration, refers to Siebel CRM Integration to Oracle FLEXCUBE Universal Banking.

To install and configure the Integration, perform the following tasks and processes:

1. Install the required software listed in Software Requirements.

   For information on installing the software, see the product documentation.

2. Accessing the Integration Files.

3. Installing Oracle Data Integrator.

4. Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment.

5. Process of Configuring Oracle Data Integrator in a Development Environment.

6. Process of Implementing the Integration in an Oracle Data Integrator Production Environment.

7. Process of Configuring Siebel Business Applications.

8. Configuring Oracle FLEXCUBE Universal Banking Integration Components.

Accessing the Integration Files

The software required for Siebel CRM Integration to Oracle FLEXCUBE Universal Banking is provided with the Siebel Tools client application. The following procedure describes how to access the Integration files.

This task is a step in Roadmap for Installing and Configuring the Integration.

To access the Integration files

1. Install the Siebel Tools client.

   For more information, see Siebel Installation Guide for the operating system you are using.

2. In the Siebel Tools installation directory, navigate to the REPPATCH directory, for example, navigate to \Siebel\8.2\Tools_1\REPPATCH\, and locate the ACR548.zip file.

3. Unpack the ACR548.zip file to extract the integration files. These include:

   • The Oracle Data Integrator work and master repository files used for the batch data loading process

   • Siebel Enterprise Integration Manager configuration files (IFB files) used for the batch data loading process

   • WSDL files used for the online synchronization of data

Installing Oracle Data Integrator

Before you can deploy the Integration files, you must install and configure Oracle Data Integrator. For general information on these tasks, see Oracle® Fusion Middleware Installation Guide for Oracle Data Integrator 11g Release 1. This topic describes the specific installation and configuration tasks required for Siebel CRM Integration to Oracle FLEXCUBE Universal Banking.

This task is a step in Roadmap for Installing and Configuring the Integration.

To install Oracle Data Integrator

1. Perform the following preinstallation tasks:

   1. Create a database schema to store the Oracle Data Integrator work repository and master repository.

   2. Ensure that the schema owners of the Oracle FLEXCUBE Universal Banking and Siebel databases are assigned the following privileges:

      • Create and drop table

      • Create and drop synonym

      • Insert, update, and delete table

      • Create and drop view

      • Create and drop procedure

      • Create and drop sequence

      • Create and drop triggers

      • Create and drop DB Links

      • Create and drop functions

      • Create and drop packages

2. Install Oracle Data Integrator as described in Oracle® Fusion Middleware Installation Guide for Oracle Data Integrator. Select the following installation options:

   1. In the Select Installation Type screen, select ODI Studio (with local agent). You can optionally choose to install the Standalone Agent.

   2. In the Repository Configuration screen, select the Skip Repository Configuration option.

3. After the installation process has completed, configure a connection between Oracle Data Integrator and the master repository as follows:

   1. Start ODI Studio.

   2. From the ODI menu, choose File, and then the New menu item.

   3. In the New Gallery window, select ODI from the General category, then select the option, Create a New ODI Master Login.

   4. In the Repository Connection Information window, enter ODI and database connection information using values similar to that shown in the following table.

      Section	Parameter	Value
      Oracle Data Integrator Connection	Login Name	Enter a connection alias, for example, Master Repository.
      	User	Enter the value SUPERVISOR for the ODI supervisor user name.
      	Password	Enter the value SUPERVISOR for the password associated with the supervisor user.
      Database Connection (Master Repository)	User	Enter the user ID of the owner of the tables created for the master repository.
      	Password	Enter the password associated with the table owner user ID.
      	Driver List	Select the driver required to connect to the database where the master repository is defined, for example, Oracle JDBC Driver.
      	Driver Name	Enter the driver name, for example, oracle.jdbc.driver.OracleDriver.
      	URL	Enter the complete path of the data server hosting the master repository.
      Work Repository	Master Repository Only	Select this option.

   5. Click the Test button to verify that the connection is working.

   6. Click OK.

Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment

This topic describes how to import the repository files required for the Integration into an Oracle Data Integrator development environment.

This process is a step in Roadmap for Installing and Configuring the Integration.

To deploy the Integration files, perform the following tasks:

1. Importing the Master Repository for the Integration

2. Creating a Work Repository

3. Importing the Work Repository for the Integration

For additional information on these tasks, see Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator 11g Release 1.

Importing the Master Repository for the Integration

This topic describes how to import the master repository for the Integration from the Master_Repository.zip file.

This task is a step in Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment and Process of Implementing the Integration in an Oracle Data Integrator Production Environment.

The following procedure describes how to import the master repository.

To import the master repository

1. Start ODI Studio.

2. From the ODI menu, choose File, and then the New menu item.

3. In the Categories tree, select ODI.

4. In the Items list, select Master Repository Import Wizard.

5. In the Repository Connection screen, specify Database Connection and Repository Configuration information as follows:

   • Database Connection. The values you specify for the Database Connection parameters must be the same as those specified when you configured the connection between Oracle Data Integrator and the master repository as described in Step 3 in Installing Oracle Data Integrator.

     Click the Test Connection button to test the database connection, then click Next. Ensure the connection is working before proceeding.

   • Repository Configuration. Select the Use a Zip File option, and enter the path to the Master_Repository.zip file that you accessed in Siebel Tools. For information, see Accessing the Integration Files.

6. In the Password Storage screen, accept the default option, Use Password Storage Configuration specified in Export. By selecting this option, the user name and password values that are configured in the repository are used to log in to Oracle Data Integrator. These values are:

   • User: SUPERVISOR

   • Password: SUPERVISOR

7. Click Finish.

   Oracle Data Integrator imports the master repository.

Creating a Work Repository

Before importing the Integration work repository from the Workrep.zip file, you must create a new work repository.

This task is a step in Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment and Process of Implementing the Integration in an Oracle Data Integrator Production Environment.

To create a work repository

1. In ODI Studio, open the Topology navigator.

2. Navigate to Repositories, then Work Repositories.

3. Right-click, then select the New Work Repository option.

4. In the ODI Work Repository connection properties screen, specify the values listed in the following table.

   Parameter	Value
   Technology	Select the technology of the server that is to host the work repository, for example, Oracle.
   JDBC Driver	Specify the driver required to connect to the database where the work repository is defined.
   JDBC URL	Enter the complete path of the data server hosting the work repository.
   User	Enter the user ID of the owner of the tables that are to be created for the work repository.
   Password	Enter the password associated with the table owner user ID.

5. Click the Test Connection button to verify that the connection is working, then click Next.

6. On the Specify ODI Work Repository properties screen, specify values for the parameters listed in the following table.

   Parameter	Value
   Id	Assign a unique number to the work repository.
   Name	Enter a name for the work repository, for example, WORKREP1.
   Work Repository Type	Select Development if you are implementing the Integration in a development environment. Select Production if you are implementing the Integration in a production environment.

7. Click Finish.

   The work repository is created.

8. Disconnect from the master repository by navigating to the ODI menu option, then selecting the Disconnect repository_nameoption.

Importing the Work Repository for the Integration

The task of importing the Integration work repository involves creating a new work repository login, connecting to the work repository you previously created, and then importing the Integration work repository. The following procedure describes these tasks.

This task is a step in Process of Importing the Integration Repository Files in an Oracle Data Integrator Development Environment.

To import the work repository for the Integration

1. Start ODI Studio.

2. From the ODI menu, choose File, and then the New menu item.

3. In the Categories tree, select ODI.

4. In the Items list, select Create a New ODI Repository Login.

5. In the Repository Connection Information screen, specify the connection information as follows:

   • Oracle Data Integrator Connection. Enter the same values for the Connection parameters that you specified when configuring the connection between Oracle Data Integrator and the master repository as described in Installing Oracle Data Integrator.

   • Database Connection (Master Repository). Enter the same values for the Database Connection parameters that you specified when configuring the connection between Oracle Data Integrator and the master repository as described in Installing Oracle Data Integrator.

   • Work Repository. In the Work repository field, enter the name of the work repository you created in Creating a Work Repository, for example, WORKREP1.

6. Click the Test button to test the connection.

7. Click the Connect to Repository… link, then select the Work Repository connection.

8. Right-click the Designer Navigator, select Import, and then select the Work Repository option.

9. In the Import work repository dialog box, select the import mode from the Import Mode list. Select one of the following options:

   • Synonym Mode INSERT

   • Synonym Mode INSERT UPDATE

10. Select the Import from a Zip file option, and enter the path to the workrep.zip file. For information on this file, see Accessing the Integration Files.

    Note: The import process can take between 30 and 50 minutes to complete. Wait until the import has completed before attempting to perform other operations in Oracle Data Integrator.

    When the work repository import is completed the Import Report is displayed.

11. Perform the following substeps to explicitly import the work repository projects for the Integration to the work repository. Performing these steps ensures that global variables are mapped to scenarios when the scenarios are generated at a later stage.

    1. Unzip the workrep.zip file.

    2. Open the Operator navigator, right-click Scenarios, then select the Import Scenario menu item.

    3. In the File import directory field, enter the name of the folder containing the unzipped Workrep.zip file.

    4. Select all the scenarios in the Select the file(s) to import list, then click OK.

Process of Configuring Oracle Data Integrator in a Development Environment

This topic describes how to configure Oracle Data Integrator for the Integration.

This process is a step in Roadmap for Installing and Configuring the Integration.

To configure Oracle Data Integrator, perform the following tasks:

1. Connecting to the Oracle FLEXCUBE Universal Banking and Siebel CRM Databases

2. Configuring a Context for the Integration

3. Configuring Integration Variables

4. Generating Scenarios for Integration Packages

Connecting to the Oracle FLEXCUBE Universal Banking and Siebel CRM Databases

In order for Oracle Data Integrator to perform bulk data uploads, it must be configured to connect to the Oracle FLEXCUBE Universal Banking and Siebel databases. This involves:

1. Creating a database link.

2. Configuring Oracle Data Integrator to connect to the Oracle FLEXCUBE database.

3. Configuring Oracle Data Integrator to connect to the Siebel database.

Each of these tasks is described in the following topics.

This task is a step in Process of Configuring Oracle Data Integrator in a Development Environment.

Creating the Database Link

Database links are used to transfer data between the Oracle FLEXCUBE Universal Banking and Siebel databases. Use SQL*Plus or any other database tool to create the database link in the Siebel database to access data from the source Oracle FLEXCUBE Universal Banking database.

The following procedure describes how to create the database link.

To create the database link

1. Enter the following command:

   		CREATE DATABASE LINK database link name
   	{CONNECT TO oracle user ID
   	IDENTIFIED BY remote oracle user's password}
   		USING 'dbstring';
   

   where:

   • database link name is the name you assign to the database link

   • oracle user id is the user ID used to connect to the remote Oracle FLEXCUBE database

   • remote oracle user's password is the password associated with the oracle user ID

   • dbstring is the name of the service used to connect to the database

2. Use the following query to verify that the database link is successfully created:

   		SELECT DB_LINK FROM ALL_DB_LINKS
   

   For example, the following SQL statements create a database link in the local Siebel database that connects to the AAADEV2 database, with the FCDEV116 user ID, using the service name AAADEV2.

   		CREATE DATABASE LINK AAADEV2 
   		CONNECT TO FCDEV116
   		IDENTIFIED BY FCDEV116
   		USING '(DESCRIPTION =
       		(ADDRESS = (PROTOCOL = TCP) (HOST = 10.184.74.142)(PORT = 1521))
       		(CONNECT_DATA =
       		(SERVER = DEDICATED)
       		(SERVICE_NAME = AAADEV2 )
       		)
       		)'
   

Configuring Oracle Data Integrator to Connect to the Oracle FLEXCUBE Universal Banking Database

The procedure in this topic describes how to configure Oracle Data Integrator to connect to the Oracle FLEXCUBE Universal Banking database.

To configure Oracle Data Integrator to connect to the Oracle FLEXCUBE database

1. Start ODI Studio, and connect to the ODI work repository you created previously, for example, WORKREP1.

2. Open the Topology Navigator, then navigate to Physical Architecture, Technologies, Oracle, and then Oracle FC Server.

3. Select Oracle FC Server, then click the Definition tab.

4. Specify values for the following Data Server definition parameters:

   1. In the Instance/dblink (Data Server) field, enter the name assigned to the database link you created in Creating the Database Link.

   2. In the User and Password fields, enter the user name and password that are used to connect to the remote Oracle FLEXCUBE Universal Banking database. Enter the same user and password values as those specified when creating the database link.

5. Click the JDBC tab, then specify values for the following parameters:

   1. In the JDBC Driver field, select the driver used to access the Oracle FLEXCUBE database, for example, the Oracle JDBC driver.

   2. In the JDBC URL field, enter the complete path to the Oracle FLEXCUBE Universal Banking database.

6. On the Topology Navigator, expand Oracle FC Server, select the FLEXCUBE data server, and select the Definition tab to view the Physical Schema definition details.

7. In the Physical Schema screen, do the following:

   1. Enter the name of the Oracle FLEXCUBE database in the Schema (Schema) and Schema (Work Schema) fields.

      The Work Schema is a temporary store for objects required at run time. Depending on how you have implemented Oracle Data Integrator, the Schema and Work Schema can be the same or different. If these schemas are different, the user specified in Step 4 must have privileges to both.

   2. Click the Default button.

Configuring Oracle Data Integrator to Connect to the Siebel Database

The procedure in this topic describes how to configure Oracle Data Integrator to connect to the Siebel database.

To configure Oracle Data Integrator to connect to the Siebel database

1. Start ODI Studio and connect to the ODI work repository you created previously, for example, WORKREP1.

2. Open the Topology Navigator, then navigate to Physical Architecture, Technologies, Oracle, and then Oracle Release Server.

3. In the Data Server editor, specify values for the following Data Server definition parameters:

   1. In the Instance/dblink (Data Server) field, enter the name of the Siebel database.

   2. In the User and Password fields, enter the user name and password that are used to connect to the Siebel database.

4. Click the JDBC tab, then specify values for the following parameters:

   1. In the JDBC Driver field, select the driver used to access the Siebel database, for example, the Oracle JDBC driver.

   2. In the JDBC URL field, enter the complete path to the Siebel database.

5. Click the Test Connection button to verify that the connection settings are correct.

6. In the Topology Navigator, expand Oracle Release Server, select the Siebel data server, and open the Physical Schema definition.

7. In the Physical Schema screen, do the following:

   1. Enter the name of the Siebel database in the Schema (Schema) and Schema (Work Schema) fields.

      The Work Schema is a temporary store for objects required at run time. Depending on how you have implemented Oracle Data Integrator, the Schema and Work Schema can be the same or different. If these schemas are different, the user specified in Step 3 must have privileges to both.

   2. Click the Default button.

Configuring a Context for the Integration

In an Oracle Data Integrator implementation, a context comprises all the physical resources belonging to a specific environment, for example, the resources in a production or development environment. Contexts are used to link components of the physical architecture (the physical resources) with components of the logical architecture. You must create a context for the Integration as described in this topic.

This task is a step in Process of Configuring Oracle Data Integrator in a Development Environment

To configure a context for the Integration

1. Start ODI Studio, and connect to the ODI work repository you created previously, for example, WORKREP1.

2. Open the Topology Navigator, then navigate to Contexts.

3. Do one of the following:

   1. Create a new context for running the ODI interfaces by right-clicking, and selecting New Context.

   2. Select the existing default value, Release Context, for running ODI Interfaces.

4. If you are creating a new context, then enter the context name in the Name field.

5. To relate the logical and physical schemas for the Oracle FLEXCUBE and Siebel database servers, do the following:

   1. Click the Schemas tab.

   2. In the Logical Schema column, select the Siebel CRM logical schema.

   3. In the associated Physical Schemas column, select the physical schema to associate with the Siebel CRM logical schema.

   4. Repeat Step b and Step c for the Oracle FLEXCUBE logical schema.

6. To verify that the context, for example, Release Context, is correctly assigned to the Siebel CRM and Oracle FLEXCUBE logical schemas, do the following:

   1. In the Topology Navigator, navigate to Logical Architecture, Technologies, Oracle, and then Oracle FC Server.

   2. In the Logical Schema editor, verify that the context specified for Oracle FC Server is Release Context.

   3. In the Topology Navigator, select the Oracle Release Server.

   4. In the Logical Schema editor, verify that the context specified for Oracle Release Server is Release Context.

Configuring Integration Variables

In Oracle Data Integrator, you can create and store the following variables, which can then be used in various projects:

• Global variables. Use in all projects.

• Project variables. Use in specific projects.

Oracle Data Integrator variables store single values, for example, a string, a number, or a date, which can be updated at run time. This topic describes how to modify the global and project variables required by the Integration.

This task is a step in Process of Configuring Oracle Data Integrator in a Development Environment

To configure integration variables

1. Start ODI Studio and connect to the ODI work repository you created previously, for example, WORKREP1.

2. Open the Designer navigator, then navigate to Others, and then Global Variables.

3. Select each of the variables shown in the following table in turn, open the variable, and in the Variable editor screen, set the default value of the variable as indicated in the following table.

   Global Variable	Default Value
   FINS_BIB_Enterprise_Server	Specify the name of the Siebel Enterprise Server, for example, siebel.
   FINS_BIB_Gateway_Server	Specify the name and port number of the Siebel Gateway.
   FINS_BIB_Log_Path	Enter the path to the directory where you want to store Server Manager log files for Enterprise Integration Manager jobs.
   FINS_BIB_Username	The Siebel user name used for connecting to the Siebel Enterprise, for example, SADMIN.
   FINS_BIB_Password	The password associated with the Siebel user name defined in FINS_BIB_Username.
   FINS_BIB_Siebel_Path	Enter the full path to the Siebel installation directory that contains the srvrmgr.exe file.
   FINS_BIB_Siebel_Server	Specify the name of the Siebel Server on which the Siebel Enterprise Integration Manager component runs.
   FINS_BIB_Default_Organization	Specify the name of the organization for which you want to load data. This variable is applicable for Product and Branch data only.
   FINS_BIB_EIM_ErrorFlags	Specify the event log level for the Siebel Enterprise Integration Manager component. For additional information on changing log levels, see Siebel Enterprise Integration Manager Administration Guide.
   FINS_BIB_EIM_SQLFlags	Specify a value of 8 to log all SQL statements that make up the Siebel Enterprise Integration Manager task. For additional information, see Siebel Enterprise Integration Manager Administration Guide.
   FINS_BIB_EIM_TraceFlags	Specify the trace log level for the Enterprise Integration Manager component. For additional information, see Siebel Enterprise Integration Manager Administration Guide.

4. In the Designer navigator, navigate to Projects, BIB BRANCH, Variables, and then FINS_BIB_Organization.

5. In the Variable editor screen, set the default value of the variable to the name of the bank for which branch data is to be loaded.

6. A Siebel organization must be created for the bank for which branch data is to be loaded before starting the branch data load. To create a Siebel organization, perform the following steps:

   1. Log in to the Siebel Financial Services application.

   2. Navigate to the Administration - Group screen, then the Organizations view.

   3. In the form, add a new record and complete the necessary fields.

   For detailed information on creating organizations and divisions, see Siebel Security Guide.

Generating Scenarios for Integration Packages

Generating a scenario for an object compiles the code required to deploy and execute the object in a production environment. This topic describes how to generate scenarios for the packages provided by the Integration.

This task is a step in Process of Configuring Oracle Data Integrator in a Development Environment.

The following procedure describes how to generate scenarios for the Integration packages.

To generate scenarios for the Integration packages

1. Start ODI Studio, and connect to the ODI work repository that you created previously, for example, WORKREP1.

2. Open the Designer navigator, then navigate to Projects, BIB BRANCH, First Folder, Packages, and then FINS_BIB_BRANCH_PKG.

3. Right-click the package, then select the Generate Scenario menu item.

4. Click OK in the New Scenario dialog box to select the default scenario name and version.

   New scenarios are named after the component by default.

5. In the Designer navigator, navigate to the relevant project for each package listed in the following table, then repeat Step 3 and Step 4 for each of the packages.

   Project Name	Package
   BIB INITIAl SETUP	FINS_BIB_INITIAL_SETUP
   BIB PRODUCT	FINS_BIB_PRODUCT_PKG
   BIB PRODUCT	FINS_BIB_PRODUCT_RATE_PKG
   BIB LIMIT MANDATE	FINS_BIB_LIMIT_PKG
   BIB LIMIT MANDATE	FINS_BIB_MANDATE_PKG
   BIB CONTRACTS	FINS_BIB_CONTRACT_PKG

Process of Implementing the Integration in an Oracle Data Integrator Production Environment

After deploying the integration files, configuring Oracle Data Integrator, and generating scenarios for the packages provided by the Integration in the Oracle Data Integrator development environment, you can deploy the Integration in the Oracle Data Integrator production environment.

This process is a step in Roadmap for Installing and Configuring the Integration.

To implement the Integration in an Oracle Data Integrator production environment, perform the following tasks:

1. Importing the Master Repository for the Integration

2. Creating a Work Repository

3. Importing Scenarios to the Production Environment

Importing Scenarios to the Production Environment

This topic describes how to export the Integration scenarios from the Oracle Data Integrator development environment and import the scenarios into the production environment. It also describes how to modify scenario variables in the production environment. For detailed information on importing and exporting Oracle Data Integrator objects, see Oracle® Fusion Middleware Developer’s Guide for Oracle Data Integrator.

This task is a step in Process of Implementing the Integration in an Oracle Data Integrator Production Environment.

When Oracle Data Integrator scenarios are generated in a development environment, the default values of the global and project variables used in the scenarios relate to the development environment. When Oracle Data Integrator is then deployed in the production environment, these default values might not apply.

To ensure that the values of the variables used in scenarios are appropriate when scenarios are transferred to the production environment, use one of the following methods:

• Change the values of the Global and Project variables in the development environment to the correct values for the production environment, and then generate the scenarios. For more information, see Configuring Integration Variables.

• Manually modify the Global and Project variables used in the scenarios in the production environment. For more information, see Modifying Scenario Variables in the Production Environment.

• Pass the correct values of the Global and Project variables for the production environment to Oracle Data Integrator each time a scenario is run. Oracle Data Integrator overrides the default value of the variable with the value that is passed.

  This option is available only if you have installed the Oracle Data Integrator Standalone Agent and can run scenarios from the command line. For additional information, see Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator 11g Release 1.

Transferring Scenarios Between Repositories

The following procedure describes how to export scenarios from the Oracle Data Integrator development environment and import the scenarios into the production environment.

To transfer scenarios between repositories

1. Perform the following steps to export the scenarios from the development environment work repository:

   1. After generating the Integration scenarios in a development environment as described in Generating Scenarios for Integration Packages, open the Operator navigator and select Scenarios.

   2. Right-click the scenario that you want to export, then select the Export menu item.

   3. In the Export Directory field, enter the path to the directory where you want to export the scenario, then click OK.

   4. Repeat Step c for each scenario that you want to export.

2. To import the scenarios into the production environment work repository, perform the following steps:

   1. In the production environment, start ODI Studio, and connect to the ODI work repository.

   2. Open the Operator navigator, right-click Scenarios, then select the Import Scenario menu item.

   3. In the File import directory field, enter the name of the file import directory. Specify the name of the directory that you exported the scenario to in Step 1.

   4. Select the files that you want to import, and then click OK.

   5. Click Yes to continue the import if a warning message appears stating that you are about to delete or replace objects.

   When the import process is completed, a list of the imported objects is displayed.

Modifying Scenario Variables in the Production Environment

You must update the variables in the scenarios that are imported to the production environment by replacing any variable value that contains information specific to the development environment with the corresponding values for the production environment. The following procedure describes this task.

To modify scenario variables in the production environment

1. In the Operator navigator, navigate to Scenarios, Scenario Name, Variables, Variable Name

   where:

   • Scenario Name is the name of the imported scenario

   • Variable Name is the name of the variable to be updated

2. In the Scenario Variable editor, change the value in the Default Value field to the appropriate value for the production environment.

3. For each of the imported scenarios, repeat Step 1 and Step 2 for the following variables:

   • FINS_BIB_Default_Organization

   • FINS_BIB_EIM_ErrorFlags

   • FINS_BIB_EIM_SQLFlags

   • FINS_BIB_EIM_TraceFlags

   • FINS_BIB_Enterprise_Server

   • FINS_BIB_Gateway_Server

   • FINS_BIB_Log_Path

   • FINS_BIB_Organization

   • FINS_BIB_Password

   • FINS_BIB_Siebel_Path

   • FINS_BIB_Siebel_Server

   • FINS_BIB_Username

Process of Configuring Siebel Business Applications

This topic describes the tasks you must complete to configure your Siebel financial application for the Integration. For additional information on the Siebel CRM finance applications, see Siebel Finance Guide.

This process is a step in Roadmap for Installing and Configuring the Integration.

To configure Siebel Business Applications, perform the following tasks:

• Configuring the Workflow Monitor Agent

• Configuring the Workflow Process Manager Component

• Configuring JMS for Outbound Web Services Using Advanced Queuing

• Modifying Lists of Values

• (Optional) Setting Up Additional Product Features

• Activating Integration Workflows

• Configuring Outbound Web Services

• Setting System Preferences

Configuring the Workflow Monitor Agent

This topic describes how to configure the Workflow Monitor Agent that is used to monitor workflow policies used in the Integration.

This task is a step in Process of Configuring Siebel Business Applications.

• The Integration uses the Workflow Monitor Agent BIB Customer workflow to monitor customer workflow policies. Configuring this component involves:

• Creating a Workflow Monitor Agent, Workflow Monitor Agent BIB Customer

• Configuring the Workflow Monitor Agent BIB Customer component

Creating a Workflow Monitor Agent to Monitor Customer Workflow Policies

The procedure in this topic describes how to create a new Workflow Monitor Agent to monitor the customer workflow policies used in the Integration.

To create a Workflow Monitor Agent to monitor customer workflow policies

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Definitions view.

3. In the Component field, select Workflow Monitor Agent, and then make a copy of the record by selecting the Copy Record menu item.

4. Set values for the new record as shown in the following table.

   Field	Value
   Component	Workflow Monitor Agent BIB Customer
   Alias	WorkMonBiBCust
   Component Group	Workflow Management
   Description	Monitors Workflow Manager events for BIB Customer

5. Click the Activate button to activate the new component, then Click the Synchronize button to synchronize the component.

6. Restart the Siebel Server.

   For information on this task, see Siebel System Administration Guide.

Configuring the Workflow Monitor Agent BIB Customer Component

This topic describes how to configure the Workflow Monitor Agent BIB Customer component created previously.

To configure the Workflow Monitor Agent BIB Customer component

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Server Configuration screen, then the Servers view.

3. In the Siebel Servers list, select the server that you want to configure.

4. In the Component field, select Workflow Monitor Agent BIB Customer.

5. In the Parameters form, set the values of the parameters as shown in the following table.

   Parameter	Value
   Group Name	BIB Customer
   Action Interval	5
   Sleep Time	10
   Default Tasks	1

6. Restart the Siebel Server.

   For information on this task, see Siebel System Administration Guide.

Configuring the Workflow Process Manager Component

This topic describes how to configure Siebel Server parameter values for the Workflow Process Manager component used in the Integration.

This task is a step in Process of Configuring Siebel Business Applications.

To configure the Workflow Process Manager

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Server Configuration screen, Servers, and then the Components view.

3. In the Component field, select Workflow Process Manager.

4. In the Parameters form, select Business Service Query Access in the Parameter field, and set the Value field to Workflow Process Manager.

Configuring JMS for Outbound Web Services Using Advanced Queuing

When updates are made in Siebel CRM to accounts or contacts, either a Siebel run-time event or a workflow policy is triggered to send the updated data to Oracle FLEXCUBE Universal Banking. The run-time event or workflow policy in turn causes one of the following Siebel workflows to be invoked:

• FINS BIB Account Info Update FC Workflow

• FINS BIB Contact Info Update FC Workflow

When each of these workflows is invoked, it submits a request, using the EAI JMS Transport business service, to the JMS queue hosted by Oracle FLEXCUBE Universal Banking. This topic describes how to set up the Java environment for the Integration and how to configure and test the EAI JMS Transport business service used in the Siebel outbound Web services.

This task is a step in Process of Configuring Siebel Business Applications.

Installing and Configuring the Java Environment

The following procedure describes how to set up your Java environment.

To install and configure your Java environment

1. Verify that Java Runtime Environment (JRE) 1.6 is installed on the computer on which your Siebel Server runs.

   For information on downloading JRE, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

2. Install the required JAR files:

   1. Copy the following Siebel JAR files from the SIEBSRVR_ROOT\CLASSES directory to D:\JMS.

      • Siebel.jar

      • SiebelJI_enu.jar

      where SIEBSRVR_ROOT is the installation directory for Siebel Server.

      Note: If this directory is not present, then create it.
   2. Copy the Wlfullclient.jar file to D:\JMS.

      The wlfullclient.jar file is provided by Oracle FLEXCUBE Universal Banking, the Web service provider.

3. Create the jndi.properties file on the Siebel Server in the D:\JMS directory. The jndi.properties file specifies the connection values that the Siebel Server uses to look up queues and their connection factories dynamically. Specify the following values for the jndi.properties file:

   		java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
   		java.naming.provider.url=FLEXCUBE ipaddress and port name 
   		java.naming.security.principal=weblogic
   		java.naming.security.credentials=weblogic#1
   

   where FLEXCUBE ipaddress and port name is the remote method invocation (RMI) URL used to connect to Oracle FLEXCUBE Universal Banking.

4. Create the JVM subsystem used in Siebel CRM, and specify the profile parameters for the subsystem as shown in the following table.

   Name	Alias	Data Type	Value
   JVM Classpath	Classpath	String	D:\JMS\Siebel.jar;D:\JMS\SiebelJI_enu.jar;D:\JMS\wlfullclient.jar;.;D:\JMS
   JVM DLL Name	DLL	String	The path to the JVM library file, for example, in a Windows environment: C:\Sun\SDK\jdk\jre\bin\server\jvm.dll
   JVM Options	VMOPTIONS	String	JVM-specific options for the log file, for example: -Djms.log=D:\JMS\log\jms.log

   For detailed information on creating a JVM subsystem, see Transports and Interfaces: Siebel Enterprise Application Integration.

5. Stop and restart the Siebel Server for the changes to take effect.

Configuring and Testing the EAI JMS Transport Business Service

This topic describes how to configure and test the connection and queue information specified for the EAI JMS Transport business service. This service is invoked by the workflows that send updated contact and account data to Oracle FLEXCUBE Universal Banking from Siebel CRM.

The following procedure describes how to run the Business Service Simulator to test the EAI JMS Transport business service configuration.

To configure and test the EAI JMS Transport business service

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Business Service screen, then the Simulator view.

3. In the Simulator list, click New, and specify the values shown in the following table.

   Field	Value
   Service Name	EAI JMS Transport
   Method Name	CheckAll

4. In the Input Arguments list, specify the input parameters for the Business Service method by clicking New and specifying the values shown in the following table.

   Field	Value
   Test Case #	1
   Type	PropertySet
   Property Name	ConnectionFactory
   Property Value	JNDI name of the JMS connection factory, for example: java:comp/env/jms/MDBQCF Oracle FLEXCUBE Universal Banking provides this value.

5. To create an additional property set, click New again and specify the values shown in the following table.

   Field	Value
   Test Case #	1
   Type	PropertySet
   Property Name	SendQueue
   Property Value	JNDI name for the JMS queue. For example: MDB_QUEUE_DA Oracle FLEXCUBE Universal Banking provides this value.

6. Click Run to run the simulator for the business service.

Updating Queue and Connection Factory Details for Outbound Web Services

After verifying the queue and connection factory details using the Business Service Simulator, you must update the Integration workflows for outbound Web services with this information.

To update queue and connection factory details for outbound Web services

1. In Siebel Tools, navigate to the Workflow Processes Object List Editor.

2. Query for each of the following workflows in turn:

   • FINS BIB Account Info Update FC Workflow

   • FINS BIB Contact Info Update FC Workflow

3. For each of the workflows, perform the following steps:

   1. Change the status of the workflow to In Progress.

   2. Right click the workflow, then select Edit Workflow Process.

   3. In the Send Message to JMS Queue step of the workflow, change the values for the following process properties to the values tested in Configuring and Testing the EAI JMS Transport Business Service:

      • ConnectionFactory

      • SendQueue

   4. Save the changes.

   5. Publish and activate the workflow by clicking the Publish/Activate button on the WF/Task Editor toolbar.

      For detailed information on editing workflows using Siebel Tools, see Siebel Business Process Framework: Workflow Guide and Using Siebel Tools.

Modifying Lists of Values

Siebel CRM comes with many predefined lists of values (LOVs) that support the static lists displayed in the Siebel client. Before implementing the Integration, you must modify a number of LOVs as described in the following procedure. For detailed information on modifying LOVs, see Siebel Applications Administration Guide.

This task is a step in Process of Configuring Siebel Business Applications.

To modify the LOVs for the Integration

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Data screen, then the List of Values view.

3. Click the menu button, and then choose New Query.

4. Enter the Display Value for the record that you want to change in the Display Value field, for example, Citizen.

5. Click the menu button, then choose Run Query.

   A list of records appears that includes the display value that you entered.

6. Select the record that you want to modify, and make the change. For example, for the record with a Display Value of Citizen, deselect the Active field.

7. Perform Step 4 to Step 6 for each of the records in the following table.

   LOV_TYPE	Display Value	Change Required
   FIN_CON_CITIZENSHIP	Citizen	Deselect the Active field.
   FIN_CON_CITIZENSHIP	US Citizen	Deselect the Active field.
   FIN_CON_CITIZENSHIP	Permanent Resident	Deselect the Active field.
   FIN_CON_CITIZENSHIP	Resident Alien	Deselect the Active field.
   FIN_CON_CITIZENSHIP	Non-Resident Alien	Deselect the Active field.
   FIN_CON_CITIZENSHIP	Other	Deselect the Active field.
   FIN_CON_CITIZENSHIP	Indian	Set the Order field to 7.
   	British	Set the Order field to 8.
   	American	Set the Order field to 9.

   Note: If you choose to enable citizenship values other than Indian, British, or American, then set the Order field to a value of less than 100.

8. To see the modified list-of-values in the Siebel application, click Clear Cache.

(Optional) Setting Up Additional Product Features

The Integration loads product features information from Oracle FLEXCUBE Universal Banking to Siebel CRM. This product feature data is mapped to the following product features, which are provided as seed data in Siebel CRM:

• Check Book Facility

• Overdraft Facility

• Passbook Facility

• ATM Facility

• ILM Applicable

• Branch List in Siebel CRM

You can create additional product features in Siebel CRM if necessary. For more information, see Siebel Product Administration Guide.

This task is an optional step in Process of Configuring Siebel Business Applications.

Activating Integration Workflows

The Integration uses a number of workflows that must be activated in Siebel CRM before data synchronization can occur. The following procedure describes this task.

This task is a step in Process of Configuring Siebel Business Applications.

To activate the Integration workflows

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration-Business Process screen, then the Workflow Deployment view.

3. In the Repository Workflow Processes list, query the Name field for each of the Integration workflows.

4. For each of the workflows, select the record, and click Activate.

   Activate each of the following workflows in your Siebel application:

   • FINS BIB Account Info Update FC Workflow

   • FINS BIB Account Info Upsert SYNC Workflow

   • FINS BIB Account Limit Upsert SYNC Workflow

   • FINS BIB Activity Insert WF

   • FINS BIB Activity Upsert Workflow

   • FINS BIB Call Customer Info Update FAF Workflow

   • FINS BIB Call Lead Info Upsert Workflow

   • FINS BIB Contact Info Update FC Workflow

   • FINS BIB Contact Info Upsert SYNC Workflow

   • FINS BIB Contact Limit Upsert SYNC Workflow

   • FINS BIB Contract Upsert Workflow

   • FINS BIB Customer Info Create SYNC Workflow

   • FINS BIB Customer Info Inquiry Workflow

   • FINS BIB Customer Info Update FAF Workflow

   • FINS BIB Deposit Account Create Workflow

   • FINS BIB Deposit Account Update Workflow

   • FINS BIB Financial Transaction Populate VBC Workflow

   • FINS BIB GET Branch Loc

   • FINS BIB Lead Info Upsert Workflow

   • FINS BIB Loan Account Create Workflow

   • FINS BIB Loan Account Update Workflow

   • FINS BIB Offers Inquiry All Workflow

   • FINS BIB Populate Schedule VBC from Profile Attribute

   • FINS BIB Populate VBC from Profile Attribute

   • FINS BIB Remove Account To Customer Relationship

   • FINS BIB Remove Contact To Customer Relationship

   • FINS BIB Service Request Info Upsert FAF Workflow

   • FINS BIB Service Request Info Upsert SYNC Workflow

   • FINS BIB Service Request Query SYNC Workflow

   • FINS BIB Service Request Update Workflow

   • FINS BIB Set XML Msg to Profile

   • FINCORP BIB Deposit Account Info Upsert SYNC Workflow

   • FINCORP BIB Deposit Account Update FAF Workflow

   • FINCORP BIB Deposit Account Upsert FAF Workflow

   • FINCORP BIB Loan Account Info Upsert SYNC Workflow

   • FINCORP BIB Loan Account Update FAF Workflow

   • FINCORP BIB Loan Account Upsert FAF Workflow

   • Get Treatment Id

   For detailed information on activating workflows in a Siebel client, see Siebel Business Process Framework: Workflow Guide.

Configuring Outbound Web Services

This topic lists the Siebel outbound Web services used in the Integration and describes how to configure these services to point to the Oracle FLEXCUBE Universal Banking server.

This task is a step in Process of Configuring Siebel Business Applications.

To configure outbound Web services

1. Navigate to the Administration - Web Services screen, then the Outbound Web Services view.

2. Select a Web service.

3. In the Service Ports list, change the address field to the URL of the Oracle FLEXCUBE Universal Banking server.

4. Perform Step 2 and Step 3 for each of the following Web services in turn:

   • BankGuaranteeService

   • CustomerPartyService

   • DepositAccountService

   • DocumentaryCollectionService

   • DocumentaryCreditService

   • FinancialTransactionService

   • LineOfCreditService

   • LoanAccountService

5. Click the Clear Cache tab.

Setting System Preferences

This topic describes how to set the system preferences for the Siebel Financial Services application so that the features specific to Siebel CRM Integration to Oracle FLEXCUBE Universal Banking are enabled.

This task is a step in Process of Configuring Siebel Business Applications.

To set system preferences

1. Log in to the Siebel Financial Services application.

2. Navigate to the Administration - Application screen, then the System Preferences view.

3. Click the New button to create a new system preference, and enter the values shown in the following table.

   Field	Value
   System Preference Name	BIBEnabled
   System Preference Value	Y
   Description	To enable BIB specific flows

Configuring Oracle FLEXCUBE Universal Banking Integration Components

This topic provides a high-level overview of the tasks you must perform to install and configure Oracle FLEXCUBE Universal Banking components for the Integration. Detailed information on each of these tasks is available in the Oracle FLEXCUBE Universal Banking documentation provided with your application.

This task is a step in Roadmap for Installing and Configuring the Integration.

To install and configure Oracle FLEXCUBE Universal Banking integration components

1. Copy the contents of the installation files for Oracle FLEXCUBE Universal Banking from the CD provided by the Oracle FLEXCUBE Universal Banking product distribution group.

2. Consolidate the sources from the following releases in the order shown:

   1. FC_UBS_V.UM_11.0.0.0

   2. FCUBS_11.0.6 with patch P01

3. Install the Oracle FLEXCUBE Universal Banking application.

   For information on this task, see the Oracle FLEXCUBE Universal Banking documentation that is provided with the product software.

4. Install and configure the Oracle FLEXCUBE Universal Banking integration components (the EBO Direct Build utility) that allow the Oracle FLEXCUBE Universal Banking and Siebel CRM applications to be integrated.

   For detailed information on these tasks, see FCUBS EBO Direct Build Utility User Guide.

After configuring the Oracle FLEXCUBE Universal Banking integration components, you must perform several other tasks before the Oracle Data Integrator batch data processes can run. For information on these tasks, see Performing Batch Data Loading.