Collect

Register Sources to Target

Data can be pulled from multiple sources to a single target; therefore, multiple sources can be registered to a Target.

To register a source to a target: 

  1. Click Targets in the Navigation pane.
  2. Click the Sources icon for the Target.

  3. Click Add.

    View the field descriptions for the Target Sources page

  4. Select a database name from the SOURCE list box. The source database must be different from the target database.

  5. Update the CONNECTION TYPE list box if the default value is not applicable.

    NOTE: The CONNECTION TYPE is a valid database connection type from source to target.

  6. Select a System Type from the SYSTEM TYPE ID list box if importing group tables from a System Type delivered with Common.

    NOTE: Click the + icon to open the System Types page in Common in a new tab to add a System Type, if needed.

  7. Update the SCHEMA OWNER field if the default value is not applicable.

    NOTE: The SCHEMA OWNER controls the schema of the source database that contains the tables. The Schema Owner for a source cannot be the same as the Schema Owner for an associated target.

  8. Click Save; the Vertical View displays.

    View the field descriptions for the Target Sources page's Vertical View

  9. Enter a brief description of the Source in the Description field, for example., DBA or Business Contact information.
  10. Click Advanced Settings tab.

  11. Enter the table name of the renamed table in the target database in the Rename Table Template field, if tables must be renamed when copied to the target.

    NOTE: The Rename Table Template field allows the user to rename a table in the target database when the target is refreshed with source data. The field must contain the value <TableName> and any prefix or suffix can be used. When the table is downloaded from the source, <TableName> is replaced with the Rename Table Template value. If the table has been previously created, enable Delete Target Table On Build to recreate the table using the new name.

  12. Update the Schedule ID list box if the default value is not applicable.

    NOTE: The Schedule ID determines when the refresh process is run. Schedules are created and maintained in Common. Refer to Create Schedules for detailed information.

  13. The Download Keys Indexes check box is checked by default, allowing Collect to download primary key indexes from non-SAP source system.

    NOTE: If Download Keys Indexes is checked, Download SQL (Configuration > Connection Types > Sources) must be defined for the database connection type.

  14. Click the Delete Target Table on Build check box to activate it, which deletes all previously downloaded tables (and primary keys and indexes) and rebuilds the table each time a package is built.

    NOTE: The Delete Target Table on Build setting ensures the most recent table schema is downloaded.

  15. Select a database connection type from the Data Services Connection Type list box to connect to the source database if using SAP Data Services. Values are:
    • AES15
    • DB2 UDBv8
    • DB2 UDBv9
    • Informix v10
    • Informix v11
    • MySQL v5.0
    • MySQL v5.1
    • ODBC
    • Oracle10g
    • Oracle 11g
    • Oracle9i
    • SQL2000
    • SQL2005
    • SQL2008

    NOTE: The Data Services Connection Type list box displays Data Sources supported via the DSP’s integration with Data Services. If the source connects to SAP Data Services, populate the Connection Settings. Refer to Configure Source for SAP Data Services for detailed information.

  16. Click the Sap Settings tab if SAP is the target database. If SAP is not the target database, these fields can remain blank.

    NOTE: With the SAP Settings fields populated, Collect recognizes that the connecting system is SAP. If the actual value is unknown, populate these fields with dummy values for the time being (e.g., “NA”). Be sure to update these values before Go-Live.

  17. Enter an ID in the SAP User ID field.
  18. Enter the password that corresponds to the User ID in the SAP Password field.
  19. Enter the name of the client within the SAP instance in the Client field.

    NOTE: The information in this field is used to filter the data downloaded from the source. The filter runs against the MANDT column.

  20. Click the All Clients check box to activate it, if more than one SAP client is required. If enabled, data is downloaded for all clients in the SAP instance.
  21. Click the Remove Client From Key check box to activate it, which builds the Client field (usually MANDT). This feature can only be used if one client is being downloaded (as in, if All Clients is disabled).
  22. Enter a three-character SAP instance used in the source refresh in the Instance field.
  23. Enter the default language in the Language field, for example, E for English.
  24. Enter the system number used to log into SAP in the SAP System Number field so Pool Table data can be refreshed.

    NOTE: The information in this field is used to filter the data downloaded from the source. The filter runs against the MANDT column.

    NOTE: The SAP System Number is located on SAP GUI Change Item screen in SAP so Pool Table data can be refreshed.

  25. Enter the server host name in the SAP Server Host field.

    NOTE: The SAP Server Host is located on the SAP GUI Change Item screen in SAP.

  26. Expand the Sap Optional label to configure RFC options.

    NOTE: If not using an RFC connection, the fields under Sap Optional can remain blank.

  27. Update the RFC Name Space Option list box if default value is not applicable. Values are:
    • NAMESPACE
    • NONNAMESPACE

  28. Enter the server host name in the SAP Msg Server Host if SAP Load Balancing is used to download SAP table via RFC.

    NOTE: If Load Balancing is not used, enter a single space. The SAP Msg Server Host is located on the SAP GUI.

  29. Enter the logon group name in the SAP Logon Group if SAP Load Balancing is used to download SAP table via RFC.

    NOTE: If Load Balancing is not used, enter a single space. The SAP Logon Group is located on the SAP GUI.

  30. Click Save.
  31. Click the Sap Settings tab to test the SAP connection. If the source database is not SAP, close the Vertical View.
  32. Click the Test Sap Connection icon to use the provided User ID and Password to verify the login credentials are valid. This process does not verify the user has security to the source tables within SAP.

Continue with Configure Source for SAP Data Services.