Sterling OMS HTTP API Tester

By | 07/26/2017

Sterling OMS HTTP API Tester

Why we need this tool ? : Using HTTP tester you can test any new service created or existing API.

Is this only way to test ? : we can create simple Java HTTP program and do the same activity.

HTTP API Tester

How to use HTTP API testing with OMS?

After successful IBM Order Management System install should be able to test the application using http tester. Should be enabled only in test.

Specify the following URL to access the HTTP API tester:

http://localhost:7001/smcfs/yfshttpapi/yantrahttpapitester.jsp

Note: Below link works only when application is up and running.

Sterling OMS HTTP API Tester

Attribute Name Remarks
Is a Service If we are calling out of the box API we should not select the checkbox

If we are calling a service created by our own; we should select the checkbox

Service Name If Is a Service check box selected; enter the Service name (Case Sensitive)
API Name Select API name from drop down (Out of the box API’s)
User ID Sterling application user ID. Refer yfs_user table column LOGINID
Password Sterling application password. Refer yfs_user table password (Encrypted)
Version Select if needed; else blank
Locale Enter locale code; else blank (en_US_EST)
Message Input XML message; should be valid XML
Template Valid template XML; How your output needs to be displayed;

Question : In production how to stop the HTTP tester?

  1. Modify the web.xml: By implementing the security-constraint element with the web-resource-collection element, you can set up authorization to protect this page from unauthorized access.
  2. OR simply remove the yfshttpapi directory under /repository/eardata/platform/war and secure the /interop/InteropHttpServlet servlet using the security features provided by your application server

You can register with us to get more OMS learning updates

OMS Interview Questions

Sterling OMS add new column (Extending)

 

11 thoughts on “Sterling OMS HTTP API Tester

  1. shamsudheen

    To exclude the HTTP API Tester in the production build, specify the following parameter when calling buildear.sh (refer Installation Guide)

    -Ddevmode=false

    Reply
    1. admin

      Thanks for the information. Let us keep learning.

      Reply
  2. ravi

    why we used template XML in API Tester?

    :—— Template XML file allows you to specify a subset of the elements and attributes that the API returns.

    Reply
    1. Admin

      Yes Thanks for the information. here is some more additional information

      What is difference between TotalNumberOfRecords attribute vs MaximumRecords attriute

      TotalNumberOfRecords : Used part of output XML template. When this attribute used select count(*) from table_name where x=y (Search condition applied) query been fired to calculate the total record count. This can create performance issue if more records found.

      MaximumRecords : Used part of list API calls (getOrderList, getItemList). If value not specified defaulted to 5000 record (Most of the cases). if specified returns only number of records specified.

      Wonder from where this 5000 value coming from ? Is it possible to override this value ?

      properties\yfs.properties file
      yantra.app.maxrecords=5000

      You can override this value from customer override properties. But remember this change will get applied to entire system.

      Reply
    1. admin

      Abhi, thanks for your question. Need some time to test this and get back you. Thanks

      Reply
  3. Pingback: Sterling OMS Creating Integration Server - Learn IBM Sterling Order Management System

Leave a Reply

Your email address will not be published. Required fields are marked *