Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Categories Runtime
Created by Guest
Created on Oct 30, 2013

JVM Server Kategory - Dynamic Deployment

At the moment I am trying several things in JAVA with Cics 5.1 and applications and there is one thing more and more I don't like.<br /><br />For every bundle I have to define a JVM server where it runs on. I think this is not realy flexible and not a good way to do it.<br /><br />In my opinion the programmer should normally not know about the JVM Server. He Should only know about the "Server Type". The deployment to a server should be done and decided by the Platform itselfe. The Platform should know about its "Server pool" and should decide by itselfe on which server the application best runs.<br /><br />But there should be also the possibility like it is now to put special applications on spezial server, like it is now.<br /><br />To sum up I think there must be three scenarios on the bundle definition:<br /><br />1) a default Server pool with a default Pool name<br />2) defined Server pools with defined Pool names (for grouping applications)<br />3) a spezial defined Server (like now)

Idea priority Medium
  • Guest
    Reply
    |
    Jan 5, 2016

    CICS TS 5.3 which is generally available as of December 11th 2015 provides a partial solution , ie a solution for the deployment scenario. Variable substitution allows the developer to give a logical name for the JVMSERVER into which their components (OSGI or Liberty) should be deployed. At build or deployment time (using CICS BT --resolve and a .properties file or application binding override) that variable can be resolved to a physical name. There can be different .properties files for different environments / platforms.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Jan 8, 2015

    We have the same Feeling here. Application developers should never have a direct dependency to a specific infrastructur and names.
    As Peter mentioned there shoul be meta data to describe a certain need for a specific runtime environment in a JVMServer.

  • Guest
    Reply
    |
    Jul 21, 2014

    Time has passed and after a half year our system has grown, and the use cases have changed. This is why I want to update this RFE.

    At a point of futur thinking of myselfe it is very important for IBM to introduce a now logical server artifact. As I see it the Cics Lab has stared to seperate the logical and the phisical layer inside Cics. This is a very important as this makes a lot of sence to this RFE.

    At the moment each application has the phisical Liberty Server in the bundle. The better way would be to define a logical Liberty on the platform and this logical Liberty is pointing to a physical Liberty and "tada" you have your Liberty Server Kategory.

    Now it would be possible to do the same what a local Liberty does. Here you have a Defaultserver and a second one, a third one,.... and so on.

    The scenario would be I have 1 to n phisical Libertys in Cics. On the platform the system programer defines a logical Liberty which is pointing to the phisical one. The handling for a logical one is the same than on a local Liberty. Cics would create a new instance inside the phisical Liberty.

    If the system programmer sees there is an application which needs to shift to another phisical Liberty, he can create a new platform, and tell the logical liberty now your phisical instance is the other logical, install the platform and all the applications work fine without a change.