Appboard/old/widgets/web page/pim content - Revision history

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

2014-07-17T17:16:16Z

← Older revision		Revision as of 17:16, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:Using PIM Content}}
			[[Category:AppBoard old]]
	enPortal PIMs provide out-of-the-box integration of web application GUIs. In some cases, you may want to display an enPortal channel on a Board in AppBoard.		enPortal PIMs provide out-of-the-box integration of web application GUIs. In some cases, you may want to display an enPortal channel on a Board in AppBoard.

imported>Jason.nicholls: moved Web Widget PIM Content to appboard/old/widgets/web page/pim content

2014-07-17T17:15:29Z

moved Web Widget PIM Content to appboard/old/widgets/web page/pim content

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

imported>Mylene.stolpe at 18:12, 6 February 2014

2014-02-06T18:12:29Z

← Older revision		Revision as of 18:12, 6 February 2014
Line 5:		Line 5:


	For information on the opposite concept, using enPortal to display AppBoard content, see the section on [[~~Creating_Content~~#AppBoard\|creating AppBoard content in enPortal]]. You would only create an AppBoard/Web channel in enPortal if you wanted to access one or more AppBoard boards when accessing the system using the enPortal HTML rendering (/enportal/home).		For information on the opposite concept, using enPortal to display AppBoard content, see the section on [[enportal/5.4/admin/user_administration/content_creation#AppBoard\|creating AppBoard content in enPortal]]. You would only create an AppBoard/Web channel in enPortal if you wanted to access one or more AppBoard boards when accessing the system using the enPortal HTML rendering (/enportal/home).

imported>Cmace: copied from internal

2012-06-19T15:03:03Z

copied from internal

← Older revision		Revision as of 15:03, 19 June 2012
Line 1:		Line 1:
	enPortal PIMs provide out-of-the-box integration of web application GUIs. ~~You~~ may want to display an enPortal channel on a Board in AppBoard. This section provides a tutorial example of using an enPortal Channel to display an integration application GUI in an AppBoard Web Widget.		enPortal PIMs provide out-of-the-box integration of web application GUIs. In some cases, you may want to display an enPortal channel on a Board in AppBoard.


			One such case is when AppBoard is used as the primary front-end (which is appropriate if the landing page is a status page or custom dashboard), but at some point you want to be able to drill down into some native web application. For this, enPortal's proxy must be used, but before AppBoard can access a web application with Single Sign-on, it needs to have an enPortal channel to reference. From the AppBoard client perspective, enPortal channels are like any other web page, except that the link is local and shares the session with AppBoard. The way to accomplish this is to pass in a URL to a Web Widget that is manually constructed (but relative to /enportal rather than an absolute URL). If you plan to access the system with the AppBoard Flash rendering (/enportal/ab/home) and still access a proxied web application, you'd need to first configure the PIM for that application to reach it inside enPortal, then reference the URL (/enportal/vdir/<pathToContent>?<params>) as the URL for a web widget or the URL for a web launch action in AppBoard.


			For information on the opposite concept, using enPortal to display AppBoard content, see the section on [[Creating_Content#AppBoard\|creating AppBoard content in enPortal]]. You would only create an AppBoard/Web channel in enPortal if you wanted to access one or more AppBoard boards when accessing the system using the enPortal HTML rendering (/enportal/home).


			This section provides a tutorial example of using an enPortal Channel to display an integration application GUI in an AppBoard Web Widget.

imported>Mike.berman at 15:23, 15 March 2012

2012-03-15T15:23:45Z

← Older revision		Revision as of 15:23, 15 March 2012
Line 34:		Line 34:
	# Create a Stack called "Reporter".		# Create a Stack called "Reporter".
	# Create a Web Widget and add it to the "Reporter" Stack.		# Create a Web Widget and add it to the "Reporter" Stack.
	# Configure the <b>URL</b> of the Web Widget to be: <tt>/enportal/servlet/pd/vdir/customer1/ReporterHome</tt>		# Configure the <b>URL</b> of the Web Widget to be: <tt>/enportal/servlet/pd/vdir/customer1/ReporterHome</tt> This value is obtained using the following logic: To find the URL value for the portal's channel, you will first identify the channel's location in the portal's virtual directory, and then prefix it with <tt>/enportal/servlet/pd/vdir</tt>. So, in this example, the channel's location is <tt>/customer1/ReporterHome</tt>. Therefore the URL is <tt>/enportal/servlet/pd/vdir/customer1/ReporterHome</tt>.
	# Save the Web Widget and observe the Home channel displayed in the Widget:		# Save the Web Widget and observe the Home channel displayed in the Widget:


	[[Image:ReporterHomeChannelWebWidget.png\|thumb\|center\|700px\|Reporter PIM Web Widget in AppBoard]]		[[Image:ReporterHomeChannelWebWidget.png\|thumb\|center\|700px\|Reporter PIM Web Widget in AppBoard]]

imported>Cmace: copied from internalwiki

2012-03-13T19:09:19Z

copied from internalwiki

New page

enPortal PIMs provide out-of-the-box integration of web application GUIs. You may want to display an enPortal channel on a Board in AppBoard. This section provides a tutorial example of using an enPortal Channel to display an integration application GUI in an AppBoard Web Widget.

In this example, we will display the Home channel from an application called Netcool/Reporter that has been integrated into enPortal using an enPortal PIM called "ibm.reporter_pimC".

== Create the enPortal PIM Channel ==

Perform the following steps to create an enPortal channel called ReporterHome:

# Log in to enPortal as an administrator.
# Install the ibm.reporter_pimC Product Integration Module (PIM) by following the PIM's installation instructions.
# Select the Integrations tab. The Integrations Explorer panel is displayed.
# Right-click on the Directory folder and select New Subfolder.
# Name the new subfolder "customer1".
# Right-click on the customer1 folder and select New Channel.
# For the Channel Name, enter <tt>ReporterHome</tt>.
# For the Channel Type, select "3rd Party Pims".
# For the Type of Pim, select "IBM Tivoli Reporter C".
# For the Class, select "Home".
# For the Target, select "sample".
# Click Next.
# Verify the default channel parameters and click Finish.
# Click the new "ReporterHome" channel under the Directory and confirm that the application Home channel is displayed in the enPortal preview panel. You may need to enter credentials to log in to the application.

[[Image:ValidatingReporterHomeChannel.png|thumb|center|700px|Validating the ReporterHome Channel in enPortal]]

== Create the AppBoard Web Widget ==

# Log in to AppBoard Builder as an administrator.
# Create a Stack called "Reporter".
# Create a Web Widget and add it to the "Reporter" Stack.
# Configure the URL of the Web Widget to be: <tt>/enportal/servlet/pd/vdir/customer1/ReporterHome</tt>
# Save the Web Widget and observe the Home channel displayed in the Widget:

[[Image:ReporterHomeChannelWebWidget.png|thumb|center|700px|Reporter PIM Web Widget in AppBoard]]