Hello,
   Of course, our Connect/EE implementation continues to grow as it is a great platform.  My application team now wants to change our URL based on the application team.  Example www.mainframe.com/billing for one and www.mainframe.com/requests for another.  I wanted to know if the web server that comes with Connect/EE supports multiple headers or how is that handled?  All of these paths would still come to the same server but allows the customer to feel like they are using different products.  Is there someone that can point me in the direction of a manual that covers this type of setup?  Or would we use our F5 to handle these types of requests?  Is anyone doing this type of thing?  Any help is greatly appreciated.

Thanks in advance
Garrett

------------------------------
Garrett Shaw
Sr System Programmer
Ingram
La Vergne TN
404-964-2032
------------------------------

The URL of a REST API for zCEE is a combination of the basepath that is set when you create an API Project in the zCEE API Toolkit plus whatever is set in each API you create in the API project.

The basepath must be unique within a zCEE server

If you wanted www.mainframe.com/billing , then you would create an API project with the basepath set to billing, and for www.mainframe.com/requests , you would create another project with the basepath set to requests

In example below, the URL for the API would be hostname/zofficev1api/catalog/<number>

There is no web server as such with zCEE, as it is a Liberty server that is receiving the REST APIs requests

------------------------------
Edward McCarthy
WAS on System z
------------------------------

Hi Garrett,

zOS Connect does support the use of multiple "base paths" which is the name for what you describe within this product.

Each "API Project" that is deployed to zOS Connect EE must have its own unique "base path".

In this way, you may have 3 distinct "base paths" across 3 API Projects deployed to the zOS Connect instance:

1. API Project "billing" with a base path of "/billing"
2. API Project "requests" with a base path of "/requests"
3. API Project "accounts" with a base path of "/accounts

All of which can be deployed to the same zOS Connect Instance achieving as you describe, different application contexts for each of the 3 endpoints.

If you visit this page in the documentation it describes the creation of an API project which I am sure you have already created: https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/scenarios/cics_api_create.html
That page describes the process for deploying "one api project" - you would in turn repeat this process for all 3 achieving your goal.

I hope this helps.

Let me know how it goes!

------------------------------
Andy Armstrong
Winchester
------------------------------