[GUIDE] custom the starts interface on quickstart platform

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GUIDE] custom the starts interface on quickstart platform

sbuchan
If you want to choose your own specific inteface (192.168.1.116 for me, and port 9999 for the webconsole, for example) you have to edit 2 files:
1-$PETALS_HOME/conf/server.properties
Code:
# PETALS: PETALS Services Platform

# Copyright (C) 2005  EBM WebSourcing

#

# This library is free software; you can redistribute it and/or

# modify it under the terms of the GNU Lesser General Public

# License as published by the Free Software Foundation; either

# version 2.1 of the License, or any later version.

#

# This library is distributed in the hope that it will be useful,

# but WITHOUT ANY WARRANTY; without even the implied warranty of

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU

# Lesser General Public License for more details.

#

# You should have received a copy of the GNU Lesser General Public

# License along with this library; if not, write to the Free Software

# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307

# USA.

#

# Initial developer(s): EBM WebSourcing



# -----------------------------------------------------------------------

# Petals properties

# -----------------------------------------------------------------------



#This property specify the URL path to the PEtALS repository.

#PEtALS holds its JBI configuration in this repository and can recover this configuration from it.

#If not specified, the default repository is $PETALS_HOME/repository.

#petals.repository.path=file:///home/test/repository



#This property is used to activate the control of exchange acceptance by target component when

# the NMR routes messages (see isExchangeWithConsumerOkay and isExchangeWithProviderOkay methods

# in JBI Component interface)

# If not specified, the false value is selected by default.

#petals.exchange.validation=true



#This property set the maximum duration of the processing of a life-cycle operation on a JBI

# components and SAs (start, stop, ...). It prevents from hanging threads.

petals.task.timeout=30000



# This property is used to isolate the ClassLoaders created for Shared Libraries and Components

# from the PEtALS container one.

# It can be useful to avoid concurrent libraries loading issues.

# If not specified, the false value is selected by default

#petals.classloaders.isolated=true



#The webconsole port

user.webconsole.port=[b]9999[/b]



#The webconsole interface

user.webconsole.host=[b]192.168.1.116[/b]


2-$PETALS_HOME/conf/topology.xml
Code:

   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://petals.ow2.org/topology petalsTopology.xsd">
   
      Quick Start topology
      
         
            [b]192.168.1.116[/b]
            This is a Quick start PEtALS container
            petals
            petals
            
               7700
            
         
      
   


You can put an IP address or a valid hostname. You can use localhost or 127.0.0.1 Cool
Thanks the petals team Smile !

At this time, the default hostname values ("localhost")doesn't work : you've to put an 'user.webconsole.host'. It's mandatory. If you don't do this you've got:
Code:
fgardes@ebm-25:~$ $PETALS_HOME/bin/startup.sh
Setting PEtALS environment
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)


 -----------------------------------------------------------
|                                                           |
|             OW2 PEtALS Enterprise Service Bus             |
|                   http://petals.ow2.org                   |
|                                                           |
 -----------------------------------------------------------

PEtALS ESB is starting...
[petals.RMI]-INFO 2008-10-02 17:16:06,376 JMX RMI server started at : service:jmx:rmi:///jndi/rmi://192.168.1.116:7700/jmxRmiConnector
Problem while starting PEtALS, try to stop PEtALS cleanly...
Command processing error : start
org.ow2.petals.kernel.api.server.PetalsException: Problem while starting PEtALS
   at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:223)
   at org.ow2.petals.launcher.AbstractLauncher.start(AbstractLauncher.java:190)
   at org.ow2.petals.launcher.AbstractLauncher.launch(AbstractLauncher.java:147)
   at org.ow2.petals.distribution.quickstart.Main.main(Main.java:42)
Caused by: org.objectweb.fractal.api.control.IllegalLifeCycleException
   at org.ow2.petals.webconsole.WebConsoleImpl.startFc(WebConsoleImpl.java:0)
   at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcContentState(BasicControllerMixin.java:8128)
   at org.objectweb.fractal.julia.generated.Cbd2013d7_0.setFcStarted(BasicControllerMixin.java:8068)
   at org.objectweb.fractal.julia.generated.C18c4c884_0.setFcStarted(INTERFACE[LifeCycleCoordinator])
   at org.objectweb.fractal.julia.generated.C4eddf8e0_0.startFc$$0(BasicControllerMixin.java:4097)
   at org.objectweb.fractal.julia.generated.C4eddf8e0_0.startFc(BasicControllerMixin.java:5095)
   at org.objectweb.fractal.julia.generated.C18c4c884_0.startFc(INTERFACE[LifeCycleCoordinator])
   at org.ow2.petals.kernel.server.FractalHelper.startComponent(FractalHelper.java:343)
   at org.ow2.petals.kernel.server.PetalsServerImpl.startPetalsComposite(PetalsServerImpl.java:455)
   at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:197)
   ... 3 more
fgardes@ebm-25:~$

In fact, we must have into the properties files one or more "user" entries for the LifecycleManager...




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=205#205

-------------------- m2f --------------------

_______________________________________________
Users mailing list
[hidden email]
http://forum-list.petalslink.org/cgi-bin/mailman/listinfo/users