Tasks to complete after generating the pattern
- The enterprise wsdl, which has been generated to include your customised fields, including the addition of
the mandatory external keys, must be imported to generate a new message definition file.
- Select the message set Instancename_SFWSDL_MSET
- Select New Message definition File from wsdl File and select the location of your
Salesforce enterprise.wsdl file.
- If you have selected the simple customisation option you must
map new fields into their equivalents in the Salesforce service data.
- If Account field(s) have been added
then the map ACCOUNT_submap0.msgmap should be opened and the fields mapped to the body
of the service request.
- If Contact field(s) have been added
then the map CONTACT_submap0.msgmap should be opened and the fields mapped to the body
of the service request.
- If you have selected the advanced customisation
option you will have to map your input data from the message definition in your message set
to the salesforce service data.
- To complete the mapping of account data for advanced customisation:
- Open the mapping file ACCOUNT.msgmap
- Right click on the sources pane, select "Add Sources" and select the message from your
message set which contains your account data.
- Right click on the source and select "Add or remove headers and folders"
- Clear "Properties" and select "LocalEnvironment"
- The SOAP Header of the target SOAP message is shown as a Wildcard Message. This is because the
Salesforce wsdl supports a number of headers. You need only to use the Session Header and the pattern
creates the data for this header in the LocalEnvironment.
- Select the LocalEnvironment in the source pane.
- Right click on the Wildcard message in the SOAP Header of the target and select
"Use Existing Submap". Select the SESSIONID.msgmap submap.
- The Body of the target SOAP message is also shown as a Wildcard Message. This is because the
Salesforce WSDL contains many operations.Create a submap to map your data to the body.
- Select the top level element which contains all the data to be mapped.
- Right click on the Wildcard message in the SOAP Body of the target and select
"Create New Submap"
- You will be give a list of elements to define the wild card.
Select the upsert operation from the message set InstanceName_SFWSDL_MSET
- The Salesforce wsdl supports the upsert operation for different object types.
To work with
the account structure right click on the "specializations for tns:Objects" and
select Show Derived Types. Deselect the top ens:Sobject and select
"tns:Sobject[0,inbounded](ens:Acount)
- Expand both sides and complete the mapping of your data into
the SOAP body. Save and exit this submap.
- Create the broker archive (BAR) file. Add the message flows
and message sets to a
single broker archive file.
- Security parameters are defined as pattern parameters but you can change these before
deployment by configuring the broker archive file to set the UDPs which define the broker
identity, password and security string obtained when
the Salesforce password is changed. These strings are held as properties of the Main message flow. The properties are:
- SF_BROKER_USERNAME
- SF_BROKER_PASSWORD
- SF_BROKER_SECTOKEN
-
Configure the broker archive file.
Further configuration of the message flow in the broker archive
file is not required before you deploy the message flows for your
MQ to Salesforce:Account Management
pattern instance, but you might want to review some of the default options and
configure changes for your environment.
For example, you might want to review the following properties:
- Request logging required and
Response logging required.
Use these properties to switch logging on and off.
When you turn logging on, you must check that the logging queue is
correctly defined for your environment.
- ErrorLoggingOn.
If error messages are included,
at deployment time this switch determines whether
logging of errors is required for the current environment.
You can change any of the pattern parameters that are listed in the
parameter tables as configurable, but you must be
careful because the pattern might be assuming specific behavior.
However, you can
change properties that are determined by operational
characteristics and do not affect flow logic, for example,
security configuration or additional instances.
-
Create queues and queue managers.
This pattern uses a standard queue prefix which is defined as a pattern parameter. If no prefix is defined
the prefix is derived from the pattern instance name by removing any characters which are invalid in a queue name.
The queues required will depend on the options selected. These are as follows:
- If the account creation option is selected create queue prefix.INCA
- If the contact creation option is selected create queue prefix.INCA
- If the account delete option is selected create queue prefix.INCA
- If the contact delete creation option is selected create queue prefix.INCA
- If the the logging option is selected create queue prefix.INCA
- If the option to write error messages nt creation option is selected create queue prefix.INCA
- If the account creation option is selected create queue prefix.INCA
- Deploy the BAR file. The message set containing the deployable WSDL must be
deployed by using the same or another BAR file, to every broker where the flows
are deployed.
Back to the overview