HTTP Servlet
182
Integration Guide
blocks, one for each type of service: enterprise service, object structure service,
and standard service.
The <web-resource-name> to service mapping is:
The following integration servlet code samples have the security constraint
comment sections removed for each service type.
<!--
<security-constraint>
<web-resource-collection>
<web-resource-name>Enterprise Service Servlet</web-
resource-name>
<description>Enterprise Service Servlet (HTTP POST)
accessible by authorized users</description>
<url-pattern>/es/*</url-pattern>
<url-pattern>/esqueue/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<description>Roles that have access to Enterprise Service
Servlet (HTTP POST)</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>
<security-constraint>
<web-resource-collection>
<web-resource-name>App Service Servlet</web-resource-
name>
<description>App Service Servlet (HTTP POST) accessible by
authorized users</description>
<url-pattern>/ss/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<description>Roles that have access to App Service Servlet
(HTTP POST)</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>
<security-constraint>
<web-resource-collection>
<web-resource-name> Service
Enterprise Service Servlet Enterprise Service
App Service Servlet Standard Service
Object Structure Service Servlet Object Structure Service