npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-jolokia

v0.1.0

Published

Jolokia JS Lib Port for Node.js

Downloads

6

Readme

#Jolokia Node Client This project is a port version of Jolokia official Javascript client for Node.JS

Current version of ported Jolokia JS client is 1.2.2. #Installation Install using npm

npm install --save node-jolokia

#Usage ##Simple Demo

var jolokia=require("node-jolokia");
jolokia("http://localhost:8181/jolokia",function(err,client){
    if (err){
      //err handle
    }else{
      //perform a request
      client.request({type:"version"},{
        success:function(res, idx){
          //responsed as JSON
        },
        ajaxError:function(statusCode,error,errorText){
          //web request error handling
        },
        error:function(errorRes, idx){
          // response error handling
        }
      });

      //get attribute:
      client.getAttribute("org.apache.zookeeper:name0=StandaloneServer_port-1,name1=InMemoryDataTree", "WatchCount",{
        success:function(){},
        error:function(){}
      });

      //set attribute:
      client.setAttribute(mBean,attribute, value, path, opt);

      //execute an operation:
      client.execute(mbean, operation, arg1,arg2..., opt);

      //search for mbeans
      client.search(mBeanPattern, opt);

      //list meta info
      client.list(path, opt);

      //version
      client.version(opt);

    }
});

In code above, it retrieves a Jolokia client with given url and performs a request to retrieve the version.

##Client Retrieve In demo above, jolokia function takes two parameters:

  1. The first parameter can be either a url to Jolokia server or a JSON object containing following fields:
  • url: the url to Jolokia server
  • username: the username of Jolokia server HTTP basic authentication
  • password: the password of Jolokia server HTTP basic authentication
  • type: POST or GET
  • jsonp: Whether the request should be sent via JSONP
  1. The second parameter is a callback function which has two parameters:
  2. errors: If client creating failed, errors will be returned.
  3. client: the client Object. See here for the usage of client.

##Client Usage As this lib is just a port of Jolokia official JS library, the client usage is the same as this document.

##Synchronous Request Although the JS lib supports synchronous request, it is highly recomment NOT to use it. In Node.JS environment, keep everything async.