Identity Assertion Providers 5-15
5.4.2.2.1 No Optional SSPI MBeans and No Custom Operations If the MDF for your custom
Identity Assertion provider does not implement any optional SSPI MBeans and does not include any custom operations, follow these steps:
1.
Create a new DOS shell.
2.
Type the following command: java -DMDF=xmlfile -Dfiles=filesdir -DcreateStubs=true
weblogic.management.commo.WebLogicMBeanMaker where the -DMDF flag indicates that the WebLogic MBeanMaker should translate
the MDF into code, xmlFile is the MDF the XML MBean Description File and filesdir is the location where the WebLogic MBeanMaker will place the
intermediate files for the MBean type.
Whenever xmlfile is provided, a new set of output files is generated. Each time you use the -DcreateStubs=true flag, it overwrites any existing
MBean implementation file.
3.
Proceed to Section 5.4.2.3, Use the WebLogic MBeanMaker to Create the MBean
JAR File MJF.
5.4.2.2.2 Optional SSPI MBeans or Custom Operations If the MDF for your custom Identity
Assertion provider does implement some optional SSPI MBeans or does include custom operations, consider the following:
Are you creating an MBean type for the first time? If so, follow these steps:
1.
Create a new DOS shell.
2.
Type the following command: java -DMDF=xmlfile -Dfiles=filesdir -DcreateStubs=true
weblogic.management.commo.WebLogicMBeanMaker where the -DMDF flag indicates that the WebLogic MBeanMaker should translate
the MDF into code, xmlFile is the MDF the XML MBean Description File and filesdir is the location where the WebLogic MBeanMaker will place the
intermediate files for the MBean type.
Whenever xmlfile is provided, a new set of output files is generated. Each time you use the -DcreateStubs=true flag, it overwrites any existing
MBean implementation file.
Note: As of version 9.0 of WebLogic Server, you can also provide a
directory that contains multiple MDFs by using the -DMDFDIR MDF directory name option. In prior versions of WebLogic Server,
the WebLogic MBeanMaker processed only one MDF at a time. Therefore, you had to repeat this process if you had multiple MDFs in
other words, multiple Identity Assertion providers.
5-16 Developing Security Providers for Oracle WebLogic Server
3.
If you implemented optional SSPI MBeans in your MDF, follow these steps:
a.
Locate the MBean implementation file. The MBean implementation file generated by the WebLogic MBeanMaker is
named MBeanNameImpl.java. For example, for the MDF named SampleIdentityAsserter, the MBean implementation file to be edited is
named SampleIdentityAsserterImpl.java.
b.
For each optional SSPI MBean that you implemented in your MDF, implement each method. Be sure to also provide implementations for any methods that
the optional SSPI MBean inherits.
4.
If you included any custom operations in your MDF, implement the methods using the method stubs.
5.
Save the file.
6.
Proceed to Section 5.4.2.3, Use the WebLogic MBeanMaker to Create the MBean
JAR File MJF. Are you updating an existing MBean type? If so, follow these steps:
1.
Copy your existing MBean implementation file to a temporary directory so that your current method implementations are not overwritten by the WebLogic
MBeanMaker.
2.
Create a new DOS shell.
3.
Type the following command: java -DMDF=xmlfile -Dfiles=filesdir -DcreateStubs=true
weblogic.management.commo.WebLogicMBeanMaker where the -DMDF flag indicates that the WebLogic MBeanMaker should translate
the MDF into code, xmlFile is the MDF the XML MBean Description File and filesdir is the location where the WebLogic MBeanMaker will place the
intermediate files for the MBean type.
Whenever xmlfile is provided, a new set of output files is generated. Each time you use the -DcreateStubs=true flag, it overwrites any existing
MBean implementation file.
4.
If you implemented optional SSPI MBeans in your MDF, follow these steps:
Note: As of version 9.0 of WebLogic Server, you can also provide a
directory that contains multiple MDFs by using the -DMDFDIR MDF directory name option. In prior versions of WebLogic Server,
the WebLogic MBeanMaker processed only one MDF at a time. Therefore, you had to repeat this process if you had multiple MDFs in
other words, multiple Identity Assertion providers.
Note: As of version 9.0 of WebLogic Server, you can also provide a
directory that contains multiple MDFs by using the -DMDFDIR MDF directory name option. In prior versions of WebLogic Server,
the WebLogic MBeanMaker processed only one MDF at a time. Therefore, you had to repeat this process if you had multiple MDFs in
other words, multiple Identity Assertion providers.
Identity Assertion Providers 5-17
a.
Locate and open the MBean implementation file. The MBean implementation file generated by the WebLogic MBeanMaker is
named MBeanNameImpl.java. For example, for the MDF named SampleIdentityAsserter, the MBean implementation file to be edited is
named SampleIdentityAsserterImpl.java.
b.
Open your existing MBean implementation file which you saved to a temporary directory in step 1.
c.
Synchronize the existing MBean implementation file with the MBean implementation file generated by the WebLogic MBeanMaker.
Accomplishing this task may include, but is not limited to: copying the method implementations from your existing MBean implementation file into
the newly-generated MBean implementation file or, alternatively, adding the new methods from the newly-generated MBean implementation file to your
existing MBean implementation file, and verifying that any changes to method signatures are reflected in the version of the MBean implementation
file that you are going to use for methods that exist in both MBean implementation files.
d.
If you modified the MDF to implement optional SSPI MBeans that were not in the original MDF, implement each method. Be sure to also provide
implementations for any methods that the optional SSPI MBean inherits.
5.
If you modified the MDF to include any custom operations that were not in the original MDF, implement the methods using the method stubs.
6.
Save the version of the MBean implementation file that is complete that is, has all methods implemented.
7.
Copy this MBean implementation file into the directory where the WebLogic MBeanMaker placed the intermediate files for the MBean type. You specified this
as filesdir in step 3. You will be overriding the MBean implementation file generated by the WebLogic MBeanMaker as a result of step 3.
8.
Proceed to Section 5.4.2.3, Use the WebLogic MBeanMaker to Create the MBean
JAR File MJF.
5.4.2.2.3 About the Generated MBean Interface File The MBean interface file is the
