Integrations/vpn checklist - Revision history

imported>Jason.nicholls at 16:24, 17 July 2014

2014-07-17T16:24:29Z

← Older revision		Revision as of 16:24, 17 July 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:VPN Checklist}}		{{DISPLAYTITLE:VPN Checklist}}
	[[Category:~~Support~~]]		[[Category:Integrations]]
	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.		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.

imported>Jason.nicholls: moved support/vpn checklist to integrations/vpn checklist

2014-07-17T16:21:03Z

moved support/vpn checklist to integrations/vpn checklist

← Older revision	Revision as of 16:21, 17 July 2014
(No difference)

imported>Jason.nicholls at 16:19, 17 July 2014

2014-07-17T16:19:35Z

← Older revision		Revision as of 16:19, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:VPN Checklist}}
			[[Category:Support]]
	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.		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.

imported>Jason.nicholls: moved VPN Checklist to support/vpn checklist

2014-07-17T16:19:06Z

moved VPN Checklist to support/vpn checklist

← Older revision	Revision as of 16:19, 17 July 2014
(No difference)

imported>Mike.berman: grammar

2011-10-24T23:08:51Z

grammar

← Older revision		Revision as of 23:08, 24 October 2011
Line 35:		Line 35:
	## Familiarity with sample data that is available		## Familiarity with sample data that is available
	## Familiarity with integration requirements (views needed, etc.) and can identify how to access them through the GUI (by menus or direct URL reference)		## Familiarity with integration requirements (views needed, etc.) and can identify how to access them through the GUI (by menus or direct URL reference)
	## ~~Familiar~~ with how to directly query special APIs / interfaces (e.g. SOAP) if needed		## Familiarity with how to directly query special APIs / interfaces (e.g. SOAP) if needed

imported>Mike.berman: created page

2011-10-24T21:21:01Z

created page

New page

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) ==

# Name of Application that is slated for integration development
# Application Version Number / Fixpack

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

# VPN access to lab/network where application is running
## VPN client instructions
### Download
### Installation
### Configuration
### Username / Password<br>(support for access by multiple users is preferred)
## VPN Notes:
### For a Cisco VPN, the SSL/AnyConnect client is preferred over the native Cisco client
### 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:
#### 65.205.41.242
#### 70.169.167.215
### Remote Desktop – This is a secondary option if VPN access is not possible
#### Windows strongly preferred
#### Server must have direct download (e.g. internet or ftp) capability for moving files to the server
# Access to the application
## URL for accessing application
### Through VPN, or
### Direct internet access (application exposed to outside world)
## Admin credentials (username/password/other) to log in to application
## One or more sets of user credentials for logging in to application
# Access to server where application is running
## Path to filesystem where application is installed on server
# Name and contact information for Subject Matter Expert who is familiar with the application and has the following:
## Availability for questions
## Familiarity with sample data that is available
## Familiarity with integration requirements (views needed, etc.) and can identify how to access them through the GUI (by menus or direct URL reference)
## Familiar with how to directly query special APIs / interfaces (e.g. SOAP) if needed