Creating a Connection
This procedure describes how to use Siebel Migration to create a connection for a migration. Creating a connection registers a Siebel environment to the Siebel Migration. Each connection represents either a Source (development) or Target (production) environment to be used for migration. Numerous connections can be created for a migration
This task is a step in Process of Using Siebel Migration to Migrate Data.
To create a connection
-
In the Siebel Migration Application, click Connections in the navigation menu in the side panel to go to the Connections screen. You define the Source or Target of a migration plan in this screen.
Click New Connection, and in the New Connection window that appears:
Note: The Name field and REST Endpoint field are mandatory fields; all other fields in the New Connection window are to be completed as required.Enter a name for the new connection in the Name field.
Enter a valid endpoint for the connection in the REST Endpoint field.
The format for a valid REST Endpoint is as follows:
https://<hostname>:<port>/siebel/v1.0
Where
siebel
can be replaced with any customized URL.If this connection will ever be used as the target of a migration plan, then in the Database Information Applicable for Target Environments only section of the New Connection window, enter the information described in the following table.
Field
Description
DB Schema Owner User ID
Enter the Database Table Owner user name.
Tablespace for Data
Enter the name of the tablespace where you want to import the tables. This field applies to Oracle and DB2 LUW. For any other database, this value will be ignored.
Tablespace for Index
Enter the name of the tablespace where you want to import the indexes. This field applies to Oracle and DB2 LUW. For any other database, this value will be ignored.
Tablespace for 16k Page
Enter the name of the 16k tablespace where you want to import the tables. This field applies to DB2 LUW only. For any other database, this value will be ignored.
Tablespace for 32k Page
Enter the name of the 32k tablespace where you want to import the tables. This field applies to DB2 LUW only. For any other database, this value will be ignored.
Database Encoding
Select one of the following options:
UNICODE Database
Non-UNICODE Database
-
To modify an existing connection:
-
Click Edit (the pencil icon) next to the connection that you want to edit.
-
In the Edit Connection window that appears, modify the fields as required—see the previous table for more information.
-