To create a Distribution using the Desktop Application type:
In ConsoleOne®, right-click the container where you want the Distribution object located > click New > click Object > select TED Distribution > click OK.
Enter a name for the Distribution.
IMPORTANT: Periods (.) are not allowed in Distribution names. Instead, use dashes (-) or underscores (_) as word separators. If you use a period in the Distribution name, the Distribution will not be sent, and the Distributor will not reload after it has been exited.
To give a Distributor ownership of the Distribution, browse and select the Distributor object > click Define Additional Properties > click OK.
The Distribution object's properties are displayed.
Click the General tab > fill in the Settings fields:
Active: Required. In order to make a Distribution available to Subscribers, it needs to be active.
Use Digests: Digests are used by Distributors and Subscribers to verify that Distributions have not been tampered with while in transit. The digest provides a checksum for the Subscriber to compare.
Encrypt: You can have the Distribution encrypted if you will be sending it across non-secured connections. Encryption provides security for the Distribution during transit between the Distributor and Subscriber. Select between Strong and Weak encryption. Encryption is not available for Linux* or Solaris* servers.
Maximum Revisions: This number helps you to control disk space usage by determining how many versions of a particular Distribution are kept in the Distributors' and Subscribers' working directories. The default is 10. Increase the number if data is changing often and the changes are minimal (smaller delta files). Decrease the number if data is not changing very often, or if a significant amount of data is changing (larger delta files). If you select 1, the Delete Previous Revision field will be checked.
Delete Previous Revision Before Receiving Next: This option is available if you selected 1 as the number for the Maximum Revisions field. If the Distribution is so large that it might compromise the available disk space on the Subscriber server, you can conserve disk space by checking this option, which will cause the previous version to be deleted before receiving the next version. If you leave the check box empty, the new version will be received in its entirety before the older version is deleted. Either way, you will have only the one version of the Distribution in the Subscriber's working directory after the Distribution has been received.
Priority: You can give the Distribution a priority that determines how it will be sent in relation to other Distributions. A High priority means it will be sent before Medium or Low priority Distributions.
Distributor: Displays the DN of the Distributor object that will build and send this Distribution. You selected the Distributor when you created the object.
Description: Enter useful details about the Distribution, such as the name of the desktop application, the files and directories it contains, intended user groups, and so on.
Click the General tab > click Restrictions.
You can select whether to have platform restrictions for the Distribution.
No Restrictions: This option is checked by default. To determine platform restrictions, click this radio button to disable it > click the check boxes corresponding to the platforms you want to receive this Distribution.
Platforms where their check boxes are not checked cannot receive the Distribution. In other words, you restrict sending to a platform by disabling the No Restrictions option and not selecting the platform.
The available options are:
No Restrictions
NetWare All
NetWare 4.x (ZfS 2)
NetWare 5.0 (ZfS 2)
NetWare 5.1
NetWare 5.x
NetWare 6.x
Windows Server
Solaris
Linux
No Restrictions means that the Distribution can be sent to any platform.
If you select NetWare All, you do not need to select any of the individual NetWare® platforms.
Click the Type tab > in the Select Type drop-down box, select Desktop Application > click Setup.
The Desktop Application Distribution Wizard is started.
Click Next after reading the Introduction information.
Fill in the fields > click Next.
Maintain Source Tree Structure: Duplicates the source tree's structure at the destination's location (the target Subscriber's working context) for placing the ZfD application objects. If you will be selecting chained applications, you must check this option.
Maintain Associations: Maintains the associations established in the source tree between the distributed applications and the trusted user/workstation groups and containers. This is done by replicating the associated groups or containers at the target location if they do not exist. However, users or workstations contained in the groups or containers in the source location are not replicated.
Source Root Container: Select a container to be used as the root container for the ZfD application objects to be distributed. You should only select application objects from this root container and its subordinate containers.
Load Balance and Fault Tolerance Support: Choose whether to use automated load balancing, fault tolerance, or neither. Load Balance automates spreading server workloads over the servers being used for the Desktop Application Distributions, and the functionality of fault tolerance is automatically accomplished through load balancing. Fault Tolerance allows a server being used for Desktop Application Distributions to assume the distribution duties of another server that has gone down. Fault Tolerance does not include load balancing. Select None to manually configure each application object for load balancing or fault tolerance.
Click Add to browse for and select ZfD application objects > click Next.
Do not browse above the root directory that you established in the previous wizard page, especially if you have checked the Maintain Source Tree Structure option.
IMPORTANT: The Desktop Application source files must reside in the Distributor server's file system. The Distribution cannot be gathered from another server's file system.
Enter the destination volume or shared folder.
The application files distributed are those that are associated with the application objects you selected in the previous wizard page.
You can enter a variable instead. If you use a variable, it must be defined in the destination Subscriber server's properties to point to the target server's volume or shared folder.
This volume or shared folder becomes the root location for placing subordinate directories where the application files will be copied.
To use only an application's default path, click Default Application Directory Path, which will be placed beginning with the root location you specified in Step 6.d.
or
To enter a user-defined directory path to the application's files, click User-Defined Directory Path > enter your path information.
The path you specify is used in the following manner:
The result is a customized directory path that begins with the volume or shared folder, has your user-defined path information next, and ends with the application's immediate directory. For example, the default path to the application's executable file (APPLICATION.EXE) might be:
Application_Root_Directory\Application_Subdirectory
and you enter MyPath for your user-defined path, the new full path to the executable will now be:
C:\MyPath\Application_Subdirectory\APPLICATION.EXE
where you entered C: as the shared folder, MyPath as your user-defined path, Application_Root_Directory is replaced by MyPath, and Application_Subdirectory is the immediate parent directory to the executable, APPLICATION.EXE.
Click Next to continue.
The Summary page is displayed.
To make changes, click Back.
When you have finished configuring the Distribution object, click Finish.
You can edit the Distribution at any time on the Type tab of the Distribution object by clicking Modify.
Click the Channels tab > click Add > browse for and select the Channel for this Distribution.
Each Distribution must be associated with at least one Channel if it is going to be used to push data to a Subscriber. A Distribution will be sent to all Subscribers that are subscribed to the selected Channel.
Click the Schedule tab > select a Build schedule:
Click Apply to create the Distribution.
You will be prompted to copy additional security certificates.
Click Yes to resolve the certificates.
This will copy the security certificates from the Distributor to Subscriber that is subscribed to the Channel.
Click OK to close the Distribution object.
The next time the Distributor reads eDirectory (this schedule is set in the Distributor object's properties), it will retrieve all of the information about the new Desktop Application Distribution, such as Distribution details, the Build schedule, and so on.
The Distribution will be built according to the Build schedule, sent according to the schedule set in the Channel object, and extracted according to schedule set in the Subscriber object.
After extraction, ZfD users associated with that Subscriber server will have access to the desktop applications that were distributed.