OMBSTART

Purpose

To execute objects from the Control Center. If the ASYNCHRONOUS keyword is specified then this command will return the Execution Job Identifier. Note, this can then be passed to the OMBSTOP command.

The 'Best Practice' usage of this command is within the context of a Design Repository connection. However, advanced users may use this command with a 'Control Center Only' usage. Note, the MAPPING keyword can not be used in this mode and you must specify the deployed Mapping type.

If it is required to fully specify the Deployed Mapping type then the possible values are ABAPFILE, DATAAUDITOR, DATAPROFILE, PLSQLMAP, PROCESSFLOW, SQLLOADERCONTROLFILE and SCHEDULEDJOB.

The Deployment Location of the object is optional if the name of the executable object is unique in the Control Center. However, please specify the 'CONTROL_CENTER' location for types that are deployed to the Control Center (SQL Loader and SAP Mappings).

The System Parameters that can be overriden are

PLSQL Mapping - BULK_SIZE COMMIT_FREQUENCY DEFAULT_AUDIT_LEVEL DEFAULT_OPERATING_MODE DEFAULT_PURGE_GROUP MAXIMUM_NUMBER_OF_ERRORS

SQL Loader Mapping - AUDIT BIND_SIZE CONTROL_FILE_LOCATION CONTROL_FILE_NAME DEFAULT_PURGE_GROUP DIRECT_MODE DISCARD_MAX ERRORS_ALLOWED LOG_FILE_LOCATION LOG_FILE_NAME PERFORM_PARALLEL_LOAD READ_SIZE RECORDS_TO_LOAD RECORDS_TO_SKIP ROWS_PER_COMMIT SKIP_INDEX_MAINTENANCE SKIP_UNUSABLE_INDEXES

SAP Mapping - BACKGROUND CONTROL_FILE_NAME DATA_FILE_NAME FILE_DELIMITER_FOR_STAGING_FILE LOG_FILE_NAME NESTED_LOOP PRIMARY_FOREIGN_KEY_FOR_JOIN SAP_LOCATION SQL_JOIN_COLLAPSING STAGING_FILE_DIRECTORY USE_SELECT_SINGLE

Data Auditor - BULK_SIZE COMMIT_FREQUENCY DEFAULT_AUDIT_LEVEL DEFAULT_OPERATING_MODE DEFAULT_PURGE_GROUP MAXIMUM_NUMBER_OF_ERRORS

Data Profile and Web Service - There are no System Parameters defined.

If a web service has only one operation then, as for other object types, only the ObjectName needs be specified. However if it defines more than one operation then the ObjectName must be qualified with the operation name i.e. ObjectName.operation. e.g.

MY_WEB_SERVICE.run

or

MY_WEB_SERVICE.runWithParams

Multiple operations are created for OWB object types such as PL/SQL mapping and Processflow that are published as web services. These will be:

run : "run without passing any parameters"

runWithCustomParam - "run passing Custom parameters"

runWithSystemParam - "run passing System parameters"

runWithParams - "run passing both System and Custom parameters"

The exact interface required is dependent of the interface of the object being published and therefore you are required to use the Control Center Manager or the OWB Browser to view the deployed WSDL file to determine the required parameters.

Prerequisites

'Best Practice' usage requires a Design Repository connection and the context to be set to that of executable object. The 'Control Center Only' usage does not require a Design Repository connection and therefore no context.

Syntax

parseExecuteCommand =  ( OMBSTART | OMBEXECUTE ) ( ( MAPPING | DATA_AUDITOR
           | PROCESS_FLOW | SCHEDULABLE | REAL_TIME_MAPPING | WEB_SERVICE | 
          "UNQUOTED_STRING" ) "QUOTED_STRING" [ AS "QUOTED_STRING" ] [ IN 
          "QUOTED_STRING" ] ) [ OVERRIDE SYSTEM_PARAMETER "overideParameters" ] 
          [ OVERRIDE CUSTOM_PARAMETER "overideParameters" ] [ ASYNCHRONOUS ] 
     overideParameters =  "(" "stringList" ")" VALUES "(" "stringList" ")"
     stringList =  "stringListValue" { "," "stringListValue" }
     stringListValue =  ( "QUOTED_STRING" )

Parameters