Comments on: Maven and WebLogicMBeanMaker in WebLogic 9/10

By: Manet

Manet — Fri, 07 Aug 2009 03:44:57 +0000

I’ve finally found the solution.
Since I have the validation to go through my customised authenticator, I need to set Default Weblogic Authenticator flag = “Sufficient” instead of “Required”. It solved the problem.

From what I observed, this line
sa.weak(request, response);
actually validates with all available authenticators including default.

By: Mike Fleming

Mike Fleming — Tue, 21 Jul 2009 23:37:42 +0000

Sorry, Manet, but I don’t know.

By: Manet

Manet — Tue, 21 Jul 2009 03:44:11 +0000

Thanks for the tip. I’ve got my build working. However, I still have problem with weblogic.servlet.security.ServletAuthentication.weak() function always return 1 (FAILED_AUTHENTICATE) instead of 0 (AUTHENTICATED).

My code:
ServletAuthentication sa = new ServletAuthentication(LOGIN_USERNAME_LABEL, LOGIN_PASSWORD_LABEL); int authenticated = sa.weak(request, response);
Result authenticated = 1, even though username/password provided correctly (yes i am sure user/pswd are correct)

Do you have any idea?

By: Mike Fleming

Mike Fleming — Fri, 05 Jun 2009 01:10:18 +0000

Thanks for the tip, Darryl. I’ve seen that problem with Ant. Perhaps that’s what bit you.

BTW, I’ve pared down the WLS dependencies required for a security provider build such that I don’t need a WLS installation anymore. Now I just need to write it up…

By: Darryl S

Darryl S — Fri, 05 Jun 2009 00:28:31 +0000

Not sure if its related but I had all kinds of problems with weblogic and maven when creating a weblogic deployer plugin for maven. I ultimately found that certain weblogic utilities will not work well with a classpath that contains spaces. So I ended up moving my maven repo out from Documents and Settings (e.g moved to \dev\.m2) and all the problems went away.

By: Mike Fleming

Mike Fleming — Sun, 30 Dec 2007 02:52:43 +0000

Doug,

Thanks for the comment. Yes, yours would be a better way but have you figured out how to make that structure work in the Maven repository? That’s what I’d really like to have…

By: Doug Harmon

Doug Harmon — Sun, 30 Dec 2007 00:01:41 +0000

Instead of using a WebLogic installation directory, your WL jars that you depend on need to have the same directory structure as the WL install directory. This is due to the fact that weblogic.jar’s manifest has a class-path attribute that depends on other jar files that are likely missing or could not be resolved as the directory structed was incorrect.

By: Mike Fleming

Mike Fleming — Sat, 01 Sep 2007 00:27:11 +0000

Thanks for the info, Satya.

By: Satya Ghattu

Satya Ghattu — Fri, 31 Aug 2007 14:14:35 +0000

Mike,
If I remember correctly the Maker tool uses weblogic.Home.getHome() to get to the BEA installation directory and appends the relative path’s to various different jars it depends on. For instance to get to wlManagment.jar, it will get the installation directory by calling weblogic.Home.getHome() and appends “/server/lib/mbeantypes” to get to the location of wlManagement.jar. As you may have noticed the Maker tool spawns a new JVM couple of times to get some things done and these VM’s needed a special classpath to run. And that is one of the reasons it is slow.
If you have a 8.1 provider already built using some build mechanisms, I wouldn’t throw it out, because after you build your old provider you can just simply upgrade it using the upgrade tool. The upgrade tool will internally call the MBeanMaker, but I guess you will see this Home issue even then if you are not using weblogic.jar from the installation directory.

By: Mike Fleming

Mike Fleming — Fri, 31 Aug 2007 02:27:08 +0000

Satya,

Thanks for responding. No need for any guilt, though. WebLogicMBeanMaker works just fine until one tries to shoe-horn it into a Maven build. Obviously, even that can be done after learning the tricks.

What’s funny is that I never actually stopped to ponder what the new schema files were for. Now I know.

Do you have any insight on the weblogic.Home problem mentioned in the post?

Are you saying that the upgrade tool would be a viable option for migrating a “living” security provider? I always assumed that the tool was a one-shot deal for when you didn’t have source.

Thanks,

Mike

By: Satya Ghattu

Satya Ghattu — Fri, 31 Aug 2007 01:29:29 +0000

Thanks for the post and I feel a bit guilty for the problems you are seeing, since I was responsible for WebLogicMBeanMaker tool while I was at BEA. Yes WebLogicMBeanMaker has gone through a lot of change in 9.0 to comply with the new MBean hierarchy model and management API’s. As you have noticed the jar file is a bit bloated, this is because it contains the XSB bindings and schema files that help WebLogic in persisting the security configuration to config.xml (BTW config.xml is schema based). Also, if you are migrating from WLS 8.1 and have a few security providers, you can use the Upgrade tool which may be the best way. See my blog entry at http://dev2dev.bea.com/blog/sghattu/archive/2005/08/upgrading_your.html