WebSphere Application Server & Liberty

 View Only
  • 1.  How to merge WAS and Liberty IHS plugins

    Posted Wed September 13, 2023 07:38 AM

    Hello, we're migrating an old IBM Operational Decision Manager version running on WAS to the latest ODM 8.11 release running on Liberty. We need both releases running on different ports of the same node while configuration finish. Direct access to the nodes is not allowed in this customer, access is configured in IHS.

    I don't know much about IHS,  I found a pluginUtility that allows mergin 2 plugins. But I have some questions:

    ¿Is it possible to merge 2 plugins generated by different application servers like WAS and liberty?

    ¿How can I configure IHS to provide access to same routes in 2 application servers in the same host?

    To be more clear, I need is something like this:

    http://<IHS-host>:<port1>/DecisionService/...  ==> http://<node>:<was-port>/DecisionService /...

    http://<IHS-host>:<port2>/DecisionService/...  ==> http://<node>:<liberty-port>/DecisionService /...

    Thanks in advance. 



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------


  • 2.  RE: How to merge WAS and Liberty IHS plugins

    Posted Wed September 13, 2023 02:18 PM

    Hi Eduardo, merging traditional and liberty should work. To get the behavior you want, I suggest:

    1. make a copy of both the WAS and Liberty plugin-cfg.xml
    2. Update the default_host virtualhost of each XML so they are non-overlapping and match the webserver port1/port2
    3. merge the files using the Liberty pluginUtility

    You should end up with two virtual hosts, two ServerClusters, and two Route tags. 

    Route tags are best read right-to-left and map a virtualhost + URIGroup to a ServerCluster.



    ------------------------------
    Eric Covener
    ------------------------------



  • 3.  RE: How to merge WAS and Liberty IHS plugins

    Posted Wed September 13, 2023 03:05 PM

    I should have added, that whichever version gets the non-standard port, it will need to be reflected in the appserver virtual host configuration.



    ------------------------------
    Eric Covener
    ------------------------------



  • 4.  RE: How to merge WAS and Liberty IHS plugins

    Posted Thu September 14, 2023 03:40 AM

    Hi Eric, thank you very much. I think that I understood, but I'm very new to IHS, just to be sure.

    I should edit both plugins and replace the default virtual host name ("*") by two different <virtual-host-name> for was and liberty backends. I can keep the default ports (80 and 443) in both plugins and it is safe.

    So, I edit each plugin and instead of:

      <VirtualHostGroup Name="default_host">
          <VirtualHost Name="*:80"/>
          <VirtualHost Name="*:443"/>
      </VirtualHostGroup>

    I replace by:

    <VirtualHostGroup Name="default_host">
          <VirtualHost Name="<virtural-host-name>:80"/>
          <VirtualHost Name="<virtual-host-name>:443"/>
    </VirtualHostGroup>
    

    Is it like this?



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------



  • 5.  RE: How to merge WAS and Liberty IHS plugins
    Best Answer

    Posted Thu September 14, 2023 08:10 AM

    yes, if you replace wildcards with non-overlapping hostnames, the routing should do what you expect (and not require users of either server to specify a port).



    ------------------------------
    Eric Covener
    ------------------------------