The Echo Web service expects a login from a user named wssm-testuser with
a password of testonly123. Therefore, you must add
this user to the user registry or user registries that you are using
for your Echo environment.
You can use any user registry that is supported by WebSphere® Application Server. However,
to ensure that the Echo application works correctly, consider the
following tips:
- An environment in which the Echo Web service application and Tivoli® Access Manager use the
same user registry simplifies your configuration because you must
add the wssm-testuser to only that one registry.
- If you choose to use different registries for the Echo Web service
and Tivoli Access Manager,
be sure you have added the wssm-testuser to both
of the registries.
- If you are running on the z/OS® platform with WebSphere Application Server using 'Local
operating system' for the user registry and cannot use a username
greater than eight characters, then select a different username to
use with the Echo application. This username must be specified in
the wssm_test.xsl mapping file located in the wssm/examples/etc directory.
In the wssm_test.xsl file, replace wssm-testuser with
the selected username. To perform Tivoli Access
Manager authorization checking with the Echo application, the selected
user ID must also be defined to Tivoli Access
Manager and be given access to the protected object for Echo.
Note: To log in at the Echo client, you can use any user name and
password that exists in the WebSphere Application
Server user registry that is being used by the server where the Echo
client is running.