Integrations/vpn checklist

Access to an application in your lab may be needed for developers to write a new integration and for testing the integration. This page details the requirements for providing application access to the integration development team.

Items for Integration Developer (Edge) to Provide to Requester (Customer/Partner)

1. Name of Application that is slated for integration development
2. Application Version Number / Fixpack

Items for Requester (Customer/Partner) to Provide to Integration Developer (Edge)

1. VPN access to lab/network where application is running
   1. VPN client instructions
      1. Download
      2. Installation
      3. Configuration
      4. Username / Password
         (support for access by multiple users is preferred)
   2. VPN Notes:
      1. For a Cisco VPN, the SSL/AnyConnect client is preferred over the native Cisco client
      2. Please advise if there are any source IP address restrictions, so Edge can provide a list of source IPs that will be used. For starters, the following source IPs (Edge network) should be supported:
         1. 65.205.41.242
         2. 70.169.167.215
      3. Remote Desktop – This is a secondary option if VPN access is not possible
         1. Windows strongly preferred
         2. Server must have direct download (e.g. internet or ftp) capability for moving files to the server
2. Access to the application
   1. URL for accessing application
      1. Through VPN, or
      2. Direct internet access (application exposed to outside world)
   2. Admin credentials (username/password/other) to log in to application
   3. One or more sets of user credentials for logging in to application
3. Access to server where application is running
   1. Path to filesystem where application is installed on server
4. Name and contact information for Subject Matter Expert who is familiar with the application and has the following:
   1. Availability for questions
   2. Familiarity with sample data that is available
   3. Familiarity with integration requirements (views needed, etc.) and can identify how to access them through the GUI (by menus or direct URL reference)
   4. Familiarity with how to directly query special APIs / interfaces (e.g. SOAP) if needed