|
|
|
|
|
|
Security in the WebLogic Portal Enterprise JavaBeans
As described in Security Roles and Deployment Descriptors, each Enterprise JavaBean (EJB) Java ARchive (JAR) file has two associated deployment descriptors: ejb-jar.xml and weblogic-ejb-jar.xml. These XML files contain elements that register an application's individual JavaBeans with appropriate security constraints. Since you will use the services provided by these EJBs a starting point for developing your own applications, this topic describes the contents of the deployment descriptors for each JAR in WebLogic Portal. Therefore, this topic includes the following sections:
Note About the weblogic-ejb-jar.xml Deployment Descriptors in WebLogic Portal
Because the security elements in the weblogic-ejb-jar.xml deployment descriptors for each WebLogic Portal EJB JAR may be the same, a listing of this file's contents for each EJB JAR file will not be shown. For all EJB JARs discussed in this topic, the weblogic-ejb-jar.xml deployment descriptor may contain one or more of the following security-role assignments:
<security-role-assignment>
<role-name>CustomerRole</role-name>
<principal-name>wlcs_customer</principal-name>
</security-role-assignment>
<security-role-assignment>
<role-name>DelegatedAdminRole</role-name>
<principal-name>DelegatedAdministrator</principal-name>
</security-role-assignment>
<security-role-assignment>
<role-name>EveryoneRole</role-name>
<principal-name>everyone</principal-name>
</security-role-assignment>
<security-role-assignment>
<role-name>SystemAdminRole</role-name>
<principal-name>SystemAdministrator</principal-name>
<principal-name>system</principal-name>
</security-role-assignment>
campaign.jar
The campaign.jar file is a collection of EJBs that provide the portal campaign and user interaction services. The campaign.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
campaignws.jar
The campaignws.jar file contains an EJB that supports a Web service that the E-Business Control Center uses to populate ad query and e-mail picklists. The campaignws.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
catalogws.jar
The catalogws.jar file contains an EJB that provides a Web service that the E-Business Control Center uses to browse the product catalog. The catalogws.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
customer.jar
The customer.jar file is a collection of EJBs that supports the com.beasys.commerce.ebusiness.customer.Customer entity. The customer.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
document.jar
The document.jar file contains an EJB that supports document management services (searching, retrieval, and schemas). The document.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
ebusiness.jar
The ebusiness.jar file is a collection of EJBs that support Commerce services, including product catalog, order, tax calculation, shipping, payment, and supporting EJB Pipeline Components. The ebusiness.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
ejbadvisor.jar
The ejbadvisor.jar file contains an EJB that provides access to BEA Advisor personalization infrastructure. The ejbadvisor.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
events.jar
The events.jar file contains an EJB that supports the Events and Behavior Tracking service. The events.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
ldapprofile.jar
The ldapprofile.jar file contains an EJB that is used to read user and group properties from an LDAP server. The ldapprofile.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
mail.jar
The mail.jar file is a collection of EJBs that gives your application access to the outbound Mail Service, which uses the JavaMail API to send e-mail to customers in batches. The mail.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
payment.jar
The payment.jar file contains an EJB that supports the Payment Web Service application. The payment.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
petflow.jar
The petflow.jar file contains an EJB and all the Pipeline Components for the Pet Flow sample Web application.
Note: All the Pipeline Components are application scoped, must be deployed with an EJB, and not reside in the system classpath or Web application classpath. Alternately, if the Pipeline Components are not EJBs they may be packaged in a separate JAR (as long as they are referenced from the pipeline.jar's manifest file). Since the components in the petflow.jar file reference components in other utility JARs, you must update the classpath in petflow.jar's manifest file to include the JARs of the utility components: Class-Path: p13n_util.jar petStore_EJB.jar pipeline.jar.
The petflow.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
petStore_EJB.jar
The petStore_EJB.jar file is a collection of EJBs and other application-scoped classes that are part of the Sun Microsystems Pet Store Demo, a comprehensive e-commerce application based on the Java 2 Enterprise Edition (J2EE) specification. For more information on the original Pet Store Demo, see the "Architecture Overview" at http://java.sun.com/j2ee/blueprints/jps11/archoverview.html.
The EJBs and other classes in this JAR file are referenced by the Pet Flow sample Web application, which comes packaged with the WebLogic Portal product suite. The Pet Flow application has been designed to illustrate some of the features of the Webflow mechanism.
pipeline.jar
The pipeline.jar file contains all Pipeline internals, including an EJB that provides support for the Pipeline service and other supporting, application-scoped classes.
Note: This file need only be deployed if Pipeline Components are being used. If you are strictly using only Webflow you need not deploy this file.
The pipeline.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
placeholder.jar
The placeholder.jar file is a collection of EJBs that support the placeholder, ads, and ad bucket services. The placeholder.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
portal.jar
The portal.jar file is a collection of EJBs that provide all portal functionality, including the visitor runtime tools and the administration tools. The portal.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
property.jar
The property.jar file is a collection of EJBs that provide Property Set functionality and persistence services for components that use the property framework, such as User and Group profiles. The property.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
propertysetws.jar
The propertysetws.jar file contains an EJB (that provides a Web service) that provides access to server side Property Sets so that outside components, such as the E-Business Control Center, can use them. The propertysetws.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
rules.jar
The rules.jar file contains an EJB that provides stateless access to the underlying BEA Rules Engine. The rules.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
stockportal.jar
The stockportal.jar file contains an EJB that provides [NEED DESCRIPTION]. The stockportal.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
tax.jar
The tax.jar file contains an EJB that supports the Tax Web Service application. The tax.jar file contains the following EJB, whose ejb-jar.xml deployment descriptor security settings are described in the table that follows:
usermgmt.jar
The usermgmt.jar file is a collection of EJBs that provide user and group management and Unified User Profile (UUP) services. The usermgmt.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
wlcsSample.jar
The wlcsSample.jar file is a collection of EJBs that provide various components used exclusively by the Commerce JSP templates. The wlcsSample.jar file contains the following EJBs, whose ejb-jar.xml deployment descriptor security settings are described in the tables that follow:
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|