Understand What the WebLogic MBeanMaker Provides

Design Considerations 3-13 Figure 3–6 DefaultCredentialMapper Administration Console Page The Name, Description, and Version fields come from attributes with these names inherited from the base required SSPI MBean called Provider and specified in the DefaultCredentialMapper MDF. Note that the DisplayName attribute in the DefaultCredentialMapper MDF generates the value for the Name field, and that the Description and Version attributes generate the values for their respective fields as well. The Credential Mapping Deployment Enabled field is displayed on the Provider Specific page because of the CredentialMappingDeploymentEnabled attribute in the DeployableCredentialMapper required SSPI MBean, which the DefaultCredentialMapper MDF extends. Notice that this Administration Console page does not display a field for the DefaultCredentialMapper implementation of the UserPasswordCredentialMapEditor optional SSPI MBean.

3.3.5 Understand What the WebLogic MBeanMaker Provides

The WebLogic MBeanMaker is a command-line utility that takes an MBean Definition File MDF as input and outputs files for an MBean type. When you run the MDF you created through the WebLogic MBeanMaker, the following occurs: ■ Any attributes inherited from required SSPI MBeans—as well as any custom attributes you added to the MDF—cause the WebLogic MBeanMaker to generate complete gettersetter methods in the MBean types information file. The MBean information file is not shown in Figure 3–7 . For more information about the MBean information file, see Section 3.3.5.1, About the MBean Information File. Necessary developer action: None. No further work must be done for these methods. ■ Any operations inherited from optional SSPI MBeans cause the MBean implementation file to inherit their methods, whose implementations you must supply from scratch. Necessary developer action: Currently, the WebLogic MBeanMaker does not generate method stubs for these inherited methods, so you will need to supply the appropriate implementations. ■ Any custom operations you added to the MDF will cause the WebLogic MBeanMaker to generate method stubs. Necessary developer action: You must provide implementations for these methods. However, because the WebLogic MBeanMaker generates the stubs, you do not need to look up the Java method signatures. This is illustrated in Figure 3–7 . 3-14 Developing Security Providers for Oracle WebLogic Server Figure 3–7 What the WebLogic MBeanMaker Provides

3.3.5.1 About the MBean Information File

The MBean information file contains a compiled definition of the data in the MBean Definition File in a form that JMX Model MBeans require. The format of this file is a list of attributes, operations, and notifications, each of which also has a set of descriptor tags that describe that entity. In addition, the MBean itself also has a set of descriptor tags. An example of this format is as follows: MBean + tags attribute1 + tags, attribute2 + tags ... operation1 + tags, operation2 + tags ... notification1 + tags, notification2 + tags ... If desired, you can access this information at runtime by calling the standard JMX server getMBeanInfo method to obtain the ModelMBeanInfo.

3.3.6 SSPI MBean Quick Reference