When PageVisit JMS messages are sent within an Oracle Commerce Platform application rather than to an Oracle Commerce Platform application from a Web service, the values of various message properties are determined by the PageEventTrigger component on the Oracle Commerce Platform server. When you send these messages through a Web service, however, the PageEventTrigger is not available, and you must set them explicitly on the PageVisit object created by the client application.
Note that setting these values incorrectly will prevent any scenarios that are waiting for these messages from being fired.
Use the same settings for the PageVisit message properties that you would use for a message sent within an application, with the following important exception: use the path property rather than scenarioPathInfo property to specify the path of the page that was visited. This behavior is necessary because only the PageEventTrigger contains the necessary logic for specifying the correct value for scenarioInfoPath.
Important: When you set up a scenario to watch for this event, do not use the document picker (Choose document…) to select the page to include in the Visits element; pages specified this way automatically use the scenarioInfoPath property. Instead, use the whose path or with Dynamo path option in the element to specify the path to the page, and make sure that the value you enter matches the value that you send in the message from the Web service. Both of the following examples are valid ways to specify the correct path in the scenario element:
Visits a page whose path is /en/index.jsp
Or
Visits a page with Dynamo path /en/index.jsp
For pages that are outside the Dynamo document root (the page is part of a non-DAS J2EE application) make sure the path property includes the application context root.
For more information on the PageVisit message, refer to PageVisit Event.
