Recommended usage of JMX Extractor microservice is to run it on JLupin Platform Control Center (by default JPCC includes configured JMX Extractor microservice). If for any reason this is not acceptable for you microservice can be uploaded to any platform running node you want.


JLupin JMX Extractor microservice can be download from our download section.

Uploading microservice

To install microservice you must only upload it to running platform. To do so you can put jmx-extractor microservice zip into upload directory on platform and from platform/start directory run command microservice deploy

Configuring microservice

Configuration file can be found in microservice directory (platform/application/jmx-extractor). Its name is jmx-extractor-configuration.yml.

Default file is shown below:

  jmxPort:  9010
  provider: jpcc
    address:          localhost
    jlrmcPort:        9090
    queuePort:        9095
    transmissionPort: 9096
    informationPort:  9097
    username:         jmx_extractor
    password:         jmx_extractor
  # provider: list
  # configuration:
  #   - localhost

This configuration is for case shown below:

Figure 1. JPCC with JLupin JMX Extractor microservice.

Of course there is also option to run microservice outside of JPCC. You can still connect it with your JPCC instance using provider of type jpcc. You can read more about jpcc provider configuration here.

You can also configure JMX Extractor microservice with list of static IP addresses with provider of type list. You can read more about list provider configuration here.

Figure 2. JLupin JMX Extractor microservice outside of JPCC.