Verifying the TIBCO Cloud API Management Connectors and Adapters

To verify if the TIBCO Cloud API Management Connectors and Adapters were loaded and deployed successfully perform the following steps:

Procedure

  1. Check the status of all the containers as follows: 
    njaltare@appss-MacBook-Pro-5 manifest-onprem-swarm % docker ps -a
CONTAINER ID   IMAGE                   COMMAND                  CREATED        STATUS                 PORTS                                              NAMES
0d847c71a32c   tml-tm:v5.3.1.GA.3      "/usr/local/bin/tm-e…"   4 hours ago    Up 4 hours (healthy)   22/tcp, 80/tcp, 443/tcp, 8000/tcp, 8083-8084/tcp   tmstack_tm.1.nexbrmw2np59yky95mm8k4tm6
dbfd3ae614fc   tml-cache:v5.3.1.GA.3   "/usr/local/bin/cach…"   4 hours ago    Up 4 hours             11211-11216/tcp                                    cachestack_cache.1.uprbqvq472ckrrl4l6yy49if4
0bf0e830f261   tml-sql:v5.3.1.GA.3     "/usr/local/bin/sql-…"   4 hours ago    Up 4 hours             3306/tcp                                           sqlstack_sql.1.sxhask7woay9d9fxtufv911wi
352d9e5cb78d   tml-log:v5.3.1.GA.3     "/usr/local/bin/log-…"   4 hours ago    Up 4 hours             24023/tcp, 24220/tcp, 24224/tcp                    logstack_log.1.f75ej5wha5t7htjt2y27wg8ie
9b5de6dd0847   tml-cm:v5.3.1.GA.3      "/usr/local/bin/cm-e…"   4 hours ago    Up 4 hours (healthy)                                                      cmstack_tmlcm.1.ymgtad7ty8to6606s29cjxpvj
87496d0e2a4c   tml-nosql:v5.3.1.GA.3   "/usr/local/bin/nosq…"   4 hours ago    Up 4 hours (healthy)   7000-7001/tcp, 7199/tcp, 9042/tcp, 9160/tcp        nosqlstack_nosql_seed.1.ebce8f5eptjlib651wyg15qhr
    All the containers namely, tml-tm, tml-cache,tml-sql, tml-log, tml-cm and tml-nosql must be up and running.
  2. Login to the Traffic Manager container tml-tm as follows: 
    njaltare@appss-MacBook-Pro-5 manifest-onprem-swarm % docker exec -it 0d847c71a32c bash
[root@0d847c71a32c builder]#
  3. On successfully logging into the Traffic Manager container, you can access the OSGi console of the Traffic Manager using the following command: 
    [root@0d847c71a32c builder]# telnet localhost 8081
  4. Verify if connection to the OSGi console is successful as follows: 
    [root@0d847c71a32c builder]# telnet localhost 8081
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
OSGi>
  5. List the OSGi bundles by executing the ss command.
    An example of OSGi ss command is shown below. 
    OSGi> ss
"Framework is launched."
 
id  State       Bundle
0   ACTIVE      org.eclipse.OSGi_3.15.0.v20190830-1434
1   ACTIVE      org.eclipse.equinox.simpleconfigurator_1.3.300.v20190716-0825
2   RESOLVED    ch.qos.logback.access_1.1.11
3   RESOLVED    ch.qos.logback.classic_1.1.11
                Fragments=42
4   RESOLVED    ch.qos.logback.core_1.1.11
5   RESOLVED    ch.qos.logback.slf4j_1.1.2.v20160301-0943
                Master=147
6   RESOLVED    com.amazonaws_1.1.9
7   RESOLVED    com.codahale.metrics.core_3.1.2
8   RESOLVED    com.datastax.driver.core_3.7.2
9   RESOLVED    com.google.guava_27.1.0.v20190517-1946
10  ACTIVE      com.mashery.cassandra.client_1.0.0.v20200122-1721
11  STARTING    com.mashery.geoip_1.0.0.v20200122-1721
12  RESOLVED    com.mashery.http_1.2.0.v20191113-0329
13  ACTIVE      com.mashery.internal.http_1.0.0.v20200130-0430
14  RESOLVED    com.mashery.internal.util_1.0.1.v20200329-0041
15  STARTING    com.mashery.mail.aws_1.0.0.v20200122-1721
16  STARTING    com.mashery.mail.log_1.0.0.v20200313-2203
17  RESOLVED    com.mashery.oauth2_1.2.0.v20200311-2141
18  ACTIVE      com.mashery.perf_1.0.0.r51209
19  ACTIVE      com.mashery.perf.metric_1.0.0.v20180828-0655
20  STARTING    com.mashery.perf.statsd_1.0.0.r51209
21  RESOLVED    com.mashery.proxy.config_1.0.0.v20200323-2237
22  ACTIVE      com.mashery.proxy.configurator_1.0.0.v20200130-0430
23  ACTIVE      com.mashery.proxy.connector.oauth2jwtconnector_1.1.0.v20200330-1631
24  STARTING    com.mashery.proxy.connectors.util_1.1.0.v20200330-1631
25  ACTIVE      com.mashery.proxy.core_1.0.0.v20200222-0620
26  ACTIVE      com.mashery.proxy.core.crypto_1.0.0.v20200218-2209
27  ACTIVE      com.mashery.proxy.core.oauth1_1.0.0.v20200122-1721
28  ACTIVE      com.mashery.proxy.core.oauth2_1.2.0.v20200312-0442
29  RESOLVED    com.mashery.proxy.crypto_1.0.0.v20200130-0430
30  STARTING    com.mashery.proxy.customer.common.xmltojson_1.2.0.v20200402-0713
31  ACTIVE      com.mashery.proxy.customer.generic_1.2.0.v20200529-0649
32  ACTIVE      com.mashery.proxy.customers.util_1.2.0.v20200526-1123
33  STARTING    com.mashery.proxy.dataservice_1.1.0.v20200313-2203
34  ACTIVE      com.mashery.proxy.datasource_1.1.0.v20200406-0749
35  ACTIVE      com.mashery.proxy.datasource.compatibility_1.0.0.v20200130-0430
36  ACTIVE      com.mashery.proxy.dateservice_1.0.0.v20180828-0655
37  RESOLVED    com.mashery.proxy.email_2.0.0.v20200319-0236
38  ACTIVE      com.mashery.proxy.email.provider_1.0.0.v20200122-1721
39  ACTIVE      com.mashery.proxy.env_1.0.0.v20200406-0749
40  RESOLVED    com.mashery.proxy.launcher_1.1.0.v20200309-2140
41  ACTIVE      com.mashery.proxy.logback_1.0.0.v20200122-1721
42  RESOLVED    com.mashery.proxy.logback.config_1.0.0.v20200122-1721
                Master=3
43  RESOLVED    com.mashery.proxy.logback.syslog_1.0.0.v20200122-1721
44  ACTIVE      com.mashery.proxy.management_1.0.0.v20200320-2008
45  ACTIVE      com.mashery.proxy.memcached_1.0.1.v20200317-2011
46  ACTIVE      com.mashery.proxy.memcacheloader_1.1.0.v20200305-1624
47  RESOLVED    com.mashery.proxy.oauth2_1.1.0.v20180731-2352
48  ACTIVE      com.mashery.proxy.oauth2.onprem_1.0.0.v20200327-1828
49  ACTIVE      com.mashery.proxy.onprem.crypto_1.0.0.v20200130-0430
50  ACTIVE      com.mashery.proxy.onprem.jmx_1.0.0.v20200218-2209
51  RESOLVED    com.mashery.proxy.onprem.mom.msg_1.0.0.v20200320-0726
52  ACTIVE      com.mashery.proxy.onprem.tokenpurge_1.0.0.v20200122-1721
53  ACTIVE      com.mashery.proxy.onpremloader_1.1.0.v20200218-2209
54  ACTIVE      com.mashery.proxy.OSGi.console.cmd_1.0.0.v20200218-2209
55  RESOLVED    com.mashery.proxy.OSGi.hooks_1.1.0.v20200225-0641
56  ACTIVE      com.mashery.proxy.responder_1.2.0.v20200327-1828
57  ACTIVE      com.mashery.proxy.server_1.1.0.v20200327-1828
58  ACTIVE      com.mashery.proxy.servlet_1.1.0.v20200410-2009
59  ACTIVE      com.mashery.proxy.signal_1.0.1.v20200222-0620
60  RESOLVED    com.mashery.proxy.slf4j_1.0.0.v20140814-1844
                Master=147
61  STARTING    com.mashery.proxy.slf4j.helper_1.0.0.v20200220-2055
62  ACTIVE      com.mashery.proxy.verbose.logger_1.0.0.v20181112-1720
63  ACTIVE      com.mashery.proxy.xml.parsers_1.0.0.v20200122-1721
64  ACTIVE      com.mashery.service_1.3.0.v20200319-1949
65  ACTIVE      com.mashery.service.oauth2_1.2.0.v20200221-2225
66  ACTIVE      com.mashery.service.onprem_1.0.0.v20200218-2209
67  ACTIVE      com.mashery.service.onprem.oauth_1.0.0.v20200218-2209
68  ACTIVE      com.mashery.service.responder_1.1.0.v20200319-1949
69  RESOLVED    com.mashery.signal_1.0.0.v20111004-1955
70  RESOLVED    com.mashery.trafficmanager.sdk_1.2.0.v20200313-2203
71  RESOLVED    com.mashery.util_1.1.0.v20200319-1810
72  RESOLVED    com.springsource.org.objenesis_1.0.0
73  RESOLVED    io.dropwizard.metrics.core_3.2.6
74  RESOLVED    io.netty.buffer_4.1.46.Final
75  RESOLVED    io.netty.codec_4.1.46.Final
76  RESOLVED    io.netty.common_4.1.46.Final
77  RESOLVED    io.netty.handler_4.1.46.Final
78  RESOLVED    io.netty.resolver_4.1.46.Final
79  RESOLVED    io.netty.transport_4.1.46.Final
80  RESOLVED    jackson-core-asl_1.6.3
81  RESOLVED    jackson-mapper-asl_1.6.3
82  RESOLVED    javax.mail_1.4.4
83  RESOLVED    javax.servlet_3.1.0.v201410161800
84  RESOLVED    net.bytebuddy.byte-buddy_1.9.0.v20181107-1410
85  RESOLVED    net.bytebuddy.byte-buddy-agent_1.9.0.v20181106-1534
86  RESOLVED    net.jpountz.lz4_1.3.0
87  RESOLVED    net.spy.memcached_2.12.3
88  RESOLVED    org.apache.commons.cli_1.4.0
89  RESOLVED    org.apache.commons.codec_1.10.0.v20180409-1845
90  RESOLVED    org.apache.commons.collections_3.2.2
91  RESOLVED    org.apache.commons.dbcp_1.4.0
92  RESOLVED    org.apache.commons.httpclient_3.1.0
93  RESOLVED    org.apache.commons.io_2.6.0.v20190123-2029
94  RESOLVED    org.apache.commons.lang_2.6.0.v201404270220
95  RESOLVED    org.apache.commons.lang3_3.9.0
96  RESOLVED    org.apache.commons.logging_1.2.0.v20180409-1502
97  RESOLVED    org.apache.commons.pool_1.6.0
98  ACTIVE      org.apache.felix.gogo.command_1.0.2.v20170914-1324
99  ACTIVE      org.apache.felix.gogo.runtime_1.1.0.v20180713-1646
100 ACTIVE      org.apache.felix.gogo.shell_1.1.0.v20180713-1646
101 ACTIVE      org.apache.felix.scr_2.1.14.v20190123-1619
102 RESOLVED    org.apache.httpcomponents.httpclient_4.0.3
103 RESOLVED    org.apache.httpcomponents.httpcore_4.1.0
104 RESOLVED    org.apache.httpcomponents.httpmime_4.0.3
105 RESOLVED    org.apache.james.mime4j_0.6.0
106 ACTIVE      org.eclipse.core.contenttype_3.7.400.v20190624-1144
107 ACTIVE      org.eclipse.core.jobs_3.10.500.v20190620-1426
108 ACTIVE      org.eclipse.core.runtime_3.16.0.v20190823-1314
109 ACTIVE      org.eclipse.equinox.app_1.4.300.v20190815-1535
110 ACTIVE      org.eclipse.equinox.cm_1.4.100.v20190714-1849
111 ACTIVE      org.eclipse.equinox.common_3.10.500.v20190815-1535
112 ACTIVE      org.eclipse.equinox.console_1.4.0.v20190819-1430
113 ACTIVE      org.eclipse.equinox.ds_1.6.0.v20190122-0806
114 ACTIVE      org.eclipse.equinox.event_1.5.200.v20190814-0953
115 ACTIVE      org.eclipse.equinox.http.jetty_3.7.200.v20190714-1849
116 RESOLVED    org.eclipse.equinox.http.registry_1.1.700.v20190214-1948
117 ACTIVE      org.eclipse.equinox.http.servlet_1.6.200.v20190823-1423
118 INSTALLED   org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1100.v20190907-0426
119 ACTIVE      org.eclipse.equinox.preferences_3.7.500.v20190815-1535
120 ACTIVE      org.eclipse.equinox.registry_3.8.500.v20190714-1850
121 RESOLVED    org.eclipse.equinox.supplement_1.9.0.v20190830-1434
122 RESOLVED    org.eclipse.equinox.useradmin_1.1.700.v20181116-1551
123 STARTING    org.eclipse.equinox.util_1.1.300.v20190714-1852
124 RESOLVED    org.eclipse.equinox.wireadmin_1.0.800.v20180827-1235
125 RESOLVED    org.eclipse.jetty.alpn.client_9.4.20.v20190813
126 RESOLVED    org.eclipse.jetty.client_9.4.20.v20190813
127 RESOLVED    org.eclipse.jetty.continuation_9.4.20.v20190813
128 RESOLVED    org.eclipse.jetty.http_9.4.20.v20190813
129 RESOLVED    org.eclipse.jetty.http2.client_9.4.20.v20190813
130 RESOLVED    org.eclipse.jetty.http2.client.http_9.4.20.v20190813
131 RESOLVED    org.eclipse.jetty.http2.common_9.4.20.v20190813
132 RESOLVED    org.eclipse.jetty.http2.hpack_9.4.20.v20190813
133 RESOLVED    org.eclipse.jetty.http2.server_9.4.20.v20190813
134 RESOLVED    org.eclipse.jetty.io_9.4.20.v20190813
135 RESOLVED    org.eclipse.jetty.OSGi-servlet-api_3.1.0.M3
136 RESOLVED    org.eclipse.jetty.OSGi.httpservice_9.4.20.v20190813
137 RESOLVED    org.eclipse.jetty.security_9.4.20.v20190813
138 RESOLVED    org.eclipse.jetty.server_9.4.20.v20190813
139 RESOLVED    org.eclipse.jetty.servlet_9.4.20.v20190813
140 RESOLVED    org.eclipse.jetty.util_9.4.20.v20190813
141 RESOLVED    org.eclipse.OSGi.services_3.8.0.v20190206-2147
142 RESOLVED    org.eclipse.OSGi.util_3.5.300.v20190708-1141
143 RESOLVED    org.mariadb.jdbc_2.5.4
144 RESOLVED    org.mockito_2.23.0.v20190527-1420
145 RESOLVED    org.objenesis_2.6.0.v20180420-1519
146 RESOLVED    org.OSGi.service.jdbc_1.0.0.201505202023
147 RESOLVED    org.slf4j.api_1.7.10.v20170428-1633
                Fragments=60, 5
148 RESOLVED    org.slf4j.jcl_1.7.2.v20130115-1340
149 RESOLVED    org.slf4j.log4j_1.7.2.v20130115-1340
150 RESOLVED    OSGi.core_5.0.0.201203141902
151 RESOLVED    OSGi.enterprise_4.2.0.v201108120515
152 RESOLVED    slf4j.api_1.7.28
  6. The TIBCO Cloud API Management Connectors will be listed as a single bundle.
    For example, the bundle for a custom adapter built with TIBCO Cloud API Management Connectors and standalone OAuth2JWT Connector, is as follows: 
    id  State       Bundle
23  ACTIVE      com.mashery.proxy.connector.oauth2jwtconnector_1.1.0.v20200330-1631
31  ACTIVE      com.mashery.proxy.customer.generic_1.2.0.v20200529-0649
32  ACTIVE      com.mashery.proxy.customers.util_1.2.0.v20200526-1123
    Note:
    • TIBCO Cloud API Management Connectors bundle can have different version values based on your deployment. The value 1.2.0.v20200529-0649 can be different accordingly.
    • The example shown above is of an OAuth2JWT Connector, com.mashery.proxy.connector.oauth2jwtconnector_1.1.0.v20200330-1631 deployed as standalone Connector bundle.
  7. The TIBCO Cloud API Management built Adapters, if any, will be listed as a single bundle.
    For example, a bundle for a Mashery built adapter is as follows: 
    id  State       Bundle
31  ACTIVE      com.mashery.proxy.customer.acme_1.2.0.v20200529-0649
    Note: TIBCO Cloud API Management Adapter bundle can have different version values based on your deployment. The value 1.2.0.v20200529-0649 can be different accordingly.
  8. Execute the exit command to exit from the OSI console.
    Type exit and hit the enter button twice.
    Sample output is as follows: 
    Login to TML-TM container bash.
njaltare@appss-MacBook-Pro-5 manifest-onprem-swarm % docker exec -it c038db019f96 bash
 
 
[root@c038db019f96 builder]# telnet localhost 8081Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
 
 
OSGi> quit
gogo: CommandNotFoundException: Command not found: quit
 
 
OSGi> exit
Really want to stop Equinox? (y/n; default=y) 
Connection closed by foreign host.
 
 
[root@c038db019f96 builder]#
    Note:
    • quit is not supported command as an exit command from OSGi console.
    • To log into the OSGi console again, follow the instructions in sequence above.
      • Make sure to exit completely from the TML-TM container.
      • Re-login to the container bash.
      • Login to OSGi again.