File Explorer PIM - Revision history

imported>Jason.nicholls: /* File Explorer PIM Package */

2014-07-17T18:30:40Z

File Explorer PIM Package

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

	The File Explorer PIM package is delivered as a JAR file. This is an archive that contains all of the directories and files that comprise the PIM.		The File Explorer PIM package is delivered as a JAR file. This is an archive that contains all of the directories and files that comprise the PIM.

	~~=== Installing the PIM Package ===~~

	~~{{Note\|enPortal must be running before you begin the PIM installation process.}}~~


	~~See the following article for instructions on installing the File Explorer PIM package: [[PIM_Installation\|Installing a PIM]]~~



	= Configuration =		= Configuration =

192.168.21.185: fix text wrapping

2010-07-20T20:22:56Z

fix text wrapping

← Older revision		Revision as of 20:22, 20 July 2010
Line 3:		Line 3:
	File Explorer is a Product Integration Module (PIM) available from [http://www.edge-technologies.com Edge Technologies]. It allows for the creation of portal content which can directly access files on the portal server. The file explorer add-on looks similar to Windows Explorer, with the ability to configure the root folder where exploration starts and give it an alias.		File Explorer is a Product Integration Module (PIM) available from [http://www.edge-technologies.com Edge Technologies]. It allows for the creation of portal content which can directly access files on the portal server. The file explorer add-on looks similar to Windows Explorer, with the ability to configure the root folder where exploration starts and give it an alias.

	[[Image:FileExplorer.jpg\|thumb\|700px\|Sample view in enPortal using the File Explorer]]		[[Image:FileExplorer.jpg\|thumb\|center\|700px\|Sample view in enPortal using the File Explorer]]


	= Installation =		= Installation =

imported>Nick.chang: /* Folder Actions */

2010-07-14T14:58:22Z

Folder Actions

← Older revision		Revision as of 14:58, 14 July 2010
Line 147:		Line 147:
	# Expand the folder Directory / system / .cmd / folder		# Expand the folder Directory / system / .cmd / folder
	# Right-click on the action to hide and select "Security" and add a deny all rule to the action		# Right-click on the action to hide and select "Security" and add a deny all rule to the action
			<br/>

	=== File Actions ===		=== File Actions ===

imported>Nick.chang: /* Channel Configuration */ change root node example value

2010-07-14T14:57:37Z

Channel Configuration: change root node example value

← Older revision		Revision as of 14:57, 14 July 2010
Line 102:		Line 102:
	\| Root Node		\| Root Node
	\| The absolute reference of a node to be the root of the tree (optional). This will be appended to any system-level root node defined as the master directory location in <tt>pkg-edge.fileexplorer.properties</tt>.		\| The absolute reference of a node to be the root of the tree (optional). This will be appended to any system-level root node defined as the master directory location in <tt>pkg-edge.fileexplorer.properties</tt>.
	\| <tt>~~/httproot/custom~~</tt>		\| <tt>${shim:session.credentials.domain}</tt>
	\|-		\|-
	\| Root Node Label		\| Root Node Label
Line 116:		Line 116:
	\| <tt>false</tt>		\| <tt>false</tt>
	\|}		\|}


	== File Explorer Actions ==		== File Explorer Actions ==

imported>Nick.chang: /* Master Directory Location */ change edgetech.fileexplorer.home location to a more secured location

2010-07-14T14:56:09Z

Master Directory Location: change edgetech.fileexplorer.home location to a more secured location

← Older revision		Revision as of 14:56, 14 July 2010
Line 56:		Line 56:
	#: <tt>edgetech.fileexplorer.home=${portal.home}/''<your directory path>''</tt>		#: <tt>edgetech.fileexplorer.home=${portal.home}/''<your directory path>''</tt>
	#:		#:
	#: Example: <tt>edgetech.fileexplorer.home=~~${portal.home}~~/~~httproot~~/~~custom/fileroot~~</tt>		#: Example: <tt>edgetech.fileexplorer.home=C:/Docs/Customer</tt>
	# Re-start enPortal		# Re-start enPortal



	== File Explorer Channels ==		== File Explorer Channels ==

imported>Nick.chang: /* Folder Actions */ added alternative hide action

2010-07-14T14:46:20Z

Folder Actions: added alternative hide action

← Older revision		Revision as of 14:46, 14 July 2010
Line 143:		Line 143:
	# Right-click on the action to eliminate and select "Delete"		# Right-click on the action to eliminate and select "Delete"


			Or alternatively perform the following steps to hide support for any of the above actions:

			# Log in to enPortal as administrator
			# Click on the Administration view
			# Expand the folder Directory / system / .cmd / folder
			# Right-click on the action to hide and select "Security" and add a deny all rule to the action

	=== File Actions ===		=== File Actions ===

imported>Nick.chang: /* File Actions */ added hide action alternative

2010-07-14T14:45:13Z

File Actions: added hide action alternative

← Older revision		Revision as of 14:45, 14 July 2010
Line 162:		Line 162:
	# Expand the folder Directory / system / .cmd / file		# Expand the folder Directory / system / .cmd / file
	# Right-click on the action to eliminate and select "Delete"		# Right-click on the action to eliminate and select "Delete"

			Or alternatively perform the following steps to hide support for any of the above actions:

			# Log in to enPortal as administrator
			# Click on the Administration view
			# Expand the folder Directory / system / .cmd / file
			# Right-click on the action to hide and select "Security" and add a deny all rule to the action


	{{Tip\|In many cases you might have access to log in to a customer's portal, but do not have physical access to the files on their server. If the customer installs the File Explorer PIM, they can configure it to give you access to some files on their server. This could be useful for viewing log files, for example, or XML customizations.}}		{{Tip\|In many cases you might have access to log in to a customer's portal, but do not have physical access to the files on their server. If the customer installs the File Explorer PIM, they can configure it to give you access to some files on their server. This could be useful for viewing log files, for example, or XML customizations.}}

imported>Mike.berman: /* Overview */

2010-07-13T21:29:30Z

Overview

← Older revision		Revision as of 21:29, 13 July 2010
Line 3:		Line 3:
	File Explorer is a Product Integration Module (PIM) available from [http://www.edge-technologies.com Edge Technologies]. It allows for the creation of portal content which can directly access files on the portal server. The file explorer add-on looks similar to Windows Explorer, with the ability to configure the root folder where exploration starts and give it an alias.		File Explorer is a Product Integration Module (PIM) available from [http://www.edge-technologies.com Edge Technologies]. It allows for the creation of portal content which can directly access files on the portal server. The file explorer add-on looks similar to Windows Explorer, with the ability to configure the root folder where exploration starts and give it an alias.

	[[Image:FileExplorer.jpg\|~~frame~~\|Sample view in enPortal using the File Explorer]]		[[Image:FileExplorer.jpg\|thumb\|700px\|Sample view in enPortal using the File Explorer]]


	= Installation =		= Installation =

imported>Mike.berman: created page

2010-07-13T21:10:14Z

created page

New page

= Overview =

File Explorer is a Product Integration Module (PIM) available from [http://www.edge-technologies.com Edge Technologies]. It allows for the creation of portal content which can directly access files on the portal server. The file explorer add-on looks similar to Windows Explorer, with the ability to configure the root folder where exploration starts and give it an alias.

[[Image:FileExplorer.jpg|frame|Sample view in enPortal using the File Explorer]]

= Installation =

To install File Explorer, first update the enPortal license file and then install the PIM package.

== enPortal License File ==

The enPortal license file is located in the [portal_home]/config folder. It is usually named license.properties. When you purchase the File Explorer PIM, your vendor will provide a license file to support the PIM. This can either be a full update of the license.properties file or a separate license file.

=== Installing the License File ===

Perform the following steps to install the license file:

# View the license file provided to you by the vendor to confirm that it has a line labeled as follows:
#: <tt>FEATURE=edge.fileexplorer</tt>
# Save the file into the following folder on the portal server:
#: <tt>[portal_home]/config</tt>
#:The file can either replace your existing license file or be added into the directory along with the existing file(s).
# Re-start enPortal

== File Explorer PIM Package ==

The File Explorer PIM package is delivered as a JAR file. This is an archive that contains all of the directories and files that comprise the PIM.

=== Installing the PIM Package ===

{{Note|enPortal must be running before you begin the PIM installation process.}}

See the following article for instructions on installing the File Explorer PIM package: [[PIM_Installation|Installing a PIM]]

= Configuration =

Once the File Explorer PIM is installed, you must create views and channels that use the File Explorer interface. You can then provision these views and channels to the users of the system.

== Master Directory Location ==

File Explorer has a properties file that configures the base location the FileExplorer is capable of showing documents from. You can also create multiple copies of the FileExplorer channel and configure them to only be able to display folders and sub-folders within a path of the base location (specified by the properties file).

To set the master directory location for the enPortal system:

# Open the following file in a text editor:
#: <tt>[portal_home]/config/pkg-edge.fileexplorer.properties</tt>
# Edit the following line to set the top level folder that is exposed by the file explorer
#: <tt>edgetech.fileexplorer.home=${portal.home}/''<your directory path>''</tt>
#:
#: Example: <tt>edgetech.fileexplorer.home=${portal.home}/httproot/custom/fileroot</tt>
# Re-start enPortal

== File Explorer Channels ==

{{Warning|Provisioning channels to a user that contain the File Explorer will give the user access to certain files on the portal server.}}

Perform the following steps to configure and provision the File Explorer:

# Log in as a portal administrator.
# Configure the FileExplorer channel to specify a sub-folder within the Master Directory location
# Render the FileExplorer channel to confirm that it presents an explorer tree (similar to Windows Explorer), providing an interface to view the files and folders available within the Master Directory path and sub-folder.
# Copy the FileExplorer channel and configure for each separate document explorer that you want to provide to portal users.
# Provision the File Explorer channels to the domains, users, and/or roles as appropriate.
# Additionally, you may want to control what actions users can perform. These include a unique list when selecting on a folder versus a document. Actions you can restrict include the ability to delete and upload, or the ability to create sub-folders.

=== Channel Configuration ===

Configure the following parameters to control the behavior of each FileExplorer channel:

{| class="wikitable" border="1" style="background-color:#eeeeee;"
|+ align="bottom" style="color:#e76700;" |''FileExplorer Channel Parameters''
|-
! width="150" | Parameter Name
! width="150" | Description
! width="150" | Example
|-
| Object Type
| Type of object to explore
| <tt>pkgs</tt>
|-
| Object Type Filter
| Allows all object types when not specified, or only the comma-separated list of base types
| <tt></tt>
|-
| Context Type
| Indicates what type of explorer this is and what type of objects it explores
| <tt>portal</tt>
|-
| Explore Type
| Make the explorer function as either content listing and editing <Content> or as content object selection <Select>
| <tt>Content</tt>
|-
| Root Node
| The absolute reference of a node to be the root of the tree (optional). This will be appended to any system-level root node defined as the master directory location in <tt>pkg-edge.fileexplorer.properties</tt>.
| <tt>/httproot/custom</tt>
|-
| Root Node Label
| The label to be use for the specified root node, if it is too be displayed (optional)
| <tt>MyDocuments</tt>
|-
| Show Root Node
| Whether the root is to be displayed or not
| <tt>true</tt>
|-
| Expand On Load
| Whether root is to be expanded on channel load or not. This only applies if showRootNode is true
| <tt>false</tt>
|}

== File Explorer Actions ==

When a user right-clicks on a folder or file, certain actions are provided to allow for manipulation of the selected item. This section details how to customize the supported actions that are provided by the File Explorer.

=== Folder Actions ===

After installing the File Explorer PIM, the following folder actions are permitted by default:

* Delete
* Folder Detail
* New Subfolder
* Rename
* Upload

Perform the following steps to eliminate support for any of the above actions:

# Log in to enPortal as administrator
# Click on the Administration view
# Expand the folder Directory / system / .cmd / folder
# Right-click on the action to eliminate and select "Delete"

=== File Actions ===

After installing the File Explorer PIM, the following file actions are permitted by default:

* Copy
* Delete
* Download
* File Detail
* Rename
* View

Perform the following steps to eliminate support for any of the above actions:

# Log in to enPortal as administrator
# Click on the Administration view
# Expand the folder Directory / system / .cmd / file
# Right-click on the action to eliminate and select "Delete"

{{Tip|In many cases you might have access to log in to a customer's portal, but do not have physical access to the files on their server. If the customer installs the File Explorer PIM, they can configure it to give you access to some files on their server. This could be useful for viewing log files, for example, or XML customizations.}}