Thanks Scott. The systems where the REST client will be deployed on will not be doing any compiling or object creation. Only consuming the web service.
--
Jim Oberholtzer
Agile Technology Architects
Hi Jim,
That really depends on what you're using.
For HTTPAPI, you'll need:
1) The HTTPAPIR4 service program
2) The EXPAT service program if you're using the XML integration features.
3) The HTTPAPI *CMD, , *PNLGRP and HTTPCMDR4 *PGM objects if using the CL command.
4) The HTTPQSHR4 *PGM object if using the QShell command.
For YAJL you'll need:
1) The YAJL service program
2) The YAJLR4 service program if using YAJL with RPG (including DATA-GEN, DATA-INTO or subprocedure calls)
3) The YAJLDTAGEN program if using the DATA-GEN interface
4) The YAJLINTO program if using the DATA-INTO interface
I'm assuming that you aren't compiling/binding anything on the non-dev box. If for some reason you do plan to bind things, you'll need the binding directories (HTTPAPI and YAJL *BNDDIR objects, respectively.) IF compiling, you'll need the copybooks, too. (HTTPAPI_H, CONFIG_H for HTTPAPI, YAJL_H for YAJL) But, if no compiling or binding, you won't need any of that.
--
Scott Klement
sk@xxxxxxxxxxxxxxxx
I plan to distribute a REST client using the HTTPAPI and YAJL open source to multiple systems. After the modules and programs are compiled what other objects (aside from what’s needed to honor the open source license) need to go with the REST client?
My guess is none of them since they would have been built with the modules/programs, but I don’t really know.