Integrations/ca/concord.ehealth pimB - Revision history

imported>Jason.nicholls: moved EHealth pimB to integrations/ca/concord.ehealth pimB

2014-07-25T03:53:07Z

moved EHealth pimB to integrations/ca/concord.ehealth pimB

← Older revision	Revision as of 03:53, 25 July 2014
(No difference)

imported>Teri.roberts at 15:48, 24 June 2014

2014-06-24T15:48:47Z

← Older revision		Revision as of 15:48, 24 June 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:CA eHealth [Concord] pimB}}		{{DISPLAYTITLE:CA eHealth [Concord] pimB}}
	[[Category:Integrations]]		[[Category:Integrations]]
	This page documents the enPortal integration for CA eHealth.		This page documents the enPortal integration for CA eHealth [Concord] .

	* <b>Vendor</b>: CA Technologies		* <b>Vendor</b>: CA Technologies

imported>Teri.roberts at 15:38, 24 June 2014

2014-06-24T15:38:16Z

← Older revision		Revision as of 15:38, 24 June 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:CA Concord ~~eHealth~~ pimB}}		{{DISPLAYTITLE:CA eHealth [Concord] pimB}}
	[[Category:Integrations]]		[[Category:Integrations]]
	This page documents the enPortal integration for CA eHealth.		This page documents the enPortal integration for CA eHealth.

	* <b>Vendor</b>: CA Technologies		* <b>Vendor</b>: CA Technologies
	* <b>Product</b>: eHealth		* <b>Product</b>: eHealth [Concord]
	* <b>Supported Version(s)</b>: 6.2		* <b>Supported Version(s)</b>: 6.2
	* <b>Name of enPortal Integration Package</b>: ca.ehealth_pimB		* <b>Name of enPortal Integration Package</b>: ca.ehealth_pimB

imported>Teri.roberts at 17:23, 6 February 2014

2014-02-06T17:23:47Z

← Older revision		Revision as of 17:23, 6 February 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:CA Concord eHealth pimB}}
			[[Category:Integrations]]
	This page documents the enPortal integration for CA eHealth.		This page documents the enPortal integration for CA eHealth.

imported>Teri.roberts at 18:02, 31 October 2013

2013-10-31T18:02:12Z

← Older revision		Revision as of 18:02, 31 October 2013
Line 98:		Line 98:
	*** Label: Target Frame		*** Label: Target Frame
	*** Description: Identifies a named frame the report should target: _top=topmost frame, crstop='top' of the channel, newframe= launch a new frame, or '_self'=current frame.		*** Description: Identifies a named frame the report should target: _top=topmost frame, crstop='top' of the channel, newframe= launch a new frame, or '_self'=current frame.



Line 115:		Line 116:
	# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.		# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.
	# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.		# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.



	=== Create Channels ===		=== Create Channels ===

imported>Teri.roberts at 18:01, 31 October 2013

2013-10-31T18:01:28Z

← Older revision		Revision as of 18:01, 31 October 2013
Line 30:		Line 30:
	Perform the following steps to install the CA eHealth PIM:		Perform the following steps to install the CA eHealth PIM:
	# Install AppBoard/enPortal as detailed in the [[Installation\|Installation]] documentation		# Install AppBoard/enPortal as detailed in the [[Installation\|Installation]] documentation
	# Download the file ~~concord~~.ehealth_pimB.jar		# Download the file ca.ehealth_pimB.jar
	# Start enPortal and login as an administrator		# Start enPortal and login as an administrator
	## User Name: administrator		## User Name: administrator
Line 37:		Line 37:
	# Under the <b>Advanced</b> tab, select <b>PIMImport</b>		# Under the <b>Advanced</b> tab, select <b>PIMImport</b>
	# Click the <b>Choose File...</b> button		# Click the <b>Choose File...</b> button
	# Locate the ~~concord~~.ehealth_pimB.jar file in the Open dialog		# Locate the ca.ehealth_pimB.jar file in the Open dialog
	# Click the <b>Start</b> button to extract the files from the PIM .jar archive		# Click the <b>Start</b> button to extract the files from the PIM .jar archive
	# Under the <b>Advanced</b> tab, select <b>XMLImport</b>		# Under the <b>Advanced</b> tab, select <b>XMLImport</b>
	# Click the <b>Start</b> button to load the PIM into the system		# Click the <b>Start</b> button to load the PIM into the system
	# Confirm that the following message is displayed: "Import completed; loaded the following file(s): ~~load_concord~~.ehealth_pimB.txt"		# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_ca.ehealth_pimB.txt"
	# Under the <b>Advanced</b> tab, select <b>Explore System</b>		# Under the <b>Advanced</b> tab, select <b>Explore System</b>
	# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel		# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
Line 112:		Line 112:
	## Click "Save" to keep your changes		## Click "Save" to keep your changes
	# Click on the <b>Integrations</b> tab		# Click on the <b>Integrations</b> tab
	# In the Explorer, under Packages, expand the ~~concord~~.ehealth_pimB tree and click on the <b>Sample</b> target. Confirm that the information you entered is displayed for your CA eHealth server		# In the Explorer, under Packages, expand the ca.ehealth_pimB tree and click on the <b>Sample</b> target. Confirm that the information you entered is displayed for your CA eHealth server
	# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.		# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.
	# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.		# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.
Line 121:		Line 121:

	# Click on the <b>Applications</b> tab		# Click on the <b>Applications</b> tab
	# Right-click on the name "sample" in the row for ~~concord~~.ehealth_pimB and select a channel type		# Right-click on the name "sample" in the row for ca.ehealth_pimB and select a channel type
	# In the "Channel Name" box, enter the name you want to give to the new channel		# In the "Channel Name" box, enter the name you want to give to the new channel
	# For "Channel Type", select "3rd Party Pims"		# For "Channel Type", select "3rd Party Pims"
Line 127:		Line 127:
	# Click <b>Finish</b>		# Click <b>Finish</b>
	# Click on the Integrations tab		# Click on the Integrations tab
	# In the Explorer, under Packages, expand the ~~concord~~.ehealth_pimB tree and click on the Sample target. Confirm that the new channel is listed along with the other sample channels		# In the Explorer, under Packages, expand the ca.ehealth_pimB tree and click on the Sample target. Confirm that the new channel is listed along with the other sample channels


	Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.		Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.

			=== Known Issues ===

			The following known issues are associated with this PIM:

			*There are currently not any known issues associated with this PIM


			=== License Usage ===

			In order for the AppBoard/enPortal administrator to configure the ca.ehealth_pimB PIM, the AppBoard/enPortal license.properties file must include licensing for at least one ca.ehealth_pimB server. The administrator can create one additional host ("target") in AppBoard/enPortal for each server license included in the license file.

			Each AppBoard/enPortal user maintains one user session with the CA eHealth server. The CA eHealth application must be licensed to support the number of users that will be accessing the application through AppBoard/enPortal.


			=== Version Support ===

			The following matrix details the supported CA eHealth and compatible AppBoard/enPortal versions:

			{\| class="wikitable" border="1" style="background-color:#eeeeee;"
			\|+ align="bottom" style="color:#e76700;" \|''Version Support''
			\|-
			! width="150" \| Package Name
			! width="150" \| enPortal Version
			! width="150" \| CA eHealth Supported Versions
			\|-
			\| ca.ehealth_pimB
			\| 4.6.1+
			\| 6.2
			\|}

			{{Tip\|To see the current enPortal version, run the <tt>portal version</tt> command from the <tt>[AppBoard_Home]/server/bin</tt> directory.}}


	== CA eHealth Upgrades ==		== CA eHealth Upgrades ==
Line 143:		Line 176:
	Perform the following steps when the CA eHealth server is upgraded to a newer version of CA eHealth:		Perform the following steps when the CA eHealth server is upgraded to a newer version of CA eHealth:

	# Check the AppBoard/enPortal PIM online documentation to see if the new CA eHealth version is supported by the existing ~~concord~~.ehealth_pimB PIM.		# Check the AppBoard/enPortal PIM online documentation to see if the new CA eHealth version is supported by the existing ca.ehealth_pimB PIM.
	## To test if the new CA eHealth version is supported by the existing PIM that you have installed, perform the following steps:		## To test if the new CA eHealth version is supported by the existing PIM that you have installed, perform the following steps:
	### Click on the <b>Applications</b> tab		### Click on the <b>Applications</b> tab
Line 157:		Line 190:
	== Uninstall ==		== Uninstall ==

	{{Warning\|Uninstalling the ~~concord~~.ehealth_pimB PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.}}		{{Warning\|Uninstalling the ca.ehealth_pimB PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.}}

	Perform the following steps to uninstall the ~~concord~~.ehealth_pimB PIM:		Perform the following steps to uninstall the ca.ehealth_pimB PIM:

	# Click on the <b>Integrations</b> tab		# Click on the <b>Integrations</b> tab
	# In the Explorer, under Packages, locate the ~~concord~~.ehealth_pimB integration		# In the Explorer, under Packages, locate the ca.ehealth_pimB integration
	# Right click on the integration name, and select "Delete"		# Right click on the integration name, and select "Delete"
	# Click "Ok" to confirm that you want to delete the integration package		# Click "Ok" to confirm that you want to delete the integration package

imported>Nick.chang: /* Configuration */

2013-10-31T16:26:49Z

Configuration

← Older revision		Revision as of 16:26, 31 October 2013
Line 105:		Line 105:

	# Click on the <b>Applications</b> tab		# Click on the <b>Applications</b> tab
	# Right-click on the name "sample" in the row for ~~concord.ehealth_pimB~~ and select "Modify"		# Right-click on the name "sample" in the row for "CA eHealth" and select "Modify"
	# Fill in the items in the <b>Modify Application Wizard</b> dialog:		# Fill in the items in the <b>Modify Application Wizard</b> dialog:
	## Select the protocol used to access your CA eHealth server (http or https)		## Select the protocol used to access your CA eHealth server (http or https)
Line 115:		Line 115:
	# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.		# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.
	# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.		# Log in using the same credentials you would use for accessing the CA eHealth application in a browser. Confirm that the CA eHealth Home page is displayed.


	=== Create Channels ===		=== Create Channels ===

imported>Nick.chang at 16:25, 31 October 2013

2013-10-31T16:25:42Z

← Older revision		Revision as of 16:25, 31 October 2013
Line 3:		Line 3:
	* <b>Vendor</b>: CA Technologies		* <b>Vendor</b>: CA Technologies
	* <b>Product</b>: eHealth		* <b>Product</b>: eHealth
	* <b>Supported Version(s)</b>: 6		* <b>Supported Version(s)</b>: 6.2
	* <b>Name of enPortal Integration Package</b>: ca.ehealth_pimB		* <b>Name of enPortal Integration Package</b>: ca.ehealth_pimB
	* <b>Required enPortal Version</b>: 4.6.1 and above		* <b>Required enPortal Version</b>: 4.6.1 and above

imported>Nick.chang at 16:24, 31 October 2013

2013-10-31T16:24:23Z

← Older revision		Revision as of 16:24, 31 October 2013
Line 4:		Line 4:
	* <b>Product</b>: eHealth		* <b>Product</b>: eHealth
	* <b>Supported Version(s)</b>: 6		* <b>Supported Version(s)</b>: 6
	* <b>Name of enPortal Integration Package</b>: ~~concord~~.ehealth_pimB		* <b>Name of enPortal Integration Package</b>: ca.ehealth_pimB
	* <b>Required enPortal Version</b>: 4.6.1 and above		* <b>Required enPortal Version</b>: 4.6.1 and above

imported>Teri.roberts: /* Installation */

2013-07-29T23:11:02Z

Installation

← Older revision		Revision as of 23:11, 29 July 2013
Line 42:		Line 42:
	# Click the <b>Start</b> button to load the PIM into the system		# Click the <b>Start</b> button to load the PIM into the system
	# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_concord.ehealth_pimB.txt"		# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_concord.ehealth_pimB.txt"
			# Under the <b>Advanced</b> tab, select <b>Explore System</b>
	# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel		# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
	# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel		# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel
	# In the Manage Proxy tool, click “Reset All”		# In the Manage Proxy tool, click “Reset All”
	# Refresh the browser		# Refresh the browser