IBM BJ0NJML - Service And Asset Management - Enterprise Bean Access; Securing Enterprise Bean Access

Enterprise Bean Access
Security 179
2 Under the <assembly-descriptor> section in the ejb-jar.xml file, add the
following elements shown in bold text:
<assembly-descriptor>
<security-role>
<role-name>maximouser</role-name>
</security-role>
<container-transaction>
<method>
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
Enterprise Bean Access
The integration gateway implements an Enterprise JavaBean (EJB) as the entry
point for receiving data from an external system. An enterprise bean supports the
basic J2EE security.
Securing Enterprise Bean Access
If J2EE Authentication on the system is enabled, you must enable the security for
each enterprise bean in the deployment descriptors.
1 Change the ALLOWDFLTLOGIN value to 0 (false), to force system
authentication.
Under the <enterprise-beans> section of the ejb-jar.xml file, three integration
EJBs (enterprise service, object structure service, and standard service) are
deployed with a default value of 1, no authentication.
The <ejg-name> to service mapping is:
The following code illustrates that the enterprise service is deployed with an
ALLOWDFLTLOGIN value of 1.
<enterprise-beans>
<session id="Session_enterpriseservice">
<ejb-name>enterpriseservice</ejb-name>
<home>psdi.iface.gateway.MEAGatewayHome</home>
<remote>psdi.iface.gateway.MEAGateway</remote>
<local-home>psdi.iface.gateway.MEAGatewayHomeLocal</local-
home>
<local>psdi.iface.gateway.MEAGatewayLocal</local>
<ejb-name> Service
enterpriseservice Enterprise Service
mosservice Object Structure Service
actionservice Standard Service