What do you mean by a application server?
If you mean that you have some application implementing your business logic
(perhaps as EJB3's) and you then have your portlets as a way to realize your UI
towards that application, then surely the portlets and the business app can
reside on different
Well I do not mean the AS where the business logic resides. I mean to say the
portal server's app server only and as you suggested that in case of WSRP also
we have multiple portal servers and hence multiple app servers.
Why I am calling this as tightly coupled is because a portal application
Not any webapp can run on any AS...
Yes JBoss Portal relies on JBoss AS as we are using services provided by JBoss
AS that are not available on other AS (or done in a different way because not
defined by a standard)
A portal framework consumes services from JBoss AS to deliver services to you.
okay so what I understand is that the databases for portal server, application
and the application server can be different from the default ones and they can
even exist on remote machines. However, the same is not true in case of teh
application server. THe portal server's application server
I believe that all you need to do is define a new datasource with JDNI name
PortalDS.
The HSQLDB one, is defined in portal-hsqldb-ds.xml (at least in my setup)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240222#4240222
Reply to the post :
Is this the only place where we need to change because the HSQLDB is found in
the name of the xml file as well. So it means that somewhere we may need to
specify the name of the xml as well
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240226#4240226
Reply
My understanding is, that the name of the xml is unimportant.
You just place the xml file in the deploy directory and it will be picked up at
deploy time.
Then the portal will use the JNDI name PortalDS to get to the datasource.
View the original post :
correct, as long as it ends with -ds.xml
Also make sure to not deploy 2 datasources with the same name
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240249#4240249
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240249
also can this custom portal database be on a different machine that is remote
from where the portal server has been installed?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240254#4240254
Reply to the post :
Sure, that only depends on the connection-url definition in the -ds.xml
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240279#4240279
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240279
Is the same applicable for the portal server's application server as well? Can
the application server(of the portal container) reside on a different machine
and the portal server on a different one. I mean if it cannot be then is it not
a tughtly coupled architecture?
View the original post :
You have to be more clear on what you mean by portal server.
In JBoss Portal case, it's portal bits running on top of JBoss Application
server. JBoss Portal bits are deployed on the same machine running JBoss
Application server. Currently, JBoss Portal only works with JBoss AS.
View the
You can use the same database for the Portal's data as well as for the data for
the portlets that you write (or that you obtain from third parties). However, I
usually recommend that you use separate databases - imagine the hassle if you
have to reset the Portal's database for some reason and
I hit Submit too soon. I should have also stated the following:
JBoss AS, by default, uses a datasource name DefaultDS, mainly for messaging
and timer data. While you can configure both AS and Portal to use the same
database, I recommend that you do not for the same reasons I gave for having
14 matches
Mail list logo
