The XML Gateway uses profile options to define the following for your system:
The directory path for XML messages and log files
The directory path for XSLT style sheets
The XML Gateway System Administrator's e-mail address
The sender's information system
The time zone for the database server
The maximum size an outbound document may reach before validating whether parsing should be continued
The maximum memory available for the database session running the Java portion of the XML transformation
The option of either purging all XML Gateway data along with workflow data or only purging workflow data
The continuation of parsing XML document if an outbound document reaches its maximum size
The Trading Partner user security feature for inbound transactions
The XML Gateway engine processing of inbound messages either in Java or PL/SQL
To define these profile options, you must sign on to Oracle E-Business Suite as the System Administrator responsibility. Navigate to the System Profile Values form using the path (N) Profile > System.
For additional information on setting profile options and profile categories, see User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide.
The following table lists the XML Gateway system profile options:
| Profile Option | Description | Category | Required | Default Value |
|---|---|---|---|---|
| ECX: Log File Path | Log File Path where the XML messages and runtime log are stored | Deployment | YES | None |
| ECX: XSLT File Path | XSLT Path where XSLT style sheets are stored | Deployment | YES | None |
| ECX: System Administrator Email Address | XML Gateway System Administrator e-mail address | Administrator Setup | YES | None |
| ECX: OAG_LOGICALID | Identifier for Sender's Information System | Administrator Setup | NO | None |
| ECX: Server Time Zone | The time zone in which the database server is running. See Important below. | Administrator Setup | YES | Null |
| ECX: Maximum XML Size | This profile option specifies the maximum size of an outbound XML document (in bytes). For more information on how this profile option works, see Note below. | XML Processing | NO | 2 MB |
| ECX: XML Validate Flag | This profile option specifies whether an outbound document should continue to be parsed by the engine after the maximum size defined in the 'ECX: Maximum XML Size' profile option has been reached. This profile option works together with the 'ECX: Maximum XML Size' profile option. For more information on how this profile option works and how to disable the XML parsing and validation, see Note below. | XML Processing | NO | Y |
| ECX: Enable User Check for Trading Partner | This profile option controls whether an inbound transaction can be enabled based on the value set in the profile option and the association between a user and Trading Partner. | Security/Compatibility | NO | NO |
| ECX: Notification Timeout in Minutes | This profile option sets the timeout period for a notification that is waiting for a response. If the notification timeout value is exceeded, XML Gateway execution engine will automatically reprocess the erred transaction if it does not exceed the maximum retries limit. | XML Processing | NO | NO |
| ECX: Maximum Reprocess Attempts For Errored Inbound Transaction | This profile option governs the number of times that XML Gateway execution engine will automatically reprocess the erred transaction after the notification timeout period. | XML Processing | NO | NO |
| ECX: Purge ECX data with WF | This profile controls purging of XML Gateway data when Purge Obsolete Workflow Runtime Data concurrent program is submitted to purge XML Gateway transactions attached to workflow.
See Purge Obsolete Workflow Runtime Data Concurrent Program. | Exportable | NO | Y |
| ECX: Java Memory Limit | This profile option allows you to increase the maximum memory (in megabytes) available for the database session running the Java portion of the XML transformation at the site level.
Note: With the increase of maximum memory while processing XML messages, it not only helps avoid Java out of memory errors (Java heap space exception), but also helps smooth XSLT transformation and XML message processing. | XML Processing/Exportable | NO | 1024 MB
Note: It can range from 256 MB up to all the available database server memory. |
| ECX_IN_JAVA_PROCESSING | This profile option determines if inbound messages will be processed in Java or PL/SQL.
| XML Processing | YES | YES |
Attention: The valid values for ECX: Server Time Zone are listed in Appendix E. If this profile option is not set, the time zone ID will default to Greenwich Mean Time (GMT).
Note: While parsing the outbound document, XML engine will check the following two profile options to determine if the outbound document will continue to be parsed:
The 'ECX: Maximum XML Size' profile value to obtain the maximum size that an outbound XML document should be parsed.
If the maximum size is not set, the default maximum value will be used.
The 'ECX: XML Validate Flag' profile value only if the outbound document size is greater than the maximum size.
If the document is less than the maximum size, then the parsing will be continued regardless of the profile value set in the 'ECX: XML Validate Flag'.
If the document is greater than the maximum size and the 'ECX: XML Validate Flag' profile value is also set to 'Y', then the parsing will be continued.
For example, while parsing the outbound document, if an outbound XML document has size greater than the maximum 2MB, then the 'ECX: XML Validate Flag' profile value will be checked. If the validate flag is also set to 'Y', then the document will continue to be parsed. However, if the document reaches the maximum size, but the validate flag is set to 'N', then the parsing will not be continued.
Disabling XML Parsing and Validation: Because the 'ECX: XML Validate Flag' profile option works together with the 'ECX: Maximum XML Size' profile option, to disable XML parsing and validation for outbound messages, you not only need to set the 'ECX: XML Validate Flag' profile value to 'N', but also need to set the 'ECX: Maximum XML Size' profile to a value that is low enough so that your outbound document size can easily surpass it. This way, when the document size is greater than the maximum size you defined, and you have the 'ECX: XML Validate Flag' profile set to 'N', then the parsing and validation will be disabled. The XML engine will not parse the document and perform the XSL transformation.
Setting the 'ECX: XML Validate Flag' profile value to anything other than 'Y' will turn off parser validation for a document once the maximum size has been parsed. Turning off the validation avoids Out of Memory errors for large documents. If validation is turned off, the XSLT Transformation action cannot be performed. For more information on the XSLT Transformation action, see perform_xslt_transformation.
For additional information on setting profile options and profile categories, see User Profiles and Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide.