To configure the Access Gateway so that it can invoke Web service implementations, the First Steps script sets the service.Endpoint policy.
The service.Endpoint policy must be created for all requesters, for all operations, and for a specific service. You can define it for both the all and unauthenticated requesters, but it needs to be set in the scope of each Web service implementation.
When defining a policy, you must specify the policy scope in terms of the requester, service and operation in which the policy applies. By default, the service key for a specific service is the namespace of the interface, for example http://www.csapi.org/wsdl/parlayx/terminal_location/v2_2/interface. You can also use full Web service endpoints.
http://localhost:9080/TWSS/ParlayX21/TerminalLocation/Parlay/services/TerminalLocation
It is good practice to check the service.Endpoint value to see that it is set as desired. The value should typically be a load balanced URL for the service in a cluster. To check the validity of the service.Endpoint value, paste it into the address bar of a Web browser and verify that it references the Web service you want.
Use the Service Policy Manager to set a policy. To create and update policies you can use the Service Policy Manager console, which provides a graphical user interface, or you can use the Web service operations createPolicies and updatePolices.
The First Steps script creates the necessary default policies. You can use the Service Policy Manager console to view or modify these policies.