Tasks to complete after generating the pattern

  1. 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.
  2. If you have selected the simple customisation option you must map new fields into their equivalents in the Salesforce service data.
  3. 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.
  4. To complete the mapping of account data for advanced customisation:
  5. Create the broker archive (BAR) file. Add the message flows and message sets to a single broker archive file.
  6. 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:
  7. 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: 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.
  8. 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:
  9. 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