Issues while creating weblogic Custom Security Provider

One of the most important and common errors that generally comes while creating the Custom Security Providers is :

om.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for XXXXXX is not specified.

The above error comes due to incorrect usage of the Weblogic Mbean maker.

We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:

Let us take the example of Windows OS:

C:/Providers                       ————— This is the base Directory for Customer security Provider.
C:/Providers/src               ————— This is the directory for the Source Code.
C:/Providers/providersjar ————- This is the directory for the Custom Provider Jar file .
C:/Providers/created_files ———— This is the Directory for the created schema file by Mbean maker.

  • The important thing needs to kept in mind is that the directory for the created files should always be different from the Source directory and the Directory where thee=”color: #993300;”>[Security:097533]SecurityProvider service class name for XXXXXX is not specified.

    The above error comes due to incorrect usage of the Weblogic Mbean maker.

    We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:

    Let us take the example of Windows OS:

    C:/Providers                       ————— This is the base Directory for Customer security Provider.
    C:/Providers/src               ————— This is the directory for the Source Code.
    C:/Providers/providersjar ————- This is the directory for the Custom Provider Jar file .
    C:/Providers/created_files ———— This is the Directory for the created schema file by Mbean maker.

    • The important thing needs to kept in mind is that the directory for the created files should always be different from the Source directory and the Directory where the Jar is created.
    • And every time when you need to run the Weblogic Mbean maker then the Created Files directory and the providersjar directory should be completely deleted, otherwise the Weblogic mbean maker will run successfully without any error but afte
      Please follow and like us:

3 Comments

  1. kuldip December 9, 2010
  2. weblogictips June 10, 2010
  3. weblogicwonders June 10, 2010