You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by "colin.chi" <ib...@hotmail.com> on 2009/08/19 04:12:35 UTC
About Web Console
Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
ServiceMix instance?
Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of Apache
ServiceMix 3.3.1 (.tar.gz)?
or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
ServiceMix Web Application 3.3.1 (.war)?
My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't manage
ServiceMix instance more convenient.
Is there any way to solve my problem?
--
View this message in context: http://www.nabble.com/About-Web-Console-tp25036675p25036675.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: About Web Console
Posted by "colin.chi" <ib...@hotmail.com>.
Hi JB,
Thanks to reply my question.
I can understand your means.
I need some help about tutorials of the web application, I need to know more
about the web application to use it.
Do you have the tutorials?
Regards,
Colin.chi
Jean-Baptiste Onofré wrote:
>
> Hi Colin,
>
> The Apache ServiceMix Web application is the administration console.
> It's a JMX client allowing you to see the deployed components, SUs, SAs,
> etc and start/stop/shutdown each part.
>
> You can download it here:
> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>
> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
> ...) or an application server (geronimo, weblogic, websphere, jboss;
> ...). By default, the web console connects to the default RMI port
> number used by ServiceMix (the 1099) and try to discover SMX instances.
> You can change it by editing the WEB-INF/servicemix.xml.
>
> Regards
> JB
>
> colin.chi wrote:
>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>> ServiceMix instance?
>>
>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of Apache
>> ServiceMix 3.3.1 (.tar.gz)?
>>
>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>> ServiceMix Web Application 3.3.1 (.war)?
>>
>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>> manage
>> ServiceMix instance more convenient.
>>
>> Is there any way to solve my problem?
>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
>
>
--
View this message in context: http://www.nabble.com/About-Web-Console-tp25036675p25047355.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: About Web Console
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Vivian,
The web application is a JMX client as the jconsole or the SMX ant tasks
are.
The advantage of the web application is a look and feel more ESB
business oriented (the presentation of the data). The jconsole is raw
information coming from the MBeans.
Regards
JB
Madesclair Vivian wrote:
> Hello,
>
> Where can we find this smx web application? What is the advantage against jconsole?
>
> Regards,
> Vivian
>
>
> -----Message d'origine-----
> De : Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
> Envoyé : mercredi 19 août 2009 08:38
> À : users@servicemix.apache.org
> Objet : Re: About Web Console
>
> Hi Colin,
>
> The Apache ServiceMix Web application is the administration console.
> It's a JMX client allowing you to see the deployed components, SUs, SAs, etc and start/stop/shutdown each part.
>
> You can download it here:
> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>
> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
> ...) or an application server (geronimo, weblogic, websphere, jboss; ...). By default, the web console connects to the default RMI port number used by ServiceMix (the 1099) and try to discover SMX instances.
> You can change it by editing the WEB-INF/servicemix.xml.
>
> Regards
> JB
>
> colin.chi wrote:
>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>> ServiceMix instance?
>>
>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of
>> Apache ServiceMix 3.3.1 (.tar.gz)?
>>
>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>> ServiceMix Web Application 3.3.1 (.war)?
>>
>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>> manage ServiceMix instance more convenient.
>>
>> Is there any way to solve my problem?
>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
jbonofre@apache.org
jb@nanthrax.net
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
RE: About Web Console
Posted by Madesclair Vivian <vm...@sopragroup.com>.
Hello,
Where can we find this smx web application? What is the advantage against jconsole?
Regards,
Vivian
-----Message d'origine-----
De : Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
Envoyé : mercredi 19 août 2009 08:38
À : users@servicemix.apache.org
Objet : Re: About Web Console
Hi Colin,
The Apache ServiceMix Web application is the administration console.
It's a JMX client allowing you to see the deployed components, SUs, SAs, etc and start/stop/shutdown each part.
You can download it here:
http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
...) or an application server (geronimo, weblogic, websphere, jboss; ...). By default, the web console connects to the default RMI port number used by ServiceMix (the 1099) and try to discover SMX instances.
You can change it by editing the WEB-INF/servicemix.xml.
Regards
JB
colin.chi wrote:
> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
> ServiceMix instance?
>
> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of
> Apache ServiceMix 3.3.1 (.tar.gz)?
>
> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
> ServiceMix Web Application 3.3.1 (.war)?
>
> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
> manage ServiceMix instance more convenient.
>
> Is there any way to solve my problem?
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086
Re: About Web Console
Posted by "colin.chi" <ib...@hotmail.com>.
Hi JB,
Here is the catalina.2009-08-31.log of tomcat which start in my
computer(IP:10.80.12.85).
==================begin catalina.2009-08-31.log==================
2009-8-31 9:06:36 org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in
production environments was not found on the java.library.path: C:\Program
Files\Java\jdk1.6.0_12\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\apache-maven-2.1.0\bin;C:\apache-servicemix-3.3.1\bin;C:\Program
Files\Java\jdk1.6.0_12\bin;D:\oracle\ora92\bin;C:\Program
Files\Oracle\jre\1.3.1\bin;C:\Program
Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;;E:\Program
Files\TortoiseSVN\bin;C:\Program Files\Common Files\Thunder
Network\KanKan\Codecs;C:\Program Files\QuickTime\QTSystem\;C:\Program
Files\StormII\Codec;C:\Program Files\StormII;D:\Program Files\IDM Computer
Solutions\UltraEdit\
2009-8-31 9:06:36 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
2009-8-31 9:06:36 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1047 ms
2009-8-31 9:06:36 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
2009-8-31 9:06:36 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
2009-8-31 9:06:36 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
2009-8-31 9:06:37 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive apache-servicemix-web-3.3.1.war
2009-8-31 9:06:39 org.springframework.web.context.ContextLoader
initWebApplicationContext
INFO: Root WebApplicationContext: initialization started
2009-8-31 9:06:39
org.springframework.context.support.AbstractApplicationContext
prepareRefresh
INFO: Refreshing
org.apache.xbean.spring.context.XmlWebApplicationContext@958bb8: display
name [Root WebApplicationContext]; startup date [Mon Aug 31 09:06:39 CST
2009]; root of context hierarchy
2009-8-31 9:06:39
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from ServletContext resource
[/WEB-INF/applicationContext.xml]
2009-8-31 9:06:41
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from ServletContext resource
[/WEB-INF/servicemix.xml]
2009-8-31 9:06:41
org.springframework.context.support.AbstractApplicationContext
obtainFreshBeanFactory
INFO: Bean factory for application context
[org.apache.xbean.spring.context.XmlWebApplicationContext@958bb8]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@1dc423f
2009-8-31 9:06:41
org.springframework.core.io.support.PropertiesLoaderSupport loadProperties
INFO: Loading properties file from class path resource
[servicemix-web-console.properties]
2009-8-31 9:06:41
org.springframework.beans.factory.support.DefaultListableBeanFactory
preInstantiateSingletons
INFO: Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@1dc423f:
defining beans
[multipartResolver,jmxProxy,jdbcAuditorMBean,adminCommandsServiceMBean,registryMBean,dotViewServiceMBean,proxyManager,registry,auditor,components,endpoints,serviceAssemblies,serviceUnits,sharedLibraries,component,endpoint,serviceUnit,serviceAssembly,sharedLibrary,placeholderConfig,server,jbi,org.apache.servicemix.jbi.audit.jdbc.JdbcAuditor#0,org.apache.servicemix.jbi.view.DotViewService#0];
root of factory hierarchy
2009-8-31 9:06:42 org.apache.servicemix.jbi.framework.EndpointRegistry
getEndpointProcessors
WARN: Disabled endpoint processor
'org.apache.servicemix.jbi.framework.support.WSDL2Processor':
java.lang.NoClassDefFoundError: org/apache/woden/WSDLReader
2009-8-31 9:06:42 org.apache.servicemix.jbi.container.JBIContainer init
INFO: ServiceMix 3.3.1 JBI Container (ServiceMix) is starting
2009-8-31 9:06:42 org.apache.servicemix.jbi.container.JBIContainer init
INFO: For help or more information please see: http://servicemix.apache.org/
2009-8-31 9:06:42 org.apache.servicemix.jbi.framework.ComponentMBeanImpl
init
INFO: Initializing component: #SubscriptionManager#
2009-8-31 9:06:42 org.apache.servicemix.jbi.framework.DeploymentService
buildState
INFO: Restoring service assemblies
2009-8-31 9:06:42 org.apache.servicemix.jbi.framework.ClientFactory start
WARN: Cound not start ClientFactory: javax.naming.NamingException: Context
is read only
2009-8-31 9:06:42 org.apache.servicemix.jbi.container.JBIContainer start
INFO: ServiceMix JBI Container (ServiceMix) started
2009-8-31 9:06:49 org.apache.servicemix.jdbc.JDBCAdapterFactory getAdapter
INFO: Database driver recognized: [apache_derby_embedded_jdbc_driver]
2009-8-31 9:06:50 org.springframework.web.context.ContextLoader
initWebApplicationContext
INFO: Root WebApplicationContext: initialization completed in 11687 ms
2009-8-31 9:06:50
org.springframework.context.support.AbstractApplicationContext
prepareRefresh
INFO: Refreshing org.apache.cxf.bus.spring.BusApplicationContext@1cb2795:
display name [org.apache.cxf.bus.spring.BusApplicationContext@1cb2795];
startup date [Mon Aug 31 09:06:50 CST 2009]; root of context hierarchy
2009-8-31 9:06:51 org.apache.cxf.bus.spring.BusApplicationContext
getConfigResources
INFO: No cxf.xml configuration file detected, relying on defaults.
2009-8-31 9:06:51
org.springframework.context.support.AbstractApplicationContext
obtainFreshBeanFactory
INFO: Bean factory for application context
[org.apache.cxf.bus.spring.BusApplicationContext@1cb2795]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@7787a5
2009-8-31 9:06:51
org.springframework.beans.factory.support.DefaultListableBeanFactory
preInstantiateSingletons
INFO: Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@7787a5:
defining beans
[cxf,org.apache.cxf.bus.spring.BusApplicationListener,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,org.apache.cxf.resource.ResourceManager,org.apache.cxf.configuration.Configurer,org.apache.cxf.binding.BindingFactoryManager,org.apache.cxf.transport.DestinationFactoryManager,org.apache.cxf.transport.ConduitInitiatorManager,org.apache.cxf.wsdl.WSDLManager,org.apache.cxf.phase.PhaseManager,org.apache.cxf.workqueue.WorkQueueManager,org.apache.cxf.buslifecycle.BusLifeCycleManager,org.apache.cxf.endpoint.ServerRegistry,org.apache.cxf.endpoint.ServerLifeCycleManager,org.apache.cxf.endpoint.ClientLifeCycleManager,org.apache.cxf.transports.http.QueryHandlerRegistry,org.apache.cxf.endpoint.EndpointResolverRegistry,org.apache.cxf.headers.HeaderManager,org.apache.cxf.catalog.OASISCatalogManager,org.apache.cxf.endpoint.ServiceContractResolverRegistry,org.apache.cxf.binding.jbi.JBIBindingFactory,org.apache.cxf.binding.soap.SoapBindingFactory,org.apache.cxf.binding.soap.SoapTransportFactory,org.apache.cxf.binding.soap.customEditorConfigurer,org.apache.cxf.binding.xml.XMLBindingFactory,org.apache.cxf.jaxws.context.WebServiceContextResourceResolver,org.apache.cxf.jaxws.context.WebServiceContextImpl,org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder,org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder,org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider,org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory,org.apache.cxf.transport.jbi.JBITransportFactory,org.apache.cxf.ws.addressing.policy.AddressingAssertionBuilder,org.apache.cxf.ws.addressing.policy.AddressingPolicyInterceptorProvider,org.apache.cxf.ws.addressing.policy.UsingAddressingAssertionBuilder];
root of factory hierarchy
2009-8-31 9:06:52 org.apache.cxf.transport.servlet.AbstractCXFServlet
replaceDestinationFactory
INFO: Replaced the http destination factory with servlet transport factory
2009-8-31 9:06:52 org.springframework.web.servlet.FrameworkServlet
initServletBean
INFO: FrameworkServlet 'dispatcher': initialization started
2009-8-31 9:06:52
org.springframework.context.support.AbstractApplicationContext
prepareRefresh
INFO: Refreshing
org.springframework.web.context.support.XmlWebApplicationContext@168afdd:
display name [WebApplicationContext for namespace 'dispatcher-servlet'];
startup date [Mon Aug 31 09:06:52 CST 2009]; parent:
org.apache.xbean.spring.context.XmlWebApplicationContext@958bb8
2009-8-31 9:06:52
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from ServletContext resource
[/WEB-INF/dispatcher-servlet.xml]
2009-8-31 9:06:52
org.springframework.context.support.AbstractApplicationContext
obtainFreshBeanFactory
INFO: Bean factory for application context
[org.springframework.web.context.support.XmlWebApplicationContext@168afdd]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@7e80a
2009-8-31 9:06:52
org.springframework.beans.factory.support.DefaultListableBeanFactory
preInstantiateSingletons
INFO: Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@7e80a:
defining beans
[handlerMapping,/installComponent.action,/startComponent.action,/stopComponent.action,/shutdownComponent.action,/uninstallComponent.action,/installSharedLibrary.action,/uninstallSharedLibrary.action,/deployServiceAssembly.action,/startServiceAssembly.action,/stopServiceAssembly.action,/shutdownServiceAssembly.action,/undeployServiceAssembly.action,/startAuditor.action,/stopAuditor.action,/dot-flow.svg,/dot-endpoints.svg,exceptionResolver,dotView];
parent:
org.springframework.beans.factory.support.DefaultListableBeanFactory@1dc423f
2009-8-31 9:06:53 org.springframework.web.servlet.FrameworkServlet
initServletBean
INFO: FrameworkServlet 'dispatcher': initialization completed in 422 ms
2009-8-31 9:06:54 org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
2009-8-31 9:06:54 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
2009-8-31 9:06:54 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/47 config=null
2009-8-31 9:06:54 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
2009-8-31 9:06:54 org.apache.catalina.startup.Catalina start
INFO: Server startup in 18141 ms
==================end catalina.2009-08-31.log==================
In the smx instance log, there is not any exception, but some new log is
added behind smx started log.
==================begin smx log==================
......
DEBUG - SedaFlow - Called Flow resume
DEBUG - JMSFlow - Called Flow resume
DEBUG - JCAFlow - Called Flow resume
INFO - JBIContainer - ServiceMix JBI Container
(ServiceMix) started
INFO - JDBCAdapterFactory - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
DEBUG - ManagementContext - Registering system service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=JdbcAuditor
DEBUG - JBIContainer - Removing listener: class
org.apache.servicemix.jbi.audit.jdbc.JdbcAuditor
DEBUG - ManagementContext - Registering system service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DotViewService
DEBUG - JBIContainer - Adding listener: class
org.apache.servicemix.jbi.view.DotViewEndpointListener
DEBUG - JBIContainer - Adding listener: class
org.apache.servicemix.jbi.view.DotViewFlowListener
DEBUG - ManagementContext - Registering system service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=LogService
DEBUG - LogService - Located logging configuration:
file:/home/chibin/apache-servicemix-3.3.1/conf/log4j.xml
INFO - LogTask - Logging system reconfigured using
file: file:/home/chibin/apache-servicemix-3.3.1/conf/log4j.xml
DEBUG - JAASAuthenticationService - Authenticating 'smx
DEBUG - JAASAuthenticationService - Authenticating smx successfully
==================end smx log==================
so, according to these logs, I find it difficult to judge web console and
the smx instance connected.
Please help me to analyze and solve it.
Thanks and regards,
Jean-Baptiste Onofré wrote:
>
> Hi Colin,
>
> do you have any exception trace ?
>
> Regards
> JB
>
> colin.chi wrote:
>> Hi JB,
>>
>> I start a smx instance(version 3.3.1), os is linux, IP is 10.80.12.100,
>> port
>> is default that 1099.
>> than I deploy war into tomcat which is start in my computer, IP is
>> 10.80.12.85, tomcat port is 8080.
>>
>> According to your steps, I edit config file
>> servicemix-web-console.properties,
>> and change the property
>> jmx-service-url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>> into
>> jmx-service-url=service:jmx:rmi:///jndi/rmi://10.80.12.100:1099/jmxrmi
>>
>> then I type the address http://localhost:8080/servicemix-web-console in
>> IE,
>> and click links in web console, and not sure if connected to the smx
>> instance.
>>
>> Is there any questions?
>> Please help me.
>>
>> Thanks and regards,
>> colin
>>
>> Jean-Baptiste Onofré wrote:
>>> Hi Colin,
>>>
>>> The Apache ServiceMix Web application is the administration console.
>>> It's a JMX client allowing you to see the deployed components, SUs, SAs,
>>> etc and start/stop/shutdown each part.
>>>
>>> You can download it here:
>>> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>>>
>>> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
>>> ...) or an application server (geronimo, weblogic, websphere, jboss;
>>> ...). By default, the web console connects to the default RMI port
>>> number used by ServiceMix (the 1099) and try to discover SMX instances.
>>> You can change it by editing the WEB-INF/servicemix.xml.
>>>
>>> Regards
>>> JB
>>>
>>> colin.chi wrote:
>>>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>>>> ServiceMix instance?
>>>>
>>>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of
>>>> Apache
>>>> ServiceMix 3.3.1 (.tar.gz)?
>>>>
>>>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>>>> ServiceMix Web Application 3.3.1 (.war)?
>>>>
>>>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>>>> manage
>>>> ServiceMix instance more convenient.
>>>>
>>>> Is there any way to solve my problem?
>>> --
>>> Jean-Baptiste Onofré (Nanthrax)
>>> BuildProcess/AutoDeploy Project Leader
>>> http://buildprocess.sourceforge.net
>>> jb@nanthrax.net
>>> PGP : 17D4F086
>>>
>>>
>>
>
>
--
View this message in context: http://www.nabble.com/About-Web-Console-tp25036675p25217289.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: About Web Console
Posted by "colin.chi" <ib...@hotmail.com>.
Hi JB,
Maybe I find the web console and smx instance is connected.
when I deploy a jms su and not start smx instance, it is always deploy
failed.
when I start smx instance, the sa which contain jms su, is deploy success.
I hope that when web console is connected with smx instance, it will be very
good to give some tips or logs.
Thanks and regards,
colin.chi
Jean-Baptiste Onofré wrote:
>
> Hi Colin,
>
> do you have any exception trace ?
>
> Regards
> JB
>
> colin.chi wrote:
>> Hi JB,
>>
>> I start a smx instance(version 3.3.1), os is linux, IP is 10.80.12.100,
>> port
>> is default that 1099.
>> than I deploy war into tomcat which is start in my computer, IP is
>> 10.80.12.85, tomcat port is 8080.
>>
>> According to your steps, I edit config file
>> servicemix-web-console.properties,
>> and change the property
>> jmx-service-url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>> into
>> jmx-service-url=service:jmx:rmi:///jndi/rmi://10.80.12.100:1099/jmxrmi
>>
>> then I type the address http://localhost:8080/servicemix-web-console in
>> IE,
>> and click links in web console, and not sure if connected to the smx
>> instance.
>>
>> Is there any questions?
>> Please help me.
>>
>> Thanks and regards,
>> colin
>>
>> Jean-Baptiste Onofré wrote:
>>> Hi Colin,
>>>
>>> The Apache ServiceMix Web application is the administration console.
>>> It's a JMX client allowing you to see the deployed components, SUs, SAs,
>>> etc and start/stop/shutdown each part.
>>>
>>> You can download it here:
>>> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>>>
>>> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
>>> ...) or an application server (geronimo, weblogic, websphere, jboss;
>>> ...). By default, the web console connects to the default RMI port
>>> number used by ServiceMix (the 1099) and try to discover SMX instances.
>>> You can change it by editing the WEB-INF/servicemix.xml.
>>>
>>> Regards
>>> JB
>>>
>>> colin.chi wrote:
>>>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>>>> ServiceMix instance?
>>>>
>>>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of
>>>> Apache
>>>> ServiceMix 3.3.1 (.tar.gz)?
>>>>
>>>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>>>> ServiceMix Web Application 3.3.1 (.war)?
>>>>
>>>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>>>> manage
>>>> ServiceMix instance more convenient.
>>>>
>>>> Is there any way to solve my problem?
>>> --
>>> Jean-Baptiste Onofré (Nanthrax)
>>> BuildProcess/AutoDeploy Project Leader
>>> http://buildprocess.sourceforge.net
>>> jb@nanthrax.net
>>> PGP : 17D4F086
>>>
>>>
>>
>
>
--
View this message in context: http://www.nabble.com/About-Web-Console-tp25036675p25218455.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: About Web Console
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Colin,
do you have any exception trace ?
Regards
JB
colin.chi wrote:
> Hi JB,
>
> I start a smx instance(version 3.3.1), os is linux, IP is 10.80.12.100, port
> is default that 1099.
> than I deploy war into tomcat which is start in my computer, IP is
> 10.80.12.85, tomcat port is 8080.
>
> According to your steps, I edit config file
> servicemix-web-console.properties,
> and change the property
> jmx-service-url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> into jmx-service-url=service:jmx:rmi:///jndi/rmi://10.80.12.100:1099/jmxrmi
>
> then I type the address http://localhost:8080/servicemix-web-console in IE,
> and click links in web console, and not sure if connected to the smx
> instance.
>
> Is there any questions?
> Please help me.
>
> Thanks and regards,
> colin
>
> Jean-Baptiste Onofré wrote:
>> Hi Colin,
>>
>> The Apache ServiceMix Web application is the administration console.
>> It's a JMX client allowing you to see the deployed components, SUs, SAs,
>> etc and start/stop/shutdown each part.
>>
>> You can download it here:
>> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>>
>> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
>> ...) or an application server (geronimo, weblogic, websphere, jboss;
>> ...). By default, the web console connects to the default RMI port
>> number used by ServiceMix (the 1099) and try to discover SMX instances.
>> You can change it by editing the WEB-INF/servicemix.xml.
>>
>> Regards
>> JB
>>
>> colin.chi wrote:
>>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>>> ServiceMix instance?
>>>
>>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of Apache
>>> ServiceMix 3.3.1 (.tar.gz)?
>>>
>>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>>> ServiceMix Web Application 3.3.1 (.war)?
>>>
>>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>>> manage
>>> ServiceMix instance more convenient.
>>>
>>> Is there any way to solve my problem?
>> --
>> Jean-Baptiste Onofré (Nanthrax)
>> BuildProcess/AutoDeploy Project Leader
>> http://buildprocess.sourceforge.net
>> jb@nanthrax.net
>> PGP : 17D4F086
>>
>>
>
Re: About Web Console
Posted by "colin.chi" <ib...@hotmail.com>.
Hi JB,
I start a smx instance(version 3.3.1), os is linux, IP is 10.80.12.100, port
is default that 1099.
than I deploy war into tomcat which is start in my computer, IP is
10.80.12.85, tomcat port is 8080.
According to your steps, I edit config file
servicemix-web-console.properties,
and change the property
jmx-service-url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
into jmx-service-url=service:jmx:rmi:///jndi/rmi://10.80.12.100:1099/jmxrmi
then I type the address http://localhost:8080/servicemix-web-console in IE,
and click links in web console, and not sure if connected to the smx
instance.
Is there any questions?
Please help me.
Thanks and regards,
colin
Jean-Baptiste Onofré wrote:
>
> Hi Colin,
>
> The Apache ServiceMix Web application is the administration console.
> It's a JMX client allowing you to see the deployed components, SUs, SAs,
> etc and start/stop/shutdown each part.
>
> You can download it here:
> http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
>
> You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
> ...) or an application server (geronimo, weblogic, websphere, jboss;
> ...). By default, the web console connects to the default RMI port
> number used by ServiceMix (the 1099) and try to discover SMX instances.
> You can change it by editing the WEB-INF/servicemix.xml.
>
> Regards
> JB
>
> colin.chi wrote:
>> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
>> ServiceMix instance?
>>
>> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of Apache
>> ServiceMix 3.3.1 (.tar.gz)?
>>
>> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
>> ServiceMix Web Application 3.3.1 (.war)?
>>
>> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't
>> manage
>> ServiceMix instance more convenient.
>>
>> Is there any way to solve my problem?
>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
>
>
--
View this message in context: http://www.nabble.com/About-Web-Console-tp25036675p25182717.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: About Web Console
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Colin,
The Apache ServiceMix Web application is the administration console.
It's a JMX client allowing you to see the deployed components, SUs, SAs,
etc and start/stop/shutdown each part.
You can download it here:
http://www.apache.org/dyn/closer.cgi?path=%2Fservicemix%2Fservicemix-3%2F3.3.1%2Fapache-servicemix-web-3.3.1.war
You need to deploy the war into a JSP/Servlet engine (Tomcat, jetty,
...) or an application server (geronimo, weblogic, websphere, jboss;
...). By default, the web console connects to the default RMI port
number used by ServiceMix (the 1099) and try to discover SMX instances.
You can change it by editing the WEB-INF/servicemix.xml.
Regards
JB
colin.chi wrote:
> Does Apache ServiceMix 3.3.1 (.tar.gz) have web console to manage the
> ServiceMix instance?
>
> Is Apache ServiceMix Web Application 3.3.1 (.war) a web console of Apache
> ServiceMix 3.3.1 (.tar.gz)?
>
> or Could Apache ServiceMix 3.3.1 (.tar.gz) work together with Apache
> ServiceMix Web Application 3.3.1 (.war)?
>
> My problem is when I use Apache ServiceMix 3.3.1 (.tar.gz), I don't manage
> ServiceMix instance more convenient.
>
> Is there any way to solve my problem?
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086