Run project
|
Application Consultant
|
You can use a project to exchange data. To be able to run a project, tasks must be set up for the project. If you run the project, all related tasks are run. Depending on the tasks that are set up for the project, you can use a project to run: - An integration or data migration.
- Outbound web services.
- Batch classes.
- Master data management.
- Test cases.
Usually, you run a project in batch. Based on the defined sub-projects and tasks dependencies, tasks are run in parallel. If you do not run the project in batch, all sub-projects and tasks are run sequentially. |
Run task
|
Application Consultant
|
You can use a task to run the execution of:
- An integration or data migration. In this case, use a task with the desired messages defined.
- Outbound web services. In this case, use a task with the desired outbound web service actions defined.
- Batch classes. In this case, use a task with the desired batch classes defined.
- Master data management. In this case, use a task with the desired master data entities defined.
- Test cases. In this case, use a task with the desired messages with test cases defined.
If you run a task, all defined messages, outbound web service actions, batch classes, and master data entities are run. Usually, you run a task by running the related project. In this case, all tasks of the project are run, taking into account the defined task dependencies. However, you can run a single task, for example, for testing purposes. |
Run web service action
|
Application Consultant
|
If you want to run an outbound web service action immediately, you can run it from the Web service action page. |
Run web service action from a button
|
Application Consultant
|
You can use button on a form to run an outbound web service action. You can add a button to a form in these ways:
- Dynamic button
Use a dynamic button to manually start an outbound web service action from a form.
- Action menu item
Use a custom action menu item to manually start an outbound web service action from a form. For the action menu item, custom coding is required.
|
Process data synchronization log
|
Application Consultant
|
For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.To fully process the logged events, process the:
- Data synchronization log: The logged events are processed and for each applicable message or web service action, a record is added to the Outbound queue.
- Outbound queue: For each record, the related message or web service action is run to export the applicable data.
This topic explains how to process the data synchronization log.
Note:
- Events are logged only for tables and event types that are defined in the data synchronization setup of any message or web service action.
- If on the data synchronization setup, the Update check box and the Check used fields check box are selected, event logging is restricted to changes to the fields as defined for the record in the applicable source document.
- Only the event is logged and used for further processing. So, in case of an update, an event is logged of type Update. However, the changed data is not marked as changed and not used for further processing. For example, if you change a customer address, an event is logged that the customer is updated. However, the address change as such is not logged. When, for the logged event, a record is processed in the outbound queue, the then current data of the customer is used.
- If a logged event is processed, it is deleted from the data synchronization log.
Example:
This table gives examples of the results for several data synchronization log processing scenarios:
Number of pages |
Page size |
Limit records |
Number of records to be processed |
Result |
5 |
10,000 |
No |
40,000 |
4 pages of 10.000 records are processed |
5 |
10,000 |
Yes |
40,000 |
4 pages of 10.000 records are processed |
5 |
10,000 |
No |
80,000 |
5 pages of 16.000 records are processed |
5 |
10,000 |
Yes |
80,000 |
5 pages of 10.000 records are processed |
|
Process outbound queue
|
Application Consultant
|
For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.
To fully process the logged events, process the:
- Data synchronization log: The logged events are processed and for each applicable message or web service action, a record is added to the Outbound queue.
- Outbound queue: For each record, the related message or web service action is run to export the applicable data.
This topic explains how to process the outbound queue.
Outbound queue
The outbound queue only has unique entries for each combination of:
- Record on which the event was logged
- Message or web service action
- Event type
- Status
Note that the record and event type are known, but the (changed) data of the records is not known. When an outbound queue entry is processed, the current data of the record is used. For example, if a customer address is changed, an event is logged that the customer is updated. However, the address change as such is not logged. When, for the logged event, a record is processed in the outbound queue, the current data of the customer is used.
Bundling
In the outbound queue, several entries can exist for a unique message or webservice action. How these entries are processed, depends on whether bundling is active. You can activate bundling on the data synchronization setup of an outbound:
- Message: On processing the outbound queue, by default, all entries for a unique message are bundled in one message run, which results in one file.
- Web service action: On processing the outbound queue, by default, all entries for a unique web service action are bundled in one web service action run, which results in one file. Note: You cannot apply bundling to an outbound web service action that uses a stream.
- EDI document flow: On processing the outbound queue, the entries are bundled in one message run or web service action run, which results in one file. In this case, the outbound queue entries are bundled by the applicable EDI party.
If the bundling field is set to:
- Yes, all outbound queue entries for the message are bundled and processed in one message run, which results in one file.
- No, each outbound queue entry is processed in a separate message run.
Processing the outbound queue
You can process the outbound queue in several ways. To process the outbound queue for:
- All records, do not define a message or web service action.
- A specific message, define the message.
- A specific web service action, define the web service action.
You can also run the outbound queue for a specific project. To do so, when you run a project, set the Process outbound queue field to Yes. As a result, the outbound queue is processed for the messages or web service actions that are linked to the project tasks.
If an outbound queue record is processed, it gets the status:
- Processed, if it is processed successfully.
- Error, if errors occurred during processing.
|