The Resource Manager for Enterprise Beans

The Resource Manager for Enterprise Beans enables you, as an EJB application developer, to perform certain actions on the EJB resources, without having to know too much about CICS®. It uses a web browser as the interface, so that there is no other technology for you to install to gain access to this tool.

The Resource Manager for Enterprise Beans can:

Preparing the Resource Manager for Enterprise Beans for use

To setup your system so that the Resource Manager for Enterprise Beans is available, there are three things to do:

When these three steps are done, you’re ready to use the Resource Manager for Enterprise Beans. Start up your browser and direct it at program DFHADWB0.

For example, using a system known to mainoffice.myorg.com as System5 and with port 9999 the URM is:

http://system5.mainoffice.myorg.com:9999/cics/cwba/dfhadwb0

Installing definitions

The group DFHADET contains all of the definitions needed for the Resource Manager for Enterprise Beans and a file definition for DFHADEM. The group DFHADET is not automatically installed as part of DFHLIST as it might not be wanted in a production region. Even if it were acceptable to you that these functions were available in a production region, you should consider whether the potential performance impact is acceptable. DFHADET can be added to your own list to be installed at start up.

The Resource Manager for Enterprise Beans requires Language Environment® runtime support. Without this, you can expect to see an abend when attempting to start it from your browser.

Defining the DFHADEM data set

The DFHADEM file is a VSAM key-sequenced data set (KSDS).

Define this file on a DD card in your CICS JCL. If you do not, you will receive no error messages regarding failures during DJAR installations (although the rest of the tool will be usable).

The JCL to create this file is defined as part of DFHDEFDS. For an example, see Figure 66.

Figure 66. JCL to create the DFHADEM data set
Start of change//ADEMJOB  JOB  'accounting information',name,MSGCLASS=A 
//*
//RMEBDEF  EXEC PGM=IDCAMS,REGION=1M                     
//SYSPRINT DD SYSOUT=*                                   
//SYSIN    DD *                                          
 DELETE CICSTS31.CICS.DFHADEM                        
 SET MAXCC=0                                             
 DEFINE  CLUSTER (NAME(CICSTS31.CICS.DFHADEM)-       
            INDEXED-        
            LOG(NONE)-
            VOLUME(SYSDAV)-
            RECORDSIZE( 284 284 )-        
            RECORDS( 10000 00 )-        
            KEYS( 40 0 )-        
         DATA (NAME(CICSTS31.CICS.DFHADEM.DATA)       -  
            CONTROLINTERVALSIZE(8192))          -        
         INDEX (NAME(CICSTS31.CICS.DFHADEM.INDEX)      -  
            CONTROLINTERVALSIZE(512))                    
/*   End of change

Defining a TCPIPSERVICE

Define a TCPIP service for the HTTP protocol. If you're running with security enabled, ensure that the TCPIP service uses at least basic authentication, otherwise you will get reduced function from the Resource Manager for Enterprise Beans.

Here is an example of a suitable TCPIPSERVICE definition. Make sure that you select a port number that is not in use :

Start of change

CEDA  View TCpipservice( WEBTCPS  )                                          
 TCpipservice   : WEBTCPS                                                    
 GROup          : TEST                                                       
 DEscription    :                                                            
 Urm            : DFHWBADX                                                   
 POrtnumber     : 9999               1-65535                                 
 STatus         : Open               Open | Closed                           
 PRotocol       : Http               Iiop | Http | Eci | User                
 TRansaction    : CWXN                                                       
 Backlog        : 00005              0-32767                                 
 TSqprefix      :                                                            
 Ipaddress      :                                                            
 SOcketclose    : No                 No | 0-240000 (HHMMSS)                  
 Maxdatalen     :                       3-524288
SECURITY                                                                     
 SSl            : No                 Yes | No | Clientauth                   
 CErtificate    :                                                            
 PRIvacy        : Supported          Notsupported | Required | Supported
 CIphers        : 0504352F0A0903060102
 AUthenticate   : Basic               No | Basic | Certificate | AUTORegister 
                                     | AUTOMatic                             
 ATtachsec      :                    Local | Verify  
DNS CONNECTION BALANCING
 DNsgroup       :                                    
 GRPcritical    : No                 No | Yes  
End of change

Using RMEB

Start the Resource Manager for Enterprise Beans by directing your web browser to the URL that was defined during the setup process (see Preparing the Resource Manager for Enterprise Beans for use).

On each panel displayed by the Resource Manager for Enterprise Beans:

For each button that is displayed by the Resource Manager for Enterprise Beans, there is help information which appears if you leave the mouse pointer over the button for a few moments, and if you are using Internet Explorer as your browser. (At the time of writing, not all browsers do this.)

User Login

The Resource Manager for Enterprise Beans requires you to be authenticated with CICS (if CICS security is switched on), before you can use the other functions of the tool. This authentication is provided by CICS via a web browser logon box. The tasks that are subsequently started are run using the authenticated ID, and usual RACF® security applies.

CORBASERVER Screen

Once you have logged on, the first screen you are shown is a view of the CORBASERVER definitions currently installed in the region, see Figure 67.

Figure 67. Resource Manager for Enterprise Beans - CORBASERVER definitions screen
 The picture shows the first panel presented by the Resource Manager for Enterprise Beans. It is described in the text.

On this panel the navigation frame on the left only shows CORBASERVER.

The Help panel for the CORBASERVER screen

 

The Help panel for the CORBASERVER screen presents this information:

Select CORBASERVER Help

This page displays a list of the CORBASERVERs currently installed in the CICS 
region. Select a CORBASERVER that has a State of ‘IN SERVICE’, then 
click the Continue button in order to work with that resource. 

DJAR Screen

The DJAR Screen (see Figure 68) presents a list of all the DJAR definitions which are currently installed the region, and associated with the selected CORBASERVER definition. The JAR file associated with each DJAR is also displayed.

Figure 68. Resource Manager for Enterprise Beans - DJAR definitions screen
 The picture shows the DJAR panel presented by the Resource Manager for Enterprise Beans. It is described in the text.

On this panel the navigation frame on the left shows CORBASERVER and DJAR.

The Help panel for the DJAR screen

 

The Help panel for the DJAR screen presents this information:

Select DJARs Help

This page displays a list of all the DJARs currently installed to the current 
CORBASERVER. 
 
Sort by Name 
Sort the DJAR list by CICS resource name.  

Sort by Date 
Sort the DJAR list by Last Modified date.  

Scan 
Scan the CORBASERVER pickup directory and create DJAR definitions for new 
or updated JAR files.  

Select All 
Select all the DJAR definitions in the list.  

Select None 
Unselect all the DJAR definitions in the list.  

Refresh 
Update the list with the DJARs currently associated with this CORBASERVER.  

Details 
View the session beans or error messages associated with the selected 
DJAR definitions.  

Discard 
Discard the selected CICS DJAR resource definitions.  

Publish 
Publish the session beans in the JAR files associated with the selected DJAR 
definitions to the JNDI namespace.  

Retract 
Retract the session beans in the JAR files associated with the selected DJAR 
definitions from the JNDI namespace.
Actions on the DJAR panel

 

Sort by Name, Sort by Date, Scan, Refresh, Select All and Select None perform the action requested and refresh the displayed information.

Discard, Publish and Retract perform the action requested each of the selected DJARs and present a screen with:

a message about the result of that action. and a prompt to Continue, which returns you to the DJAR panel for further actions.

Details takes you to the next and final panel of the Resource Manager for Enterprise Beans Details screen.

Details screen

The Details screen (see Figure 69) shows the session beans contained in the JAR file associated with each of the selected DJARs. If more than one DJAR definition has been selected, then this screen will show information related to all of the selected DJAR definitions.

Figure 69. Resource Manager for Enterprise Beans - JAR file screen
 The picture shows the Details panel presented by the Resource Manager for Enterprise Beans. It is described in the text.

On this panel the navigation frame on the left shows CORBASERVER, DJAR and Details.

There is no action button on this panel. Use the navigation frame or the browser’s back button to move to whatever you want to see next.

If the DJAR is not resolved, no information about the contents of the JAR file is displayed. Instead, an error message gives the specific reason for the failure. In Figure 70, the second paragraph under "MissingResource" contains the specific error message. Note that, if the Resource Manager for Enterprise Beans has not been installed correctly, the same panel may appear, but without the specific error message.

Figure 70. Resource Manager for Enterprise Beans - JAR file screen for an unresolved JAR file
 The picture shows the Details panel presented by the Resource Manager for Enterprise Beans for an unresolved JAR file.
The Help panel for the Details screen

 

The Help panel for the Details screen presents this information:

Details Help

The names of IN SERVICE DJAR definitions are listed 
with the filename of the corresponding JAR file. Each is followed by a list 
of the session beans in that JAR file. 

For each session bean, if published successfully, the display shows the 
relative name by which the bean is published. Sometimes it is not possible 
to find a published reference for a bean because the CORBASERVER’s 
TCPIPSERVICE is closed. If the bean cannot be found in the JNDI namespace 
then NOT PUBLISHED (or TCPIPSERVICE closed) appears.

DJAR definitions that are not IN SERVICE are displayed with a 
message indicating any problems.
[[ Contents Previous Page | Next Page Index ]]