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
From: rules-users-bounces@lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Vikas Phonsa
Sent: Monday, June 09, 2008 5:47
PM
To: Rules Users List
Subject: RE: [rules-users] BRMS on
Weblogic
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
From:
rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org]
On Behalf Of Majeed, Atif
Sent: Monday, June 09, 2008 11:45
AM
To:
Subject: RE: [rules-users] BRMS on
Weblogic
>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
From:
rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org]
On Behalf Of Vikas Phonsa
Sent: Monday, June 09, 2008 2:34
PM
To:
Subject: RE: [rules-users] BRMS on
Weblogic
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
From:
rules-users-bounces@lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Paul Browne
Sent: Thursday, June 05, 2008 9:00
AM
To:
Subject: Re: [rules-users] BRMS on
Weblogic
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
On Thu, Jun 5, 2008 at 3:58 PM, Vikas Phonsa <VPhonsa@mercuryinsurance.com>
wrote:
Paul,
Thanks a
lot for writing back.
>>>Just
so that I can update the page, when you say 'that didn't help' can you tell me
what problems you are seeing / what you feel is missing?
Sorry if
that didn't come across right. That page did help a lot. I followed the
instructions on that page. That fixed the JSF related exceptions that I was initially
getting. But then I got that other NullPointerException whose stack trace that
I listed in my last email. That's the only exception that I see in the log. And
The BRMS shows me an error message and then doesn't display the login page.
And I did
bring in the JSF dependencies. I still get the same exception.
Your Wiki
page is very good. I just am getting an exception that I am unable to find a
solution for.
Do you
know if it matters whether I use the JRocket JVM or Sun's JVM in the Weblogic
server ?
Also, did you get a chance to look at this http://www.seamframework.org/Community/GWTRPCCallFails
I would
appreciate any other input that you give.
Regards,
Vikas
From: rules-users-bounces@lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org]
On Behalf Of Paul Browne
Sent: Thursday, June 05, 2008 7:26
AM
To:
Subject: Re: [rules-users] BRMS on
Weblogic
Vikas,
Thanks for your note - I'm the person that wrote the JBoss_Drools_BRMS_on_Weblogic page that you mention.
Just so that I can update the page, when you say 'that didn't help' can you
tell me what problems you are seeing / what you feel is missing?
I'm guessing that you've already seen the page http://wiki.jboss.org/wiki/JBRMSjsfdependencies
- did it help you at all?
Regards
Paul
On Wed,
Jun 4, 2008 at 6:55 PM, Vikas Phonsa <VPhonsa@mercuryinsurance.com>
wrote:
Hi All,
I'm trying to run BRMS 4.0.7 on Weblogic 9.2.0.0. It won't run and I'm
getting the exception listed below.
I looked at the Drools Wiki entry :
http://www.firstpartners.net/kb/index.php/JBoss_Drools_BRMS_on_Weblogic
That didn't help.
I also found something about this exception at Seam's website:
http://www.seamframework.org/Community/GWTRPCCallFails
As per the instructions mentioned in the above website, I brought the
jboss-seam-remoting.jar into my lib directory, but that didn't help.
Does anybody have any idea? Has anybody been able to successfully run
BRMS on Weblogic ?
Thanks,
Vikas
------------Exception Stack Trace-----------------
####<Jun 4, 2008 10:26:56 AM PDT> <Error>
<ServletContext-/drools-jbrms>
<BRITHOST1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for
queue:
'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <>
<>
<1212600416656> <000000> <Exception while dispatching incoming
RPC call
java.lang.NullPointerException
at
org.jboss.seam.remoting.gwt.GWTToSeamAdapter.callWebRemoteMethod(GWTToSe
amAdapter.java:67)
at
org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.processCall(GWTRemot
eServiceServlet.java:290)
at
org.jboss.seam.remoting.gwt.GWTRemoteServiceServlet.doPost(GWTRemoteServ
iceServlet.java:172)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
ubSecurityHelper.java:225)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
elper.java:127)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
83)
at
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:
42)
at
org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42)
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpSe
rvletRequest.java:46)
at
org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:
42)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:3212)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
letContext.java:1983)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
ext.java:1890)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java
:1344)
at
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
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.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
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.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
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.