Thanks Atif,

 

I did find some documentation on configuring new realms. In case you are interested: http://edocs.bea.com/wls/docs81/secmanage/realm.html#1186823

 

After you enabled security, did you have to do some special configuration for the Rule Agent to have it access the package URLs (under BRMS).

 

With security enabled, won’t the Rule Agent (or something on the client side) need username and password to download pkg binaries from the URLs pointing to deployed package snapshots?

 

Also did you enable SSL on Web Logic? If yes, I guess a key store would have to be used on the client side.

 

Thanks once again.

 

Vikas

 

 

 

 

I did not have to create a new security realm. I added users/group in default ‘myrealm’. I have not tried using external LDAP. Weblogic documentataion/user list might be helpful in this regard.

 

Atif

 

Atif,

 

Thanks a lot. That was very helpful. I have a couple of questions though.

 

Did you have to create or configure a security realm? Weblogic has a security realm called “myrealm” configured by default. Do you know if the UsernamePasswordLoginModule uses “myrealm” by default?

 

I need to use an external LDAP (and not the one build in with Weblogic server ). I guess I would have to configure a new realm and providers. Do you know what needs to be done to have the UsernamePasswordLoginModule use the new realm (and hence the external LDAP).

 

Thanks again for your help.

 

Vikas

 

 

 

 

>BTW, have you ever configured and used a Weblogic JAAS module with BRMS.

 

I posted the instructions in this blog.

http://atif-majeed.blogspot.com/2008/04/setting-up-brms-security-on-weblogic.html

 

 

Atif

 

Paul,

 

I was able to run BRMS on Weblogic. Looks like the Weblogic Workspace IDE was creating some jar conflicts. When I created a domain, I selected the option to configure it for Workspace also.

 

After trying many different things (and getting thoroughly frustrated J ), I created a new domain and configured it just for the Weblogic server. Put the right JSF jars in domain lib and deployed BRMS war from the console and it started up fine.

 

I have some exceptions related to DB2 Persistence Manager, but the application is running.

 

Thanks for your help.

 

BTW, have you ever configured and used a Weblogic JAAS module with BRMS.

 

Thanks,

Vikas

 

 

 

 

Vikas,

I've always used Sun's JVM; mainly out of habit and one less thing to investigate if things go wrong. It's worth trying Sun's in this case if you're using the JRocket JVM.

Can you look at the Seam source code to see what is causing the NullPointerException at
GWTToSeamAdapter.java line 67? I don't have the source to hand at the moment. My guess is that there is an issue on the server somewhere (i.e. some missing or conflicted libs) but have no more detailled wisdom :-(.

Paul

 

This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.

This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.