Viewing EJB Modules
Use
Java EE Applications contain different modules such as EJB and Web modules.
You can view the EJB modules of the deployed applications in the SAP NetWeaver Administrator, the enterprise beans that belong to each module, and the deployment properties of each enterprise bean and of the whole EJB module. You can also change the value of the environment entry during runtime, instead of changing it in the ejb-j2ee-engine.xml and redeploying the whole application.
Prerequisites
You are in the Configuration Management → Infrastructure → Application Modules function.
Activities
To view all deployed EJB module settings, select an EJB module from the Modules List screen area. By browsing through the different tabs, you can view the corresponding deployment properties.
EJB Module Details
In EJB Module Details, you can view the name and the type of the beans in the selected EJB module, the beans’ method transactions and permissions, if any.
You can also change the value of the bean’s environment entry. The environment entry is a configuration parameter used to customize an enterprise bean’s business logic. The environment entry values may be one of the following Java types: String, Character, Integer, Boolean, Double, Byte, Short, Long, and Float. Using the SAP NetWeaver Administrator, you can configure the environment entry value without redeploying the whole application.
Use the Get Default button to reset all changed values of the beans’ environment entries in the specified EJB module, made after application deployment. In this way you only display the initially deployed values of the beans’ environment entries. If you want to save them, choose Save.
To change the bean’s environment entry value, select the bean in the Environment and References tab and enter the new value in the General tab in Full Details. Choose Save. This automatically restarts the application by default, if it has been started. If you do not want to restart the application after you change the bean’s environment entry value, you have to set the <restart-at-runtime-change> tag in the ejb-j2ee-engine.xml of the corresponding EJB module to false.
<?xml version="1.0" encoding="UTF-8"?> <ejb-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ejb-j2ee-engine_3_0.xsd"> <restart-at-runtime-change>false</restart-at-runtime-change> </ejb-j2ee-engine> |
When you set the <restart-at-runtime-change> tag to false, it is important that you do not keep references to that bean and its environment entry value. Instead, you have to lookup the bean and its environment entry value each time you use it.
For example, if you have an EJB TestBean that contains an Environment Entry with name QUEUE_CONNECTION_FACTORY and type String, you can modify its value after you have deployed the application by entering jmsfactory/default/QueueConnectionFactory in the Value field. After changing the bean’s environment entry value, choose Save.
Full Details
You can view the full details of each enterprise bean in the selected EJB module. Using the full details you can easily determine whether a bean is 2.1 or 3.0. Enterprise beans 2.1 have home, remote, local and/or local home interfaces listed in the General tab, while enterprise beans 3.0 have local business and/or remote business interfaces listed in the Local Business Interfaces and/or Remote Business Interfaces tabs respectively. You can also have beans 3.0 with client view 2.1, that is, beans 3.0 with home, remote, local and/or local home interfaces. The tabs that appear in Full Details depend on the type of the enterprise bean, that is, some of the tabs are different for session and message-driven beans. These tabs visualize their specific properties.
You can also view:
● EJB class
● JNDI name
● type of the transaction – bean or container managed
● service endpoint, if any
● local JNDI name, if any
● messaging type if the bean is message-driven bean
● destination type if the bean is message-driven bean
● destination link if the bean is message-driven bean
More information