Enabling the OSGi Console for an AppNode
The
enableconsole command dynamically enables the OSGi console on the given port for a running AppNode. Advanced users can telnet to the port and run native OSGi commands to get information about an AppNode's status. This is useful when collecting diagnostic data remotely. By default, the OSGi port is closed.
The
enableconsole command can only be run against a running AppNode. It should be issued from BWAdmin interactive mode, not from the command line.
If you are testing and running applications in TIBCO Business Studio for BusinessWorks, you can also access the OSGi commands from the Console view.
BWAdmin Command Line
- Procedure
- In a terminal, navigate to BW_HOME\bin and type bwadmin.
- Go to
MyDomain.
bwadmin[admin]> cd MyDomain
- Go to
MyAppSpace.
bwadmin[admin@MyDomain]> cd MyAppSpace
- Start the AppNode, if it is not already running:
bwamdin[admin@MyDomain/MyAppSpace]> start appnode MyAppNode
- Run the
enableconsolecommand, passing the host and OSGi port number. For example:bwamdin[admin@MyDomain/MyAppSpace]> enableconsole -n MyAppNode JSMITH-W520 9060 TIBCO-BW-ADMIN-CLI-300304: Console enabled for AppNode [MyAppNode] in Domain [MyDomain]
Note: You can also specify the OSGi port number using one of the following syntaxes:hostname:port numberlocalhost:port number
- Open a new terminal window and use the
telnetcommand to access the OSGi console:telnet JSMITH-W520 9060The OSGi console is opened in a terminal.
- Use OSGi commands to retrieve information about the engine, the AppNode, the running application. For a list of commands, enter:
help. See the topic called OSGi Runtime Statistics Commands for more information. - When you are done, use the
disconnectcommand to quit the telnet session gracefully, and leave the OSGi port open for reentry. Use the telnetstopcommand to close the connection after the debugging session is complete. Do not use the telnetexitcommand as this shuts down the AppNode.