To secure a Web Services client that already exists, perform the following procedure:
- Launch the Web Services client security configuration wizard:
- Select File > New > Other.
- Select Client Services > Mobile Web Services > Mobile Web Services Client Security Configuration.
- Click Next.
- Enter the source folder containing the Java™ source code for the Web Services client application.
- Enter the URL of the WSDL exposed by the Web Services provider.
- Click Next.
- Configure Web Services Security:
- Select the Web Services name and port from the drop down menu.
- Under How to create Web Services Security configuration, select the appropriate choice. For a test case, select Template configuration, then select the Client type and the Security template from the drop down menus (Refer to Creating secure Mobile Web services clients for more information):
- Use other Lotus® Expeditor 6.x configuration
- Import WebSphere® Application Server 6.x configuration
- Convert WCTME 5.x class-based configuration
- Use template configuration
The clientSample.jks is designed for testing purposes only. You should use your own key store file instead of clientSample.jks for commercial use to avoid security exposure. Anyone who reads this document can access the clientSampke.jks.
The DeviceEE profile cannot read the file clientSample.jks created using other profiles such as J2SE due to the limitation of the DeviceEE profile's ability to read a keystore and vice versa.
When you select ‘Basic authentication' as a template, the Mobile Web Services security configuration declares username: @USERNAME@, password: @PASSWORD@
by default. To run the client properly, you must edit the Mobile Web Services security configuration in order to modify these default values. Please refer to Editing the Mobile Web Services security configuration
Parent topic: Securing Mobile Web Services