Client messages are used in ePortal orchestrations to communicate with the client. A client can be a Web browser user, a mobile device user, or a Web service consumer. A client message can be sent to the client, received from the client, or both. As such, they can be thought of as the Web page or mobile application page that is seen by the user or as the Web service method that can be made part of a service object application. Every data source project must have client messages defined.
Client messages are created automatically during the creation of a data source in the following instances:
The project is an MCP COBOL data source project or T27 data source project populated by importing Screen Design Facility forms from a formlibrary. Refer to Using an SDF Formlibrary with ePortal.
The data source project was populated by importing individual screens or data descriptions, and the property Auto Create Client Message was True. Refer to Data Source Project Property Pages Dialog.
Client messages are not created if the data source project was populated by importing individual screens or data descriptions, and the property Auto Create Client Message was False. Refer to Data Source Project Property Pages Dialog.
If the data source project had client messages created, then one of the following can be done:
Do nothing and accept the data flow that was captured during the population of the data source.
Prepare to change the data flow by modifying, deleting, and creating client messages that meet the needs of the planned presentation project or projects.
Refer to Creating Client Messages, Deleting a Client Message, or Modifying Client Messages.
Once the appropriate client messages are present in the data source project, the data flow logic needs to be created or modified. Use orchestration to define the logic. Refer to Understanding Orchestration.