DataPower

 View Only

  • 1.  files under the file management of local:/isp/policy/ are not same for all DataPower nodes

    Posted Mon February 26, 2024 06:36 AM

    Hello All,

    We have 3 DataPower nodes in one of our environment. 
    Among 3 DP nodes, only one node has many files under local directory in the  below path:

    local:/isp/policy

    But the remaining node2 and node3  don't have as many files as node1 have. We have no idea what those files are for.

    We have a SOAP API hosted on API Connect and when we hit the API on node1 with invalid schema it's giving the error information as we expected.

    But on the remaining 2 nodes we are not getting the expected error response but we could see the expected error details in the DataPower log directory.

    The reason is when  we hit the API on node2 and node3 compiler is looking for the file called apim.context.xsl 
    local:/isp/policy/apim.context.xsl  which is not existed on the node2 and node3.

    The same file is existed in the node1 and we don't know how it came in node1 under local:/isp/policy and don't know why the same file is not exist in the 
    node2 and node3.

    And all these files under local:/isp/policy/ are having COPYRIGHT-TOP by IBM but these are editable.

    Can anyone give me the picture on how it works? 

     



    ------------------------------
    Kumar
    ------------------------------


  • 2.  RE: files under the file management of local:/isp/policy/ are not same for all DataPower nodes

    Posted Tue February 27, 2024 05:26 AM

    Hello Everyone,

    Could you please check and assist me with your Insights.



    ------------------------------
    Kumar
    ------------------------------

    Original Message


  • 3.  RE: files under the file management of local:/isp/policy/ are not same for all DataPower nodes

    IBM Champion
    Posted Tue February 27, 2024 10:18 AM

    These are files used by API Connect.  I suppose all three nodes are part of a quorum for your environment?  If so, just copy the missing files over to the others and see if it clears up the issue.

    P.S.  Though I don't want to get in trouble with the IBM folks, it would be a bit remiss not to say this; but API connect, in my experience, has a bad habit of changing things around inconsistently.  So much so I've written my own "check-and-synchronize" tools to ensure all nodes are configured exactly the same.



    ------------------------------
    Joseph Morgan
    ------------------------------

    Original Message


  • 4.  RE: files under the file management of local:/isp/policy/ are not same for all DataPower nodes

    Posted Tue February 27, 2024 10:16 AM
    Edited by Steve Linn Tue February 27, 2024 04:29 PM

    Hi Kumur, 

    First off this is an API Connect issue and should be discussed in that forum instead of the DataPower forum but having said that, in API Connect the local:///isp and child directories contain the required v5(c) framework files. If your gateway is a v5c gateway it should contain all files required by the v5c service, a multi-protocol gateway named webapi. If your gateway is an API Gateway, then these directories will contain a subset of the v5c framework files, a child apigw directory and some additional.js files required for what are called v5 emulation policies. 

    The fact your apim.context.xsl file is missing from two of your three nodes is definitely an issue as all the nodes of the same gateway regardless of gateway type should be the same. I would suspect some type of deployment issue but I know there have been fixes which you could be missing depending upon your DataPower fixpack version your nodes have deployed. I would suggest you open an API Connect PMR to assist diagnosing the exact cause of your issue. 

    Best Regards,

    Steve



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM
    ------------------------------

    Original Message