Destinations
From the EOM Console, you can define, modify, and remove destinations and destination groups. Destinations are used only for outbound data. They route files from Barr EOM to a physical destination, such as a laser printer, a host, or other locations on the LAN. Destinations can be organized into destination groups, which allow for easier monitoring from the EOM Console.
Destination groups are used to organize destinations in the Destination tree. Groups are represented as folders in the tree. From the EOM Console Destinations tree, you can create, move, rename, and delete destination groups.
From the Destinations tree, right-click a destination group (folder) and select New Group. A new group (folder) titled UnNamed is added to the selected destination group.
In the edit field, type the name of the new group and press ENTER. The new group automatically inherits the permissions of the parent group.
From the Destinations tree, select the destination group you want to move.
Use drag and drop functionality to place the group in the desired tree location. As you drag the item a yellow arrow will appear to the left of the tree to indicate where the group will be placed.
From the Destinations tree, right-click a destination group select Rename.
In the edit field, type the new group name and press ENTER. To cancel the rename, press ESC.
From the Destinations tree, right-click the destination you want to delete.
Select Delete from the menu. Groups that contain destinations or destination groups cannot be deleted. All of the objects must be removed before the group can be deleted.
Complete the following steps to add destinations to the Destinations application.
From the Destinations tree, select the destination group (folder) where you want to add destinations. Right-click and select New Destination. The Add Destination dialog box displays.
In the Type list, select the type of destination you want to create. You can select Email, EOM, FTP, IPDS, IPP, LPR, Network Folder, Socket, WebSphere MQ, and Windows Queue.
Next to Add new devices enter the number of destinations you want to create. You can create multiple destinations of the type selected and configure the destinations simultaneously.
Click OK. Tab pages will display with options specific to the selected destination type. The configuration options are shown differently depending if you chose to create a single destination or multiple destinations. When configuring one destination, individual options are listed on the tab pages. When configuring multiple destinations, the options are listed in grid format to allow for configuring multiple destinations simultaneously.
Make the necessary changes on each tab. For instructions specific to each destination type, review the following topics:
Click OK.
Complete the following steps to modify destinations in the Destinations application.
From the Destinations tree, right-click the destination you want to modify and select Configure. You can also right-click a destination in the grid view and select Configure. The dialog box that displays will vary depending on the type of destination selected.
From the Configuration dialog box, make the necessary changes.
Click OK.
Complete the following steps to remove destinations from the Destinations application.
From the Destinations tree, right-click the destination you want to delete.
Select Delete from the menu.
Use the following procedure to import a list of destinations into Barr EOM. This is particularly useful if you have a database, spreadsheet, etc. that lists your existing equipment. You can save that document as a .csv file and then import it to create matching destinations in Barr EOM.
Before you begin, review the following information on configuring/importing .csv files:
In the .csv file, the header record (first record) determines which fields are defined. You must configure the field names in the header record to match predefined Barr EOM names. Field names that match are used to populate the settings associated with that column. Field names that do not match are ignored. Contact Barr Systems Technical Support for the list of predefined Barr EOM names.
Each record after the header record is created as a device. The device will contain the settings from the recognized columns for that record. Barr EOM interprets values for text and numeric settings. For settings that have a fixed list of options, Barr EOM matches the value to the name of the option. Values which are not recognized, out of bounds, or otherwise invalid are replaced with the default value for that setting.
Not all settings can be specified through the .csv file. For example, the input/output server, users, destinations, and profiles cannot be imported.
A single .csv file can be used to generate multiple device types, sources, and destinations. Barr EOM only imports the settings which are recognized by the device type you are creating. For example, the .csv file can contain settings that are common to all devices types, settings for a particular device type, or settings for several different device types.
Complete the following steps to import destinations from a .csv file.
From the Destinations tree, right-click a destination group (folder) and select New Destination. The new destinations will be created in this group.
From the Add Destination dialog box, select the destination Type. The destination types available for import are Email, EOM, FTP, IPP LPR, Network Folder, Socket, WebSphere MQ, and Windows Queue. You cannot currently import IPDS destinations.
Select Import devices from configuration (.CSV) file.
In the box, enter the path and file name of the configuration file or click the Browse (...) button to navigate to the file.
When the configuration file is selected, click OK. Tab pages will display with options specific to the selected destination type.
Make the necessary changes on each tab. For instructions specific to each destination type, review the following topics:
Destinations can be set in a redirect mode. This causes new documents assigned to a destination to be automatically reassigned to a different destination.
For example, you can configure Destination A to reassign all received documents to Destination B. Documents already assigned to Destination A when the redirection occurs, will not be redirected. Documents received for Destination A while the redirection is in affect, will be assigned to Destination B. This includes Destination A being assigned by a source as a document is received, Destination A being assigned during business rule processing, and Destination A being assigned by failover processing. Destination assignments as a result of failover to Destination A will also be redirected to Destination B.
Complete the following steps to redirect a destination in the Destinations application.
From the Destinations tree or Destination grid, right-click the destination you want to redirect and select Destination Redirect. The Select Redirected Destination dialog box displays.
From the tree, select the destination you want to receive the redirected documents.
Configure the redirect by choosing one of the radio button options. You can select to redirect until manually turned off, redirect for a number of hours, redirect for a number of minutes, or redirect until a specific date and time. To disable redirect, select Do not redirect printer.
Click OK.
You can search for destinations from the Destinations tree and Destinations grid.
In the Search box below the tree, type the text you want to find and press ENTER or click the search button. If the text is found, your focus will be moved to the first occurrence. New buttons will appear near the Search box that allow you to move to the previous occurrence and move to the next occurrence.
In the search box below the grid, type the text you want to find, click the column in the grid you want to search, and press ENTER or click the Search image. If the text is found, your focus will be moved to the first occurrence. New buttons will appear near the Search box that allow you to stop searching, move to the previous occurrence, and move to the next occurrence.
EOM security for the Destinations application begins at the root of the Destinations tree, the All Destinations group. The Destinations tree consists of destinations and destination groups. A destination is an output from Barr EOM. A destination group is a way to organize destinations. EOM security is provided for both by adding a Microsoft Windows user or user group to the destination or destination group and assigning permissions to that user or user group. These EOM permissions define the type of access users and user groups have to the destinations and destination groups. Once the EOM security (Microsoft Windows users, user groups, and destination permissions) is set in a destination group, the EOM security is inherited by all the objects in that destination group. When a new destination or destination group is created, its security is automatically the same as its parent destination group’s security (that is, the new destination inherits its security from its parent destination group).
To begin configuring destination security, start by
assigning the desired destination permissions for the All Destinations
group. To view destinations in the tree, users or user groups must be
assigned the Allow user to view the Destination
permission in the All Destinations group. Users not assigned this permission
in the All Destinations group will not see any destinations or groups
even though they may have been given permissions for the specific destination
or group.
From the EOM Console, select the Destinations application in the navigation pane.
In the Destinations tree,
right-click a destination or destination group and select Security.
The Security Configuration
dialog box displays. To access this dialog box, you must be a member
of the local Administrators group or be assigned the Allow
user to modify the Destination’s security configuration permission.
Users with these rights can add and remove users or groups and modify
the assigned permissions. 
Use the Inherit permissions from the parent option to determine if you want to inherit permissions from a parent group or remove inheritance. By default, destinations are configured to inherit permissions from the parent folder. Click the Browse button to select a new parent group for inheritance or to remove inheritance.
It
is good practice to assign rights using inheritance, as it allows administrators
to easily assign and manage permissions. Blocking inheritance is useful
when a destination or destination group needs to be seen by just a few
users. If you plan to block inheritance, make sure the users that need
access to the blocked destination or group are in the security settings
for all of its parent groups, including All Destinations. If this is not
done then those users will not be able to see the destination. Also remember
to remove the users and user groups that should not have access to the
destination or group.
From the Users and groups with permissions list box, select the appropriate user or group in the list. The Assigned permissions list box will display the assigned permissions for the selected user.
If you want to set permissions for a user or group that
does not appear in the list, click Add.
From the User and Group
Selection dialog box, select the users/groups you want to add and
click OK. If the user/group is
not listed, click More Users to
locate the user. From the list you can choose to add EOM users, LDAP users,
or Windows users. You can also choose to import LDAP users. Once users
are added, they are placed in the EOM database, causing them to always
be listed in the future. See the Adding
users and groups to Barr EOM topic for detailed procedures on adding
users.
From the Assigned permissions box, select or clear the permissions for the selected user/group. Click Select All or Unselect All to easily assign or remove all permissions. The permissions assigned to a destination group will be inherited for all of the objects contained in that group, except for the ones that have inheritance blocked.
If you notice permissions that are selected and disabled, then the user/group selected has inherited permissions. Inherited permissions cannot be removed. To remove inherited permissions, you must first block inheritance for the destination.
Once all of your permission changes are complete, click OK.