Runtimes for Zowe Dependent Services (Node, Java and bare metal) about community HOT 5 CLOSED

3. Authorized services would likely need to be included in ZWESIS by adding DLLs.

I'm currently working on this. The cross-memory server will be expandable by providing your own load modules which will get picked up by the server, and could be called by a plugin/service name pair.

from community.

@ifakhrutdinov that's great to hear. I agree with Matt that we need a way that someone who is bringing a z/OS runtime to Zowe that delivers z/OS services written in either C, node, Java, has a clear and consistent way to introduce this into the Zowe stack. We also did get asked at the last ZLC whether we should provide a Java runtime that people can drop arbitary .war files into, and whether we should perhaps consolidate some of our existing servers. For example, we have four node servers and five springboot tomcat servers at the moment. I expect we can have fewer

from community.

On z/OS the main scripting language is REXX, well known and extensively used by system programmers. It can be used as cgi scripting with apache http server. It is old tech and runs outside process but as the number of requests for this kind of work is low this isn't really an issue.
Should C, javascript and java be the only accepted languages?

from community.

parent of zowe/zlux#109

from community.

@1000TurquoisePogs The zlux issue seems to be closed. Is there anything that needs to be done elsewhere?

from community.