[cry4dawn]

that worked!!!

how do i get it into the runlevel (/ect/init.d/jboss start) ?

[peterj]

Regarding binding to 0.0.0.0, see the jbossas readme file, or the millions of posts asking about this.

To set the app server to start as a service, see http://wiki.jboss.org/wiki/Wiki.jsp?page=StartJBossOnBootWithLinux

[cry4dawn]

i know how to use the run level im asking how do i add the -b 0.0.0.0 to it. the link you posted has no information on that

[peterj]

I am sorry, I interpreted the word "it" to mean the application server, not the text "-b 0.0.0.0".

Unfortunately, I do not know the contents of your startup script (/etc/init.d/jboss), so I will tell you how to modify the bin/jboss_init_redhat.sh script to include the -b option. You should be able to apply this to your script.

In the script, the variable JBOSSSH contains the text used to run the app server:

#define the script to use to start jboss
JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF $JBOSS_BIND_ADDR"}

Notice that it in turn refers to a JBOSS_BIND_ADDR variable:

#if JBOSS_HOST specified, use -b to bind jboss services to that address
JBOSS_BIND_ADDR=${JBOSS_HOST:+"-b $JBOSS_HOST"}

You could replace this as follows:

#if JBOSS_HOST specified, use -b to bind jboss services to that address
JBOSS_BIND_ADDR="-b 0.0.0.0"

or your could earlier define JBOSS_HOST:

JBOSS_HOST=0.0.0.0

[cry4dawn]

no worries about the misundersting it happens.

thanx for the code snipit. its all working now.

im just wondering why this problem has never showed up before we started using portal? we have been using jboss on solaris since 3.2.5. oh well.

thanx everyone for your help.

[theute]

The changed happened in 4.2

For security reasons (because people judge your products based on this...) JBoss AS no longer listen on all interfaces, by default it only listens on the local interface.

[peterj]

When you used Portal was probably the first time you used JBoss AS 4.2.x. That version changed how binding was done, previous versions bound to 0.0.0.0 by default, but 4.2.x binds to 127.0.0.1 by default. All part of making the app server more secure, yet still usable by a developer out of the box.

[pushpita_b]

hi

i want to delete the default portal and only need to deploy my own portal.Can any body help me?

[peterj]

It is much easier to "rename" your portal to "default" than it is to remove the current "default" portal and use yours instead. See the first page of this post for help.

[vinguye2]

I don't believe you can remove the default portal. As mentioned in the docs, there must always be one default portal named "default". Also, each portal instance must have a default page named "default". So in the descriptor files, these names can't be changed. The easiest approach is to modify the descriptor for the default portal, and add/remove content to fit your needs.

[theute]

in 2.6.2 you can select another default portal than 'default'. See the admin portlet.
Same for pages

[lvcster]

Hi PeterJ and Everyone,

I followed all what u said above, removing the wars/sara i dont need. I ddi just that, and now the protal is clean, except for the 3 tabs(Home, News, and Weather), and the login link on the top right hand side corner. Tell me how do i get rid of this?

And i want to change the JBossPortal Logo, background and the rest how do i go about doing that?

Please help.
Thanks.

[lvcster]

I did a bit of googling, i managed to get rid of those tabs, except for the Login and Home. I think the problem might be indefault-object.xml.

The way i understand it, the indefault-object.xml defines the <parent-ref>, as default.

How do i make my own <parent-ref> ? , and specify in the descriptor that it should reference my owm parent ref, not the default one?

Is it posible for folder server\default\deploy\jboss-portal.sar\conf\data to have multiple *-object.xml?

Somebody's help will highly be apreciated.

Thanks.
lvcster.

[peterj]

You should not remove the Home tab. Instead, modify the jboss-portal.sar/conf/data/default-object.xml file to remove the portlet objects from the 'default' portal page, and then in your *-object.xml file add you own poortlets to the default page.

To get rid of the login link, modify the jboss-portal.sar/portal.core.war/WEB-INF/jsp/header/header.jsp file and remove the login link.

Finally, you should really have started a new topic, not posted to an older one.