Package com.crystaldecisions.sdk.plugin.desktop.program

This package enables you to add non-BusinessObjects Enterprise objects into the BusinessObjects Enterprise Infrastructure.

See:
Description

Interface Summary

IBinaryProgram	This object provides functionality which allows you to use a binary program within the BusinessObjects Enterprise framework.
IJavaProgram	This object provides functionality which allows you to use a Java program within the BusinessObjects Enterprise framework.
IProgram	This interface provides the functionality necessary for creating a program object and adding it to the BusinessObjects Enterprise framework.
IProgram.CeProgramType	This interface defines possible values for the program type.
IProgramBase	This interface is implemented by schedulable Java programs that have been published to BusinessObjects Enterprise.
IProgramBaseEx	Extended interface for schedulable Java programs to implement.
IProgramGlobal	This interface is used to set what type of program object is available for deployment.
IProgramPluginBase	This interface allows you to define what types of program objects you want to manage within the BusinessObjects Enterprise Infrastructure.
IScriptProgram	This interface provides functionality which allows you to use a script program within the BusinessObjects Enterprise framework.

Package com.crystaldecisions.sdk.plugin.desktop.program Description

This package enables you to add non-BusinessObjects Enterprise objects into the BusinessObjects Enterprise Infrastructure. These non-BusinessObjects Enterprise objects are classified as program objects. The three main types of program objects are: Binary, Java, and Script Programs. In addition, you have the ability to take advantage of the BusinessObjects Enterprise scheduling engine and security features to manage and define administrative responsibilities regarding program objects, such as viewing rights and scheduling tasks.

Note: The following information is important to consider when working with the Program plugin.

• Script Engine Dependencies

When you create a script or program to run on a machine it may require other dependencies like a script engine (perl) or a java virtual machine. Therefore, these dependencies must be installed on the appropriate machines. Furthermore, these engines need to be configured outside of BusinessObjects Enterprise and be accessed using shell programs.

• Binary Compatibility

Binary programs are compiled for a specific type of hardware. Thus, if a Program Job Server is running on Windows then the binary programs need to be compiled for the appropriate operating system. If the program is compiled for UNIX and run on windows it will fail. Therefore, it is imperative that a program object is assigned to the correct Program Job Server.

• End of Line (EOL) characters

When a text file is created on UNIX it creates EOL characters that when opened in a Windows text editor causes the file to appear as one string. Similarly, when a text file is created on Windows there are extra carriage return characters which a UNIX text editor displays. This limitation is OS platform specific and you need to plan for how to deliver each.

• Malicious user concern

The ability to run program objects on the Program Job Server opens up the potential for many malicious viruses causing severe damage to the BusinessObjects Enterprise Infrastructure. Thus, in order to prevent harm, the use of impersonation is always required for Binary and Script programs. Impersonation is a type of delegation which allows a program to run using limited rights.

Java Programs use policy files and impersonation (impersonation is optional for Java programs) to minimize the risk of a security violation. A policy file allows an administrator to set customized rights and restrictions for a Java program. For more information see IProgramGlobal interface.

• Performance

Any programs/scripts or Auxiliary files will be stored in the File Repository Server (FRS) and copied to the machine at schedule time. If the files are large then this can be a time consuming operation and consume a lot of network bandwidth. For large files it is best to create a program object that references the batch file (which is stored in the FRS) and create an ‘external dependency’ to the program.