How to check satus of the application and component running in docker container from Postman

How to check satus of the application and component running in docker container from Postman

book

Article ID: KB0073970

calendar_today

Updated On:

Products Versions
TIBCO BusinessWorks Container Edition 2.5.3

Description

How to check the status of application and components deployed in container from Postman

Issue/Introduction

Below article describes how to get the application status and component status of application deployed in docker container using Rest Api from postman.

Resolution

Port forward the docker port 8090 to any port, I am using the sample as 18090.

(My run command:docker run -d -p 18050:8080 -p 18090:8090  bwce253emsappnew:latest)

--->To get the status of the application.Do a GET on

http://localhost:18090/bw/framework.json/osgi?command=la

Output:
==========================================================================
Applications:
--------------------------------------------------------
Name        : TIBCOSupport-CloseApp.application: 1.0
Bundle      : TIBCOSupport-CloseApp.application_1.0.0.20200805194228 [
  445
]
Bundle Id   : 445
State       : Running
                  TIBCO-BW-FRWK-300012: Started BW Application Module [TIBCOSupport-CloseApp: 1.0.0.20200805194226
]
ConfigState : OutOfSync
Modules     :
  (BW Application Module) TIBCOSupport-CloseApp 1.0.0.20200805194226:
    Bundle Id              : 446
    Bundle State           : ACTIVE
    State                  : Resolved
    Components             :
      ComponentSampleProcess (Resolved) (MultipleNodes,Started) -> ProcessState(com.sanofi.tibco.support.SampleProcess, Resolved)
    Processes              : See also 'lp' command
      com.sanofi.tibco.support.SampleProcess (Private, Resolved) -> ResourceDep(tibcosupport-closeapp.JMSConnectionResource,jmsConnection,
{http: //xsd.tns.tibco.com/bw/models/sharedresource/jms}JMSConnectionFactory,Resolved)
    Resource Configurations: See also 'lcfg' command
      {http: //xsd.tns.tibco.com/bw/models/sharedresource/jms}JNDIConnection.97eed8d3-47f5-48c1-bb4b-c4654acf3cc0 {http: //xsd.tns.tibco.com/bw/sharedresource/trinity/models/identity/subject}SubjectConfiguration.032e2fdf-b9ce-4ede-822f-1f5a164a3bc2 {http: //xsd.tns.tibco.com/bw/models/sharedresource/jms}JMSConnectionFactory.3db1c4a0-276a-4a55-bf18-7535d2543623
    Unresolved Dependencies: See also 'le' and 'lr' commands
      none
Dependencies:
  ConstituentBundle(TIBCOSupport-CloseApp_1.0.0.20200805194226)
  EngineDep(Main=BWEngine[BW=6.3.1400.007, BX=2.2.500.009, PVM=4.2.200.005, Alias=standalone_standalone_standalone
        ])
Unresolved Dependencies: See also 'lr' and 'dsr' commands for details
  none
Application Properties :
  Use 'lap' command
Events                 :
  com/tibco/bw/runtime/AppStateChangedEvent:  Resolved {}
  com/tibco/bw/runtime/AppStateChangedEvent:  Starting {Starting Application
        }
  com/tibco/bw/runtime/AppStateChangedEvent:  Running {TIBCO-BW-FRWK-300012: Started BW Application Module [TIBCOSupport-CloseApp: 1.0.0.20200805194226
          ]
        }
  com/tibco/bw/sharedresource/SharedResourceStartedEvent:   tibcosupport-closeapp.EMSDefaultJNDIConfiguration
  com/tibco/bw/sharedresource/SharedResourceStartedEvent:   tibcosupport-closeapp.IdentityProvider
  com/tibco/bw/sharedresource/SharedResourceStartedEvent:   tibcosupport-closeapp.JMSConnectionResource
  com/tibco/bw/sharedresource/SharedResourceCreatedEvent:   tibcosupport-closeapp.EMSDefaultJNDIConfiguration
  com/tibco/bw/sharedresource/SharedResourceCreatedEvent:   tibcosupport-closeapp.IdentityProvider
  com/tibco/bw/sharedresource/SharedResourceCreatedEvent:   tibcosupport-closeapp.JMSConnectionResource
Problems               : 
==========================================================================


---> To get the list of components of the application:

http://localhost:18090/bw/framework.json/osgi?command=getcomps%20TIBCOSupport-CloseApp.application%20-v%201.0

Here application name is :TIBCOSupport-CloseApp.application and version is 1.0
you can change the version at the end of URL to your version 

Output
ComponentSampleProcess


--->To get the status of component:

http://localhost:18090/bw/framework.json/osgi?command=getcompdetail%20TIBCOSupport-CloseApp.application%20ComponentSampleProcess

Output:
name: ComponentSampleProcess
state: Resolved
starter state: Started
activation status: MultipleNodes

--->To stop the component

http://localhost:18090/bw/framework.json/osgi?command=stopcomp%20TIBCOSupport-CloseApp.application%20ComponentSampleProcess

--->To start the component:

http://localhost:18090/bw/framework.json/osgi?command=startcomp%20TIBCOSupport-CloseApp.application%20ComponentSampleProcess

Additional Information

https://docs.tibco.com/pub/bwce/2.5.3/doc/html/GUID-4AC8019F-701F-48BD-BC44-2A293E4C3796.html