Siebel Communications Server Administration Guide > Using Wireless Messaging > Using Two-Way Wireless Messaging Workflows >

Setting Up Two-Way Wireless Messaging


This section outlines the basic process for setting up and using two-way wireless messaging.

  1. Create the communications driver profiles you will need. Profiles must be based on the Wireless Messaging 2-Way communications driver. For more information, see Configuring Communications Drivers and Profiles.
  2. Configure the workflow policies and workflow processes, according to your business needs.
  3. Make sure that the workflows you need are activated, and the workflows you do not need are inactive.
  4. NOTE:  Do not activate both the Wireless Activity Policy (Service) workflow policy (used for one-way messaging) and the Outbound Wireless Messaging Activity Dispatch Policy workflow policy (used for two-way messaging).

  5. For each workflow policy used for outbound wireless messaging, generate triggers that correspond to the applicable triggering condition, by using the Generate Triggers server component.
  6. Trigger conditions for the predefined two-way wireless messaging workflow policy are noted in Table 74.

  7. For inbound wireless messaging, create a response group. Do this in the All Response Groups view in the Communications Administration screen. For this response group:
    1. Associate one or more profiles to this response group. Associate profiles for the communications driver Wireless Messaging 2-Way.
    2. Create an input argument record named ProcessName, with the value Inbound Wireless Messaging Activity Dispatch.
  8. Start the Workflow Monitor Agent server component to monitor trigger conditions. Specify the corresponding group name.
  9. Configure the Inbound Communications Manager server component. Create the component parameter Response Group Name, and provide the exact name of the applicable response group.
  10. Start the Inbound Communications Manager server component.
  11. Test your workflows.
  12. NOTE:  Communications Outbound Manager is automatically started when an applicable workflow is invoked.


 Siebel Communications Server Administration Guide 
 Published: 23 June 2003