Versions Compared

Version Old Version 18 New Version 19
Changes made by

Robin Mulloy

Robin Mulloy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
iconfalse

The OperationsCommander platform is capable of integrating with other software and hardware systems including: Banner, Workday, SSO systems, T2 terminals, CALE devices, and many mobile payment providers.

Table of Contents

Considerations for Scoping an Integration

Note

Regardless of the integration we are scoping we need the following questions answered.

  1. What are the endpoints; where will we connect and send data? 
    1. What system or URL are we querying?
  2. Please supply us with Test system logins and a URL an endpoint address to which we can send queries to.
    1. As we progress we will need the same for Production systems.
  3. Are there additional (special) API endpoints and/or API tokens to access the system? 
  4. What API/SDK is recommended?
      Please supply use with supporting
      1. our system is built on PHP and PHP frameworks; we can also work with Java.
    1. Supporting documentation for the system APIs that we are integrating with as well as 
      1. technical contact(s); either on location and/or for the vendor.
    2. How will the data (or user) flow through the system?  ie. business logic/flow

    For Network Administrators

    Our development servers are behind:  

    • 208.124.170.242
    • 178.128.233.75

    Our production servers are behind:  

    • 209.217.117.82
    • 159.203.14.67

    Information Flow through OPS-COM

    This example shows the flow of information through the integrated system of record and OPS-COM.

    Sample: SSO Integration

    This example shows the flow of a user through the system, and at want points the client wanted us to apply business logic.  

    Notice that in their implementation they also described the flag that would be used to designate special users in the system.

    Sample: LDAP/Active Directory Integration

    This represents a standard flow of information to support LDAP/AD user validation.