Developer

Verifying Bundle Configuration Using Telnet

You can use Telnet to verify that state bundle configuration changes are in effect.

Procedure

  1. On the command line, run:
    telnet localhost 5365
  2. At the Telnet prompt, run:
    aims:cmlist
    You see:
    Configuration list:   
    org.apache.felix.webconsole.internal.servlet.OsgiManager     
       file:bundle/application/aims-felix-webconsole-1.0.2.jar   
    service.event.quartz                                         
       file:bundle/application/event-scheduler-quartz-1.0.3.jar   
    org.ops4j.pax.logging                                       
       file:bin/pax-logging-service-1.6.9.jar   
    service.webui.security                                       
       file:bundle/application/web-core-0.1.9.jar   
    service.sampleState                                         
       file:bundle/application/customState-1.0-SNAPSHOT.jar   
    service.brand_webapp                                        
       file:bundle/application/mobiliser-brand-webadmin-ui-1.3.1.war   
    service.mobiliserCustomer.states.plugin  null   
    service.mobiliserCustomer.client.plugin  null   
    service.dsprovider                                          
       file:bundle/application/dbcp-osgi-service-1.3.1.jar   
    service.coreprocessing                                      
       file:bundle/application/mobiliser-brand-processing-1.3.1.jar   
    org.ops4j.pax.web                                           
       file:bundle/application/pax-web-jetty-bundle-1.1.4.jar   
    service.event.core                                          
       file:bundle/application/event-core-1.0.3.jar
        

    In the output above, the service process ID (PID) for the customState-1.0-SNAPSHOT.jar is service.sampleState.

  3. To see the customState-1.0-SNAPSHOT.jar configuration, run:
    aims:cmget service.sampleState
    You see:
    Configuration for service (pid) "service.sampleState"   
    (bundle location = file:bundle/application/customState-1.0-SNAPSHOT.jar)  
         
    key              value   
    ------           ------   
    service.pid      service.sampleState   
    sample.country   US   
    arf.filename     service.sampleState.properties

    If you set the <ARF-Bundle-Template> property in the Maven POM file, you can view the sample properties file that is packaged in the state bundle. Sample property files generally contain documentation for each property.

  4. To find all state bundles that have sample property templates, run:
    aims:template

    You see:

    Bundles with configuration templates:   
    ID: 39  Bundle:com.sybase365.mobiliser.thirdparty.smppapi   
    ID: 49  Bundle:com.sybase365.mobiliser.brand.processing.mobiliser-brand-processing   
    ID: 51  Bundle:com.sybase365.mobiliser.brand.database.mobiliser-brand-jpa   
    ID: 52  Bundle:com.sybase365.mobiliser.brand.database.mobiliser-brand-jpa-eclipselink   
    ID: 56  Bundle:com.sybase365.mobiliser.framework.event-store-db-provider   
    ID: 57  Bundle:com.sybase365.mobiliser.framework.event-store-jpa   
    ID: 58  Bundle:com.sybase365.mobiliser.framework.event-store-eclipselink   
    ID: 60  Bundle:com.sybase365.mobiliser.brand.osgi.dbcp-osgi-service   
    ID: 117 Bundle:com.sybase365.mobiliser.brand.service.mobiliser-brand-rest-core   
    ID: 118 Bundle:com.sybase365.aims.webui.web-core   
    ID: 120 Bundle:com.sybase365.mobiliser.brand.webadmin.mobiliser-brand-webadmin-ui   
    ID: 121 Bundle:com.sap.example.customState 
  5. To see more information about the com.sap.example.customState bundle, run:
    aims:template 121