Appboard/old/batch loading users - Revision history

imported>Jason.nicholls at 18:40, 17 July 2014

2014-07-17T18:40:55Z

← Older revision		Revision as of 18:40, 17 July 2014
Line 4:		Line 4:


	This document outlines a method of creating an AppBoard/enPortal customization to allow an administrator to implement some elements of [[~~Provisioning_Basics~~\|User Provisioning]] outside of the standard application UI.		This document outlines a method of creating an AppBoard/enPortal customization to allow an administrator to implement some elements of [[appboard/old/provisioning_basics\|User Provisioning]] outside of the standard application UI.

imported>Jason.nicholls: moved Batch Loading Users to appboard/old/batch loading users

2014-07-17T16:30:54Z

moved Batch Loading Users to appboard/old/batch loading users

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

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

2014-07-17T16:30:36Z

← Older revision		Revision as of 16:30, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:Batch Loading Users}}
			[[Category:AppBoard old]]
	The AppBoard/enPortal administration user interface (UI) is a robust set of screens and menus that assist the administrator with configuring Users, Domains, Roles, and content permissions in the system. However, in cases with a high volume of Users, a tool may be desired that will enable the administrator to process batch updates to the system.		The AppBoard/enPortal administration user interface (UI) is a robust set of screens and menus that assist the administrator with configuring Users, Domains, Roles, and content permissions in the system. However, in cases with a high volume of Users, a tool may be desired that will enable the administrator to process batch updates to the system.

imported>Jason.nicholls: /* Batch Processing of Provisioning Updates */

2014-07-16T15:48:10Z

Batch Processing of Provisioning Updates

← Older revision		Revision as of 15:48, 16 July 2014
Line 9:		Line 9:
	There are several potential options for an administrator to perform batch updates to system provisioning:		There are several potential options for an administrator to perform batch updates to system provisioning:

	# <b>Custom JSP</b> - Installing a custom JSP file that ~~enables URL commands that can be used~~ to apply provisioning. This is similar to a "Command Line" type of solution (with the application URL used as the "command line"). More information on this approach is available under [[Direct_Provisioning\|Direct Provisioning By Custom JSP]].		# <b>Custom JSP</b> - Installing a custom JSP file that exposes a web interface to manage users.
	# <b>XML Load</b> - This method involves creating an XML file detailing the updates to be made in the system, and then loading the file. Because of the effort required in formatting the XML file, this is typically not a preferred method. The XML Load solution is the option detailed in this document.		# <b>XML Load</b> - This method involves creating an XML file detailing the updates to be made in the system, and then loading the file. Because of the effort required in formatting the XML file, this is typically not a preferred method. The XML Load solution is the option detailed in this document.
	# <b>API Access Interface</b> - A tool and interface can be built that would provide direct access to the AppBoard/enPortal provisioning API. This may be available in the future as a product enhancement.		# <b>API Access Interface</b> - A tool and interface can be built that would provide direct access to the AppBoard/enPortal provisioning API. This may be available in the future as a product enhancement.


	== XML Load Instructions ==		== XML Load Instructions ==

imported>Mike.berman: add more detailed instructions for XML loading

2013-07-10T14:05:49Z

add more detailed instructions for XML loading

← Older revision		Revision as of 14:05, 10 July 2013
Line 25:		Line 25:
	# Save the code shown in the "XML Code" section below into a text file with the file name: batchLoad.xml		# Save the code shown in the "XML Code" section below into a text file with the file name: batchLoad.xml
	# Modify the XML code as appropriate to meet the needs of the customer.		# Modify the XML code as appropriate to meet the needs of the customer.
	# Save the file in to <tt>${Application_Home}/server/~~bin~~/batchLoad.xml</tt>		# Save the file in to <tt>${Application_Home}/server/webapps/enportal/WEB-INF/xmlroot/server/provisioning/batchLoad.xml</tt>
	# Load the XML File into the system, as detailed under <i>Applying Provisioning Updates</i>		# Load the XML File into the system, as detailed under <i>Applying Provisioning Updates</i>

Line 59:		Line 59:
	Perform the following steps to apply provisioning updates using the XML batch file:		Perform the following steps to apply provisioning updates using the XML batch file:

	# Follow the steps above under <i>Installation and Configuration</i> to save the XML code into the application file system.		# Follow the steps above under <i>Installation and Configuration</i> to save the XML code into the application file system as <tt>${Application_Home}/server/webapps/enportal/WEB-INF/xmlroot/server/provisioning/batchLoad.xml</tt>.
	# ~~Load~~ the XML file into the system database.		# Create the following single-line file as <tt>${Application_Home}/server/webapps/enportal/WEB-INF/xmlroot/server/loadBatch.txt</tt>:
			#* provisioning/batchLoad.xml
			# Perform the following steps to load the XML file into the system database:
			#* Log into enPortal/AppBoard as an administrator.
			#* Go to the enPortal URL: <tt>http://<<i>hostname</i>>:<i>port</i>/enportal/home</tt>
			#* Under the “Advanced” tab, select “XMLImport”.
			#* Click “Start” to detect and load the XML file into enPortal.
			#* Observe the message that batchLoad.txt was loaded into the system.
			#* In the Admin UI, review and confirm that the new User accounts and assignments were automatically created.

imported>Mike.berman: created page

2012-10-25T07:13:50Z

created page

New page

The AppBoard/enPortal administration user interface (UI) is a robust set of screens and menus that assist the administrator with configuring Users, Domains, Roles, and content permissions in the system. However, in cases with a high volume of Users, a tool may be desired that will enable the administrator to process batch updates to the system.

This document outlines a method of creating an AppBoard/enPortal customization to allow an administrator to implement some elements of [[Provisioning_Basics|User Provisioning]] outside of the standard application UI.

== Batch Processing of Provisioning Updates ==

There are several potential options for an administrator to perform batch updates to system provisioning:

# Custom JSP - Installing a custom JSP file that enables URL commands that can be used to apply provisioning. This is similar to a "Command Line" type of solution (with the application URL used as the "command line"). More information on this approach is available under [[Direct_Provisioning|Direct Provisioning By Custom JSP]].
# XML Load - This method involves creating an XML file detailing the updates to be made in the system, and then loading the file. Because of the effort required in formatting the XML file, this is typically not a preferred method. The XML Load solution is the option detailed in this document.
# API Access Interface - A tool and interface can be built that would provide direct access to the AppBoard/enPortal provisioning API. This may be available in the future as a product enhancement.

== XML Load Instructions ==
This section details the procedures for implementing the XML Load solution for direct provisioning.

{{Note|This section documents an optional customization to AppBoard/enPortal that is not part of the core system or supported under the standard product maintenance contract. It is recommended that this solution be implemented as part of a consulting engagement to ensure that it is configured and implemented correctly. This solution offers some pieces of provisioning, but does not offer all of the provisioning options that are available in the application's web administration interface.}}

=== Installation and Configuration ===
Perform the following steps to create an XML Load file for custom batch provisioning:

# Save the code shown in the "XML Code" section below into a text file with the file name: batchLoad.xml
# Modify the XML code as appropriate to meet the needs of the customer.
# Save the file in to <tt>${Application_Home}/server/bin/batchLoad.xml</tt>
# Load the XML File into the system, as detailed under Applying Provisioning Updates

=== XML Sample Code ===
<code>[xml,N]

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE AccountDefinitions SYSTEM "../dtds/AccountDefinitions.dtd">
<AccountDefinitions>
<Role name="testing"/>
<Role name="manager" parentRoleID="/testing"/>
<Domain name="EdgeFairfax">
<User userID="ktaylor">
<RoleLink roleID="/testing/manager"/>
<RoleLink roleID="/training"/>
</User>
<User userID="jrowe">
<RoleLink roleID="/training/instructor"/>
</User>
</Domain>
<Domain name="EdgeLaurel">
<User userID="cmorgan">
<RoleLink roleID="/testing"/>
</User>
</Domain>
</AccountDefinitions>
</code>

=== Applying Provisioning Updates ===

Perform the following steps to apply provisioning updates using the XML batch file:

# Follow the steps above under Installation and Configuration to save the XML code into the application file system.
# Load the XML file into the system database.