Versions Compared

Version Old Version 16 New Version 17
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

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? 
  2. What system or URL are we querying?
  3. Please supply us with Test system logins and a URL address to which we can send queries to. As we progress we will need the same for Production systems.
  4. Are there API endpoints and/or API tokens to access the system?  What API is recommended?
  5. Please supply use with supporting documentation for the system we are integrating with as well as technical contact(s); on location and/or for the vendor.
  6. How does the data flow through the system?

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

Integrations

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   

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.