[JBoss Portal] - Re: Dashboard show to other users
by andiXT
Its easy - every user might configure its own dashboard, apply own theme, add desired portlets - another words - create its own page. After then this dashboard might use other users - just view its content.
Examples:
Car renting portal. Administrator of portal has configured only default portal with welcome page, explanations and thats all. After that every registered user (actually depending on role which is owner) receives pre-configured portal with set of pages and portlets on them. This user is owner of this portal and might change theme of this portal, location of portlets, and add or remove some portlets from his own portal. In his portal he publishes its car to be rented.
Another user, who registers himself as owner, also receives its portal, where he changes theme, portlets, etc. And so on.
Currently we have implemented such scenario by building new portal for every owner. But we have investigated, that in case of very big amount of portals performance of JBoss Portal significantly drops down.
Actually configuration of own portal is almost the same, as every user might configure its own dashboard. I think, since dashboard is only one, it doesn't affect so much performance and its possible probably to use in our scenario in case of big amount of users. But the main problem how to show my own dashboard to other users.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205459#4205459
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205459
17 years, 2 months
[EJB 3.0] - Re: MDB redeploy with ...-service.xml
by jaikiran
"Wolfgang Knauf" wrote : Hi jaikiran,
|
| the -service.xml in META-INF instead of the JAR root ...
| The first error (javax.management.InstanceAlreadyExistsException) is gone.
|
As i suspected, this looks like some issue with JBossAS-5 deployment. Maybe you could open a thread in our AS5 forum to see if someone has more inputs.
anonymous wrote : So I assume that -service.xml files MUST be placed in META-INF? Is this correct?
Not sure. AS5 forum may provide an answer :) But if placing it at the root of the jar is incorrect, then atleast the deployer should not throw a AlreadyExistsException.
"Wolfgang Knauf" wrote :
| results only in this error:
|
| | javax.naming.NameNotFoundException: MessageBeanQueue not bound
| | at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
| | at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
| | ...
| | 21:14:01,335 INFO [QueueService] Queue[queue/MessageBeanQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
|
|
| For the "NameNotFoundException": is there some dependency of the MDB deployer to the service deployer, which is in the wrong order?
|
| Thanks
|
| Wolfgang
Yes, looks like an ordering issue. Going by the logs, you first see the error and then the successful binding of the queue. Add a @Depends on your MDB (either the annotation or through deployment descriptor jboss.xml) to prevent the MDB from deploying before the queue is deployed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205458#4205458
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205458
17 years, 2 months
[JBoss Portal] - Re: Admin role ignored when fetched from LDAP
by olivsch7
Hello,
yes, I can. But you'll see that the configuration is disappointingly simple ;-):
| <login-module code="org.jboss.portal.identity.auth.SynchronizingLDAPExtLoginModule" flag="sufficient">
| <module-option name="synchronizeIdentity">true</module-option>
| <module-option name="synchronizeRoles">true</module-option>
| <module-option name="preserveRoles">false</module-option>
| <module-option name="additionalRole">Authenticated</module-option>
| <module-option name="defaultAssignedRole">User</module-option>
| <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
| <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
| <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
| <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
| <module-option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</module-option>
| <module-option name="java.naming.provider.url">ldap://address:389/</module-option>
| <module-option name="java.naming.security.authentication">simple</module-option>
| <module-option name="bindDN">cn=Directory Manager</module-option>
| <module-option name="bindCredential"></module-option>
| <module-option name="baseCtxDN">ou=People,o=boschrexroth</module-option>
| <module-option name="baseFilter">(uid={0})</module-option>
| <module-option name="rolesCtxDN">ou=Roles,o=boschrexroth</module-option>
| <module-option name="roleFilter">(member={1})</module-option>
| <module-option name="roleAttributeID">cn</module-option>
|
| <module-option name="roleRecursion">-1</module-option>
| <module-option name="searchTimeLimit">10000</module-option>
| <module-option name="searchScope">SUBTREE_SCOPE</module-option>
| <module-option name="allowEmptyPasswords">false</module-option>
| </login-module>
|
| <login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="sufficient">
| <module-option name="unauthenticatedIdentity">guest</module-option>
| <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
| <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
| <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option>
| <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option>
| <module-option name="validateUserNameCase">true</module-option>
| <module-option name="additionalRole">Authenticated</module-option>
| </login-module>
Although it's no problem to use roles instead of groups, this issue should be covered anyhow. Well, let's see what we can find out.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205457#4205457
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205457
17 years, 2 months
[JBoss jBPM] - drools in jbpm-console
by nl＠ap
Hi,
is there a way to get the rulesActionHandler example run in the jbpm-console?
I'm getting the following error on starting an instance:
08:12:36,160 ERROR [GraphElement] action threw exception: Unable to resolve ObjectType 'Customer' : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| Unable to resolve ObjectType 'Order' : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| org.jbpm.action.Customerorg.jbpm.action.OrderRule Compilation error : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| org/jbpm/action/Rule_Determine_Shipper_0.java (2:33) : Only a type can be imported. org.jbpm.action.Customer resolves to a package
| org/jbpm/action/Rule_Determine_Shipper_0.java (2:109) : Only a type can be imported. org.jbpm.action.Order resolves to a package
|
| org.drools.rule.InvalidRulePackage: Unable to resolve ObjectType 'Customer' : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| Unable to resolve ObjectType 'Order' : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| org.jbpm.action.Customerorg.jbpm.action.OrderRule Compilation error : [Rule name=Determine Shipper, agendaGroup=MAIN, salience=0, no-loop=false]
| org/jbpm/action/Rule_Determine_Shipper_0.java (2:33) : Only a type can be imported. org.jbpm.action.Customer resolves to a package
| org/jbpm/action/Rule_Determine_Shipper_0.java (2:109) : Only a type can be imported. org.jbpm.action.Order resolves to a package
|
| at org.drools.rule.Package.checkValidity(Package.java:424)
| at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:394)
| at org.jbpm.action.RulesActionHandler.readRule(RulesActionHandler.java:95)
| at org.jbpm.action.RulesActionHandler.execute(RulesActionHandler.java:39)
| at org.jbpm.graph.def.Action.execute(Action.java:122)
it looks like drools can't find any of the deployed beans, while it does find those if running in a standalone app. So I don't thing this is a drools problem.
Does anyone know how to resolve this problem?
BTW: I'm using jbpm-jpdl-3.2.3.
Thanks,
Niels
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205454#4205454
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205454
17 years, 2 months
[Installation, Configuration & DEPLOYMENT] - jboss and tivoli ldap
by jagkuar86
I tried to configure jboss portal 2.6.7 with tivoli ldap like the way specified in the reference manual but i m getting the following error.
2009-01-27 19:06:53,281 ERROR [org.jboss.portal.identity.auth.IdentityLoginModule] Error when validating password
org.jboss.portal.common.transaction.NestedException: javax.security.auth.login.LoginException: org.jboss.portal.identity.IdentityException: Unable to connect to LDAP: Name: null, Host: ldap://hostip, Port: 389, Context factory: com.sun.jndi.ldap.LdapCtxFactory, Admin user: cn=userid, Admin password: ***, Authentication: simple, Protocol: null
at org.jboss.portal.common.transaction.Transactions.apply(Transactions.java:253)
at org.jboss.portal.common.transaction.Transactions.required(Transactions.java:289)
at org.jboss.portal.identity.auth.IdentityLoginModule.getUserStatus(IdentityLoginModule.java:233)
at org.jboss.portal.identity.auth.IdentityLoginModule.validatePassword(IdentityLoginModule.java:185)
at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:257)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:416)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
This conect string is working fine with my present wps and ldap configuration.
i searched through forum but i could not solve it can anyone help me out.
thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205453#4205453
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205453
17 years, 2 months