InReach CE Center API Integration

VIDEO TRANSCRIPT | Recorded: 2022-01-27 | Verify against current system state

Abstract¶

Technical overview of the InReach CE Center integration architecture covering the SSO API authentication flow, conference evaluation certificate syncing via Windows service, database triggers for queue population, retry logic for failed syncs, and escalation procedures for InReach outages. Explains how CE credits from conference evals are pushed to InReach CE tracker and made available in members' portfolios.

Key Procedures¶

• Log into CE Center which triggers API call to push user info (username, first name, last name, email, member type)
• Complete session evaluations and general conference evaluation to trigger credit sync
• Database trigger inserts records into inreach_eval_queue table when evals complete
• Windows service picks up queue entries (10-15 at a time) and processes through InReach API
• Failed syncs retry up to 3 times before marking as failed
• Check queue table status to monitor sync progress and failures
• Reset failed entries by clearing process date and setting attempts to zero
• View service logs on production server (Web01C) for troubleshooting
• Contact Julie Wilmer or InReach support for escalation
• Verify CE Center redirect from cecenter.amp.org to amp.inreach.com

Notable Statements¶

• 0:01:02 "It's not SAML. It's a specific API integration. It picks up the username, first name, last name, email address and member type and pushes that over into CE Center."
• 0:06:23 "It picks up really fast. It added the new session and gave me more credit."
• 0:07:06 "I had to use triggers. I have not used triggers anywhere else in the entire system. But this is one area where it just made sense."
• 0:08:34 "I believe three times. At that point, it will just fail completely, won't try again."
• 0:09:05 "There's oftentimes where the InReach API integration fails or there's a deadlock and it just fails just because of the deadlock."
• 0:10:09 "This is probably one of the first alerts you'll see because it runs so often."
• 0:14:03 "You can see we've had a good day so far. Everything has worked."
• 0:17:22 "This is another one where it's scary because this never breaks."
• 0:19:10 "If I try to push something over to InReach, they're not going to accept it because there's no user... you have to create the user first."
• 0:23:17 "We weren't able to provide us with a vanity URL. So we redirect all traffic from cecenter.amp.org over to amp.inreach.com."

Systems & Configurations¶

Systems Mentioned¶

• InReach CE Center (LMS, CE tracking)
• Aptify (AMS)
• Windows Service (InReach Eval Sync)
• Eval System (conference evaluations)
• AAMPDB (legacy database)
• Postman (API testing)

Specific Configurations¶

Credentials/Access Mentioned¶

• SharePoint: InReach Technical Documentation
• Julie Wilmer (personal cell): Primary InReach contact
• InReach Application Support number: Member call center
• InReach support hours: 8am-5pm

Errors & Troubleshooting¶

• Issue: API deadlock failures
• Cause: Database contention or API issues
• Resolution: Automatic retry up to 3 times, usually succeeds on second attempt

• Timestamp: 0:09:05

• Issue: User doesn't exist in InReach

• Cause: Person attended conference but never visited CE Center
• Resolution: Windows service creates user first, then syncs credits

• Timestamp: 0:19:10

• Issue: Extended outage causing mass failures

• Cause: InReach system down or database issues
• Resolution: Reset failed entries: clear process date, set attempts to 0
• Timestamp: 0:25:30

Transcript Gaps & Quality Notes¶

• Training session for Keith (new team member)
• References to SharePoint documentation with detailed procedures
• Mentions upcoming virtual conference integration work
• Discussion of escalation process with specific contacts
• Recording covers technical architecture and troubleshooting procedures