Versions Compared

Old Version 26

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user 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. Test system logins and a test endpoint address to which we can send queries to.
      1. we will need the same for production systems  
  2. Are there additional (special) API endpoints and/or API tokens to access the system? 
  3. What API/SDK is recommended?
    1. at the core the OPS-COM platform is built on PHP; we also work with Java and many other languages
  4. Supporting documentation for the API/SDKs that we are integrating with
    1. technical contact(s); either on location and/or for the vendor.
  5. 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 what 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.

Current APIs Available

OperationsCommander (OPS-COM) has made APIs (Application Programming Interface) available that allow for third-parties with proper authentication to interact and manipulate data in OPS-COM as needed to accomplish specific functions, for example adding valid permits from pay and display machines. Refer to this wiki article for more information on currently available APIs.

Other Integrations Available

OPS-COM has integrations with third-parties. Your Sales Rep can discuss how you can make use of these integrations. 

  • T2 Luke II Meters
  • CALE Meters
  • MacKay Meters
  • Tattile Cameras
  • Vaxtor Cameras
  • gTechna Cameras
  • HotSpot Temporary Permits


Related Pages

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
sorttitle
cqllabel in ("sso","ldap","login") and space = currentSpace()


Show if
special@authenticated


Support Agent Notes

Support Notes

  • Pay station machines such as T2 must be pushing a zone into our system that is attached with an actual lot. If the zone is not set up with a lot then it will display as active in the Pay Station data but not on the handheld unit. If the zone that is being pushed into the system is not being used, then the permits will show as invalid. 

Related

Projects2cd5be47-4b47-371a-a141-44aeb050c749OPSCOM-805