Share configuration information with a trading partner using jumpstart XML files

You can help your trading partners configure their systems by creating jumpstart files for them to import into their system. A jumpstart XML file is a mirror image of a AS4 Microservice exchange profile. The jumpstart XML file is the opposite of the original exchange because it contains the configuration for the trading partner. For example, the jumpstart XML file that is created from an outbound exchange profile on AS4 Microservice is an inbound exchange profile for the trading partner. The destination that is defined in the AS4 Microservice exchange profile is a receiver in the jumpstart file.

Create jumpstart XML files with the user interface

You use the AS4 Microservice user interface to create jumpstart XML files.

Example jumpstart XML file created from an exchange profile

This table lists the parameters that are in the original exchange profile and in the created jumpstart XML file.

Table 1. Exchange profile components that are exported
Parameter	Configuration of the inbound exchange profile that is exported	Configuration in the exported XML file
Exchange profile direction	Inbound	Outbound
Owning organization	AS4 Microservice master organization.	The owner organization role is changed to the trading partner organization role.
Trading partner organization	Trading partner	The trading partner role is changed to the owner organization role.
Receiver ID	Receiver ID of the owner organization.	The receiver ID is changed to sender ID.
Sender ID	Sender ID of the trading partner organization.	The sender ID is changed to the receiver ID. If trading partner is anonymous, the value for sender ID is not provided in the exported file.
Service	The service for which the exchange profile is used.	The service remains the same.
Agreement URI	The mutually (between the owner organization and the trading partner) agreed on location where the p-mode and other message exchange-related information is uploaded or posted.	The agreement URI remains the same.
P-Mode ID	The mutually agreed on identifier that is used to identify the processing-mode (p-mode) configuration for the conformance policy.	The p-mode ID remains the same.
AS4 receiver information	The AS4 receiver information includes the AS4 service URI and the host server port information. For example, if the port number of the HTTP or HTTPS server that you have associated with the AS4 receiver is 63000, and the URI of the AS4 receiver is /test-uri, then the URL of the AS4 receiver that is exported is, `http://hostname:63000/test-uri`. Note: The host name can be replaced with the IP address. Also, the IP address or the port can be of a proxy server or an external load balancer.	The HTTP or HTTPS server information is used as the HTTP or HTTPS destination information.
Conformance policy - security settings	The following outbound, inbound, and user authentication security settings are exported: Outbound exchanges signing configuration Inbound exchanges signing configuration User authentication credentials (if user authentication checking is enabled)	If Outbound exchanges use X.509 certificate to sign the data is enabled in the conformance policy that is associated with the inbound exchange profile, the public key of the certificate that is used to sign outbound messages is exported. If primary and secondary certificates are associated with the certificate alias, both the certificates are exported. If Inbound exchanges require signed messages is enabled in the conformance policy that is associated with the inbound exchange profile, the setting is applied to the outbound exchanges. A corresponding setting must be configured in the conformance policy of the trading partner. If Enable user authentication checking is enabled in the conformance policy that is associated with the inbound exchange profile, the same setting is applied to the outbound exchange profile. The user credentials that are associated with the conformance policy are also exported. If multiple users are associated with the exchange profile, a single, selected credential is exported.
Conformance policy - Reception awareness settings	The reception awareness settings of the conformance policy	If Require receipt is enabled in the conformance policy, the same setting is applied to the outbound exchange profile. Receipts are sent to the corresponding HTTP or HTTPS server in the exported file.
Connection settings	User name and password	User name and password credentials are exported.
Pull destination name	Pull destination name is exported. If a default pull destination is specified in the inbound exchange profile, the pull destination name is not specified in the exported file.	Pull destination name is exported.
Error destination (push)	AS4 receiver	The HTTP or HTTPS server that is associated with the AS4 receiver (of the inbound exchange profile) is used to send ebMS errors.
Error destination (pull)	AS4 receiver	The HTTP or HTTPS server that is associated with the AS4 receiver (of the inbound exchange profile) is used to send ebMS errors.

For a complete list of jumpstart XML elements, see Inverse exchange profile XML elements.