Enterprise Software Technologies: Documentum & DataStage

Sequential File stages can use filter options to execute UNIX commands. Routine Activity can call routines that execute UNIX commands. Execute Command Activity is specifically designed for this purpose. Merge is purely a data combination stage with no capability to execute external UNIX commands.

In DataStage, when you configure a join stage without specifying the join type, it defaults to a Left Outer Join. This means all records from the left input link are included, and matching records from the right link are included where available. Equi-join requires exact matches on both sides, Full Outer includes all records from both sides, and Right Outer prioritizes the right input.

Hashed files use a hashing algorithm on key columns, which naturally eliminates duplicate records because identical keys produce the same hash value and overwrite previous entries. This automatic deduplication is a fundamental property of hash-based storage. The other options describe different DataStage operations not inherent to hashed files.

DataStage jobs run as operating system processes on the server. Consequently, system administrators can use standard UNIX commands like kill to terminate a running DataStage job process.

DataStage Manager is used for administrative tasks like project creation, user management, and environment configuration. Scheduling jobs and sequences is handled by DataStage Director or external scheduling tools. The Manager and Director serve different purposes in the DataStage architecture.

DataStage supports multiple instances of the same job running concurrently through its multi-instance configuration. This feature is crucial for parallel processing and workload distribution. Jobs can be configured to allow multiple instances with different invocation IDs to manage resource conflicts.

Local Containers in DataStage are specific to individual jobs and cannot be shared across jobs. Only Shared Containers can be reused across multiple jobs within a project. Local containers provide encapsulation within a single job, while Shared Containers enable reusability at the project level.

The DataStage Administrator role focuses on system-level management tasks including creating and deleting projects, managing users, and configuring system settings. Job design is done by developers, monitoring by operators, and import/export functions are available in Designer. The Administrator tool is specifically for project and user management.

The INTERPROCESS stage in DataStage is specifically designed for parallel jobs and handles inter-process communication between different processing partitions. It enables data exchange between parallel partitions in a parallel job. Server jobs use different mechanisms for data flow between stages.

When sorting in DataStage without specifying direction, the default sort order is ascending (lowest to highest). This is consistent with most sorting conventions in data processing tools. You must explicitly configure descending sort if you need reverse ordering.

DataStage Server edition processes data serially, with one record at a time passing through the pipeline. This contrasts with the Parallel edition which partitions data across multiple processors. Server edition jobs use a different architecture designed for single-threaded execution.

The @WHO system variable in DataStage returns the name of the current project directory, not the logged-in user name. This is useful for job logging and file path construction. To get user information, you would use different system variables like @USER or @LOGNAME.

In Documentum Web Publisher, the Web Developer role is responsible for creating the technical content that makes up web pages, including templates, presentation files, and the code structure. Content Authors create the actual content, Content Managers oversee the publishing workflow, and Administrators handle system configuration.

An edition in Documentum Web Publisher is a complete snapshot of a website at a specific point in time, stamped with date and time. It captures everything needed to replicate that exact state of the site and is stored in the edition cabinet in the repository. Editions capture all content (both active and inactive) to provide a complete historical record.

In Documentum Web Publisher, Presentation Files are the stylesheets used for formatting content files into the desired renditions for display on websites. Templates define structure, Rules control behavior, and Renditions are the output formats themselves. Presentation Files specifically handle the visual styling and formatting.

A folder map in Documentum Web Publisher is an XML file containing rules that place content files in specific locations in Web Cabinets based on file properties. The system evaluates folder maps whenever objects are created or properties change. When paths reference secondary folder maps, those secondary maps are evaluated before returning to the primary. The rules define the relationship between property values and repository paths.

In Documentum Web Publisher, an Instruction File determines which modifications to an XML template should be applied to existing XML content files. Rules Files control general behavior, Folder Maps handle content placement, and Presentation Files manage styling. The Instruction File specifically guides template-to-content transformations.

Site Caching Services stores copies of repository content on web servers, improving delivery performance and ensuring business continuity if the repository goes offline. It saves licenses because web clients access cached files without logging into the repository. User friendliness is a client-side interface property, not a caching benefit.

Documentum Webpublisher is the specific browser-based application designed for content creation, review, and publishing to websites. Webtop acts as a general document management client, WDK is the underlying web development kit framework, and Site Caching Services is responsible for content delivery and caching.

SCS (Site Creation Services) Source in Documentum is installed on the Content Server. The Content Server handles content storage, management, and the SCS services for web publishing. Application Servers handle client requests, and Database Servers store metadata, but SCS Source specifically runs on the Content Server.