TWS for Distributed Data
When transitioning TWS for distributed data, use the following workflow.
Step 1 | Set global options. |
---|
Step 2 | Open the TWS-d files input dialog.
The input dialog will display.
|
---|
Step 3 | Set the TWS-d input file locations. Use the buttons or text fields on the input dialog to enter the file locations. The file locations that you enter will be saved over sessions. |
---|
Step 4 | Set TWS-d preferences: - Override task type with type from cpu.
Normally, a task type is determined by the job definition. In some cases, the determined type can be overridden by the type of operating system it runs on. Use only on direction of Stonebranch engineers. - Use only the jobname when creating task names.
Normally, a task name is created from the cpu name and jobname: CPU#jobname . Checking the box will result in task names without CPU# . Extract EVERY jobs. Interval jobs can be taken out of a workflow to enable interval processing. This will give the extracted job it's own interval trigger. - Generate a workflow for each SAP job.
This option can be set to prepare the converted TWS-d data for merging with SAP transitions. Use only on direction of Stonebranch engineers.
|
---|
Step 5 | Set SAP preferences. - Name of SAP connection variable
The name of SAP connection variable can be set for each transition. - Name of SAP credential variable
The name of SAP credential variable can be set for each transition. - SAP command options
Free format text field to enter specific SAP command options to be included in the generated SAP task.
|
---|
Step 6 | Start conversion. After starting the conversion, all files will be processed in sequence. A progress bar at the top right corner informs you of the progress. |
---|
Step 7 | When conversion has finished... |
---|