IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 198 / 330

Remote Integration APIs (MicService)
184
Integration Guide
1
Use the following the security-constraint block for a Web service servlet.
<security-constraint>
<web-resource-collection>
<web-resource-name>Integration Web Services</web-
resource-name>
<description>Integration Web Services accessible by
authorized users</description>
<url-pattern>/services/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<description>Roles that have access to Integration Web
Services</description>
<role-name>maximouser</role-name>
</auth-constraint>
<user-data-constraint>
<description>data transmission gaurantee</description>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
2
For Web service invocation, ensure that the client program uses the following
user name and password calls in the JAX-RPC Call object:
call.setProperty(Call.USERNAME_PROPERTY, username);
call.setProperty(Call.PASSWORD_PROPERTY, password);
You can securely deploy a Web service by using SSL (HTTPS). Set up the SSL in
the application server with the appropriate digital certificates.
Remote Integration APIs (MicService)
Some MicService remote APIs have a secure access by forcing the user of those
methods to provide the UserInfo object. If you do not provide a valid UserInfo
object, an error occurs and the call is not completed.
The following remote methods that provide sensitive information or perform
sensitive data transaction processing have been system protected.
T exportData(..)
T deleteQueueData(..)
T processExternalData(..) (both versions)
T query(..)
T viewQueueData(..)
T loadData(..)
T loadSystemData(..)