1.2 Maintenance in Transformer
Transformer is a message formatting and translation toolkit. Using this toolkit, we can transform the files from corporate’s preferred format to OBEDX format.
Transformer consist of two parts –
- Message & Mapping definition GUI toolkit used to define set of DictionAry Definitions (DAD)
- A run-time application programming interface (API) which uses the DAD to transform messages from one format to another.
Follow following steps to use transformer for message transformation
Prerequisites
- Corporate preferred format/template – File format which a corporate upload
- OBEDX format – This template is supplied by Oracle. The template can be found in the OBEDX Formats for Transformation.zip folder.
Steps to be followed
- Create new project in Transformer
- Create or import the message of corporate preferred format – The template which needs to be transformed.
- Import the OBEDX format template as per below steps.
- Tools > JSON schema import > Single file > Next > Schema file > select the schema file provided by Oracle > Next > Enter Group name > Next > Uncheck root schema check box (but keep all the check boxes checked below root schema check box) > Next > Move everything to selected window > Next > Finish
- Do the mappings between preferred format and OBEDX format.
- Add validations as per the requirement, refer table list of supported error codes
- Create new exposed service and select the service builder as project jar builder
- Select the java version 8
- Add new exposed service operation select the operation type as OneToOneMapping
- Select the appropriate message definition group and mapping definition
- Test the mappings
- Build the exposed service, this will generate the jar file
- Note down the project key, service name & operation name generated on transformer’s console.
- Deploy this jar in middleware service.
List of supported status / error codes:
ERROR CODE | ERROR MSG |
---|---|
TRA-RLV-001 | Record Level Validations Failed. |
TRA-STX-001 | Transaction syntax check failed |
TRA-PAR-000 | PARSING SUCESS |
TRA-PAR-001 | PARSING DONE with exceptions |
TRA-RLV-002 | Expected value for $1 is $2, actual value provided $3 |
TRA-STX-003 | Invalid date $1 |
TRA-STX-002 | Max length of the field with value $1 is breached. Expected max length is $2 |
TRA-STX-004 | $1 is mandatory |
TRA-STX-005 | Invalid currency $1 |
Note:
Once should use above error codes while performing mapping in transformer’s desktop application. $1 is placeholder and it should be replaced with appropriate value.Parent topic: Integration Guide