SSSOOOAAAA

SOA stands for service oriented architecture. Before we define SOA lets first define a service. In real world service is what we pay for and we get the intended service. For instance you go to a hotel and order food. Your order first goes to the counter and then it goes to the kitchen where the food is prepared and finally the waiter serves the food.




Figure: - Hotel and services


So in order to order a item from a hotel you need the three logical departments / services to work together (counter, kitchen and waiter).

In the same manner in software world these services are termed as business services. They are self contained and logical. So let’s first define a business service, SOA definition will be just an extension of the same.

Definition of business service: - It’s a logical encapsulation of self contained business functionality.
For instance figure ‘order system’ shows a simple ordering system which is achieved by different services like payment gateway, stock system and delivery system coming together. All the services are self contained and logical. They are like black boxes. In short we do not need to understand the internal details of how the business service works. For the external world it’s just a black box which takes messages and serves accordingly. For instance the ‘payment gateway’ business service takes message ‘check credit’ and gives out output does the customer have credit or not. For the ‘order system’ business service ‘payment gateway’ service is a black box.



Figure: - Order system


Now let’s revise some bullet points of SOA before we arrive to a definition of SOA.

• SOA components are loosely coupled. When we say loosely coupled means every service is self contained and exist in alone logically. For instance we take the ‘payment gateway’ service and attach it to a different system.
• SOA services are black boxes. In SOA services hide there inner complexities. They only interact using messages and send services depending on those messages. By visualizing services as black boxes services become more loosely coupled.
• SOA service should be self defined: - SOA services should be able to define themselves.
• SOA Services are maintained in a listing: - SOA services are maintained in a central repository. Applications can search the services in the central repository and use them accordingly.
• SOA components can be orchestrated and linked to achieve a particular functionality. SOA services can be used/orchestrated in a plug and play manner. For instance figure ‘Orchestration’ shows two services ‘Security service’ and ‘Order processing service’. You can achieve two types of orchestrations from it one you can check the user first and then process order or vice-versa. Yes you guessed right using SOA we can manage work flow between services in a loosely coupled fashion.



Figure: - Orchestration

So lets define SOA.

SOA is a architecture for building business applications using loosely coupled services which act like black boxes and can be orchestrated to achieve a specific functionality by linking together.

BPEL

Oracle Service Bus

ADF (Application Development Framework)

Oracle ADF

SOA - Java - FAQs

(B) What is SOA?

SOA stands for service oriented architecture. Before we define SOA lets first define a service. In real world service is what we pay for and we get the intended service. For instance you go to a hotel and order food. Your order first goes to the counter and then it goes to the kitchen where the food is prepared and finally the waiter serves the food.

Figure: - Hotel and services

So in order to order a item from a hotel you need the three logical departments / services to work together (counter, kitchen and waiter).

In the same manner in software world these services are termed as business services. They are self contained and logical. So let’s first define a business service, SOA definition will be just an extension of the same.

Definition of business service: - It’s a logical encapsulation of self contained business functionality.
For instance figure ‘order system’ shows a simple ordering system which is achieved by different services like payment gateway, stock system and delivery system coming together. All the services are self contained and logical. They are like black boxes. In short we do not need to understand the internal details of how the business service works. For the external world it’s just a black box which takes messages and serves accordingly. For instance the ‘payment gateway’ business service takes message ‘check credit’ and gives out output does the customer have credit or not. For the ‘order system’ business service ‘payment gateway’ service is a black box.

Figure: - Order system

Now let’s revise some bullet points of SOA before we arrive to a definition of SOA.

• SOA components are loosely coupled. When we say loosely coupled means every service is self contained and exist in alone logically. For instance we take the ‘payment gateway’ service and attach it to a different system.
• SOA services are black boxes. In SOA services hide there inner complexities. They only interact using messages and send services depending on those messages. By visualizing services as black boxes services become more loosely coupled.
• SOA service should be self defined: - SOA services should be able to define themselves.
• SOA Services are maintained in a listing: - SOA services are maintained in a central repository. Applications can search the services in the central repository and use them accordingly.
• SOA components can be orchestrated and linked to achieve a particular functionality. SOA services can be used/orchestrated in a plug and play manner. For instance figure ‘Orchestration’ shows two services ‘Security service’ and ‘Order processing service’. You can achieve two types of orchestrations from it one you can check the user first and then process order or vice-versa. Yes you guessed right using SOA we can manage work flow between services in a loosely coupled fashion.

Figure: - Orchestration

So lets define SOA.

SOA is a architecture for building business applications using loosely coupled services which act like black boxes and can be orchestrated to achieve a specific functionality by linking together.

(I) In SOA do we need to build systems from scratch?

No. If you need to integrate or make an existing system as a business service, you just need to create loosely coupled wrappers which will wrap your custom systems and expose the systems functionality in generic fashion to the external world.

(I) Can you explain business layers and plumbing layers in SOA?

In SOA we can divide any architecture in two layers. The first which has direct relevance to business as it carries out business functions. The second layer is a technical layer which talks about managing computer resources like database, web server etc. This division is needed to identify a service. Consider the figure ‘Simple order system’. It has various components which interact with each other to complete the order system functionality.

Figure: - Simple order System

The simple order system can be divided in to two layers (see figure ‘business and plumbing layer’ one which is business related and second which is more technical related. You can see the plumbing layer consisting of data access layer , AJAX , yes more of technical stuff.

Figure: - Business layer and plumbing layer

(I) what’s the difference between services and components?

Services are logical grouping of components to achieve business functionality. Components are implementation approaches to make a service. The components can be in JAVA, C#, C++ but the services will be exposed in a general format like Web Services.

(A) Can you describe the complete architecture of SOA?

Figure ‘Architecture of SOA’ shows a complete view of a SOA. Please note this architecture diagram is not tied up with implementation of Microsoft, IBM etc. It’s a general architecture. Any vendor who implements SOA needs to fulfill the below SOA components. How they do it is completely their own technological implementation.

Figure: - Architecture of SOA

The main goal of SOA is to connect disparate systems. In order that these disparate system work they should messages to each other. ESB (Enterprise service bus) acts like a reliable post office which guarantees delivery of messages between systems in a loosely coupled manner. ESB is a special layer which delivers messages between applications. In the figure we have shown a huge plump pipe. It’s not hardware or some wire etc. It’s a group of components/software which helps you to send and receive messages between the disparate applications. Do not try to code your own ESB, you can think of buying one from Microsoft, IBM, Oracle, progress etc.

SOA registry is like a reference database of services. It describes what each services do, where are they located and how can they communicate. It’s a central reference of meta-data for services.

SOA workflow allows us to define work flow using the services in SOA registry. We will read more about BPM in the further questions.

Service broker reads the work flow and takes services from the SOA registry and ties them together. Service brokers are normally middleware like EAI (Enterprise application Integration) products. You can get a list of decent EAI from Sun, Microsoft, and IBM etc.

Process manager is nothing but the collection of SOA registry, SOA workflow and service broker.

SOA supervisor is traffic cop ensuring that services do not have issues. It deals mainly with performance issues of the system so that appropriate service levels are met. If any of the services have performance problems it sends messages to the proper infrastructure to fix the issue.

Note: - The above explanation is of general architecture for SOA. Any vendor (Microsoft, IBM, SUN etc) who gives solution for SOA should have the above components in some or other manner. As this is a Software architecture book, we will not be covering specific vendor implementation. We would advise the reader to map the same to their vendor products for better understanding.

(I) Can you explain a practical example in SOA?

(I) What are ends, contract, address, and bindings?

These three terminologies on which SOA service stands. Every service must expose one or more ends by which the service can be available to the client. End consists of three important things where, what and how:-

• Contract (What)
Contract is an agreement between two or more parties. It defines the protocol how client should communicate with your service. Technically, it describes parameters and return values for a method.
• Address (Where)
An Address indicates where we can find this service. Address is a URL, which points to the location of the service.
• Binding (How)
Bindings determine how this end can be accessed. It determines how communications is done. For instance, you expose your service, which can be accessed using SOAP over HTTP or BINARY over TCP. So for each of these communications medium two bindings will be created.

Below figure, show the three main components of end. You can see the stock ticker is the service class, which has an end hosted on www.soa.com with HTTP and TCP binding support and using Stock Ticker interface type.

Figure: - Endpoint Architecture

Note: - You can also remember the end point by ABC where A stands for Address, B for bindings and C for Contract.

(I) Are web-services SOA ?

SOA is a thinking, it’s an architectural concept and web service is one of the technical approach to complete it. Web services are the preferred standards to achieve SOA.

• In SOA we need the services to be loosely coupled. A web service communicates using SOAP protocol which is XML based which is very loosely coupled. It answers the what part of the service.
• SOA services should be able to describe themselves.WSDL describes how we can access the service.
• SOA services are located in a directory.UDDI describes where we can get the web service. This nothing but implementation of SOA registry.

Product Hub

Oracle Product Hub is a market-leading solution, providing customers with tools to centralize all product information from heterogeneous systems, creating a single product repository that can be leveraged across all functional departments. This proven and innovative solution provides capabilities to match, merge and consolidate multiple sources, governance and data quality tools* to securely and collaboratively manage data within the hub and integration services to share content across the enterprise and with trading partners.

Oracle Product Hub provides a number of options to meet specific customer needs:
• Oracle Product Hub Data Steward provides a set of tools for data stewards, product managers or catalog managers to easily administer, govern and maintain data within the hub; for other users who simply need to search, view, request or approve new items / changes to items, Oracle Product Hub provides the capabilities for unlimited users to address these needs

• Oracle Product Data Quality is an integrated, best-in-class data quality solution built on the latest semantic technology to handle the extreme variability of product data. It provides the capability to recognize, cleanse, match, validate and correct product data within the Oracle Product Hub repository or as data is loaded through import processes

BENEFITS
• Focus on product data consolidation and quality
• Improve visibility of information across the extended enterprise
• Lower data management costs
• Improve collaboration across and beyond the enterprise
• Accelerate new product introductions and changes
• Establish foundation for cross-application processes


FEATURES
• UI based extensibility for the entire system
• Out-of-the-box support for Enterprise Product Record
• Proven, scalable industry data-models
• Integrated best-in-class product data quality solution
• Unlimited, extensible attribution to meet the needs of the enterprise
• Unstructured data management for images, datasheets, and word documents etc.
• Multi-hierarchy support
• Easy definition of product / service offers & bundles
• Manage relationships of items to other entities, such as suppliers & locations
• Inheritance framework to easily generate & maintain parent-child item relationships
• Exception-based item induction and change workflow
• Configurable mass data updates
• Template-based publishing and reporting solution
• Granular role-based security
• Fast, flexible product search
• Rich set of web services and APIs
• Data import workbench for managing data staging processes
• Publication workbench to streamline publishing of data and metadata from the hub.

WebSphere Application Server WAS

WebSphere tools

Java - Information

Abstract class Vs. Interface                AJAX - Information                       Ant
Client-Server Programming               Concurrency (Multi-threading) - Information                CORBA
Core Java - Dev book - Info               Core Java - Information           Cruise Control          CSS
DB2                Design Patterns 
EJB                EJB 2.0 vs 3.0
Facelets (JSF)
Hibernate                Hibernate - n+1 select problem                 Hudson 
iBatis
JavaScript
JAX-WS 
JBoss
JBoss - WebServices 
JDBC 
JMS 
jQuery
JSF - Information
JSP - Information
JUnit
Linux
Maven
Messaging - Java
MVC (Struts) 
Oracle - Information
Oracle Service Bus
Performance Tuning Tips 
PL/SQL  
PostgresSQL
Quartz
RESTful
RMI
SAX vs DOM
SEAM (JBOSS) - FAQs 
Servlets - Information
Shale framework
SOA - Java - FAQs  
SOAP
SoapUI Testing
Spring - Information
Spring Inversion of Control and Dependency Injection
Spring MVC - Example
Spring Transaction Management
Struts 
TDD
Tiles
Tomcat
UML 
WebLogic
WebLogic Scripting Tool
WebServices - Information
WSAD 
WSDL
XML
XPath
XSD
XSL & XSLT

Nodes

A node is a point within a hierarchy. Every point in a hierarchy is a node. For example, within a hierarchy that represents an organizational structure, a node might represent a department or a cost center.
Within a version, a node may be a part of more than one hierarchy. A node can have many user- defined properties that store information about the node and control the use of the node within the information systems of an organization.
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
The following terms are used to define the position of a node and behavior of the node within a hierarchy:
About Nodes    13
Table 1
Node Terminology
l
l
Create a new node Insert an existing node not currently in the hierarchy - See
Term
Leaf
Limb
Child
Parent
Descendant
Ancestor
Sibling
Orphan
Definition
A node that cannot have children
A node that can have children
A node directly below another node (if B is directly below A, B is a child of A)
The node directly above another node (in the previous example, A is the parent of B)
A node below a specified node (including children and children of children)
All nodes between a node and the top of the hierarchy (including the parent, the parent of the parent, and so on)
All nodes that share a parent node in a hierarchy
A node not assigned to a hierarchy
Adding and Inserting Nodes
You can include a node in a hierarchy in two ways:
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
ä    To create a node and add it to a hierarchy: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select New. 6    Optional: Select Leaf Node if the node is a leaf. 7    Enter a name and description for the node.
14    Working with Nodes
Note:    If you are adding a node to a part of the hierarchy tree that has repeated node names, you can click ID to automatically generate a node name. See ID Function.
8    Select whether to add the node as a child or sibling of the selected node. 9    Click OK.
ä    To insert an existing node into a hierarchy: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select Insert. 6    Select the location of the node:
l
l
Existing Hierarchy
Orphan Node List
7    Do one of the following:
l
If you selected Existing Hierarchy in step 6, do the following: a.    Select a hierarchy. b.    Select the node to insert by doing one of the following:
m
m
Enter text in Find and click    to locate the node.
Note:    You can use the asterisk ( * ) as a wildcard character.
Expanding the Nodes tree to locate the node.
8    Select whether to insert the node as a child or sibling of the selected node. 9    Click OK.
ID Function
The ID function enables you to automatically generate node names using sequential numerical IDs and node prefixes. For example, a set of nodes can be created where each of them have a name like Org000xxx, where:
l
l
Org is the node prefix and can be any desired character string. 000xxx is the sequential ID and increments by 1 starting at 1.
These system preferences must be enabled for the ID function to work:
l
l
AllowNextIDGeneration must be set to True. AllowNextIDKeyCreation determines the level of user that can create new ID keys.
Adding and Inserting Nodes    15
To use the Next ID function, type a prefix in the node name field and click ID.
l    If the prefix already exists in the system, then an ID value is returned that is one greater than the last ID previously generated.
l    If the prefix has not been used before, then an ID value of 1 (with the appropriate number of leading zeros) is returned.
The total length of the ID (excluding the prefix and including any leading zeros as necessary) is determined as follows:
l    The hierarchy properties IDLengthLimbProp and IDLengthLeafProp can be set to point to node-level properties that specify the desired ID length for the specified node.
l    If the IDLengthLimbProp and IDLengthLeafProp properties are not set, then the length of the next sequential ID is used without leading zeros.
Modeling a Node
You can create a node by modeling an existing node.
ä    To create a node by modeling a node: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node to model. 5    On the Shortcuts menu, select Script and then select Model After.
The Source tab is populated with information from the node you selected.
6    On the Properties tab, from Copy Properties, select the properties to be copied from the node. l    None - No properties are copied. l    Defined - Only defined property values are copied. l    Selected - Only the properties you select are copied.
Note:    For Selected, click    to display a property selector from which to select properties.
l    All - all properties are copied. 7    Do the following:
l
Select the Global Properties tab to view the Global property values that will be included in the Action Script based on your selection in Step 4.
16    Working with Nodes
l
Select the Local Properties tab and select a hierarchy to view the local property values that will be included from each hierarchy based on your selection in Step 4. Make changes as necessary.
8    On the Target tab, do the following: l    Select the target version for the new node. l    Enter a name for the new node. l    Enter a description for the new node.
9    Click Load. 10 When the load completes, review the script actions and parameter values. You can:
l    Click    to modify a row. l    Select Script, then Substitute Versions to change a version. Select the version to be
replaced and the version to replace it with and click OK. l    Double-click a column header to sort rows alphabetically.
l    Click    to filter one or more columns. 11 Select the check box in the Process column next to each row to be run.
Note:    From the Script menu, use Select All to process all actions. You can select a subset of actions from a script and only process those actions.
12 Click    to run the Action Script. The results of each script action are displayed in the Status and Result Value columns. The
script and the results can be saved to a file using the Download option on the Script menu.
Moving and Ordering Nodes
You can move a node within a hierarchy or to a different hierarchy:
l    Moving a node within a hierarchy removes the node from its original parent and places it under the new parent.
l    Moving a node to a different hierarchy is treated like a copy. The node is left unchanged in its original hierarchy. This function is identical to inserting an existing node.
ä    To move a node: 1    Select the node to move. 2    Drag and drop the selected node to the new location. 3    If you moved the node under a different top node, select an action:
l
l
Put as Child - To insert the node as a child of the node. Put as Sibling or Reorder - To insert the node as a sibling.
Moving and Ordering Nodes    17
Relaxed Move Option
To facilitate a move that requires a node to be removed from an alternate hierarchy, you can use the Relaxed Move option. If the System Preference AllowRelaxedMove is set to True, the Relaxed Move is allowed. If the system preference is set to False or does not exist, then the normal integrity constraints are enforced.
When moving a node, the Relaxed Move enables the new parent in the main hierarchy to take precedence over any conflicting parental relationships for this node in other hierarchies.
Sorting Nodes
In Data Relationship Management, nodes are sorted according to the following default rules:
1.    Limb nodes are sorted before leaf nodes. (This is optional and controlled by the SortLimbsFirst system preference.)
2.    Nodes are sorted by name in ascending order.
Custom Sort Order
Nodes can also be sorted in any explicit custom sort order. The sort order can be defined by any property that has a property data type of Sort.
To sort a hierarchy according to the value of a node-level sort order property, the hierarchy- level property StandardHierSort must be set to point to the appropriate node-level property that contains the sort order.
A custom sort order can also be used that applies only to a specific Data Relationship Management user ID, enabling users to customize their display of Data Relationship Management data without impacting other users of the same hierarchy. This is controlled by the hierarchy-level property UserHierSort. If this property has been set to point to a node-level property that has a data type of Sort Order, then this sort order takes precedence over both the StandardHierSort property and the default sort order.
If there is no value assigned to the hierarchy-level property StandardHierSort nor to UserHierSort, then default sorting rules are used.
The value of a custom sort order property can be set in any of the following ways:
l    Sort order values can be loaded into a node-level sort order property when data is initially imported into Data Relationship Management (see following for details.)
l    Explicit values can be defined for the sort order property for any node.
l    If a sort order property has been selected for a hierarchy’s StandardHierSort or UserHierSort properties, use the Take/Put options or drag and drop to custom order nodes within a hierarchy.
l    A node-level sort order property might be defined as Derived, and so might be automatically populated with a sort order.
18    Working with Nodes
Node Deletion Methods
There are four methods of deleting nodes described in decreasing order of severity in the following table.
Table 2    Node Deletion Methods
Action
Delete
Remove
Annul
Inactivate
Result
Removes the node from all hierarchies and deletes the node from the version
Removes the node from the current hierarchy and any other hierarchies where it has the same parent. However, the node is not deleted from the version and is available for re-insertion.
Performs a Remove on the node in all hierarchies where it has the same parent, and also Deletes the node if it is then an orphan:
Note:
If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node. If the ReqMerge system preference is enabled, then you must specify a merge node. If ReqMerge is not enabled, then a merge node is optional unless the node approved property is TRUE. The node approved property is set to TRUE when a version is finalized or when it is specifically set to TRUE by a user with appropriate access.
l
l
For example, if a node has the same parent in all hierarchies in which it exists, then an Annul will remove the node from all hierarchies and then delete it because it is an orphan.
If the node does not have the same parent in all hierarchies, Annul produces the same result as Remove.
Flags the node as inactive so that it can be filtered from an export.
Deleting Nodes Note:    Only nodes without descendents can be deleted.
To delete multiple nodes from a hierarchy, use the Annul All Below command.
ä    To delete a node: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select Delete.
Node Deletion Methods    19
6    Select Delete Node to confirm node deletion. When the version tree refreshes, the node is no longer displayed. Deleting a node removes it from all hierarchies and parents in the selected version.
Merging Nodes
When you delete or inactivate nodes, you can specify nodes for Data Relationship Management to use in place of the deleted or inactivated nodes. External transaction systems supported by Data Relationship Management may have transactions that refer to a deleted node. By keeping a merge list, Data Relationship Management is able to provide appropriate node mappings that allow data to a rolled to a valid node.
Note:    The merge options (Delete & Merge and Inactivate & Merge) are available only if the UseMerge system preference is enabled.
Removing Nodes
Removing a node removes it only from the current parent. If the node has other parents, those relationships are not affected. If the node has no other parents, it becomes an orphan node.
ä    To remove a node: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select Remove. 6    Select Remove Node to confirm node removal.
When the version tree refreshes, the node is no longer displayed. If the node had no other parents, it becomes an orphan node.
Annulling Nodes
When you annul a node, the node is removed from the parent, and, if it becomes an orphan, the orphan node is deleted. For example, if a node has only one parent, then Annul results in the node being deleted.
You can use the Annul All Below command to annul multiple nodes.
ä
1
To annul a node:
From Browse, select a version.
20
Working with Nodes
2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select an action:
l
l
Annul - To annul the selected node Annul All Below - To annul all nodes below the selected node
Note:    This option is available only if you select a limb node. 6    Select Annul Node.
When the version tree refreshes, the node is no longer displayed. You can use the Annul All Below command to annul multiple nodes.
Inactivating Nodes
You can inactivate leaf nodes or limb nodes that have no active children.
The Inactivate and InactiveChanges system preferences control which users can inactivate a node and make changes to inactive nodes.
ä    To inactivate a node: 1    From Browse, select a version. 2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select a node. 5    From Nodes, select Inactivate.
Note:    If the UseMerge system preference is enabled, you can select Inactivate & Merge, then select a node to use in place of the inactivated node.
When the version tree refreshes, the node is grayed out and displays an inactive status icon.
Reactivating Nodes
ä    To reactivate a node: 1    From Browse, select a version.
Node Deletion Methods    21
2    Select a hierarchy. 3    From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4    Select an inactive node. 5    From Nodes, select Reactivate.
When the version tree refreshes, the node is displayed.
Orphan Nodes
An orphan node is defined as a node that exists in a version but is not assigned to a hierarchy within the version. Orphans may exist pending a cleanup to completely remove them, or they may be awaiting re-allocation to hierarchies in the version.
It is possible for an orphan node to have descendants that are not orphans. To avoid this, review the list of orphan nodes regularly.
Viewing Orphan Nodes
ä    To view orphan nodes: 1    Select the Orphans tab.
For each orphan node, the number of descendants is displayed.
2    Select a node. 3    Perform an action:
l    Select Related and then Descendants or Children to view a node's relationships. l    Select Node and then Properties to view a node's properties.
l    Click    to search for an orphan node by name, description, or number of descendants.
l    Select Node and then Take/Copy to copy the selected node to the clipboard.
l    Select Download and then choose a format in which to download the list of orphan nodes.
Deleting Orphan Nodes
You can delete or destroy orphan nodes. If you select destroy, the node is deleted immediately regardless of any merge requirements.
Note:    Nodes with children can only be removed, not deleted.
22    Working with Nodes
ä    To delete orphan nodes: 1    Select the Orphans tab. 2    Select one or more nodes. 3    From Node, select Delete or Destroy.
Note:    If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node.
4    Confirm the Delete or Destroy command. When the orphan list refreshes, the node is no longer displayed.
Finding Nodes
You can search for nodes within a hierarchy or a version.
ä    To find a node in a version: 1    From Browse, select a version. 2    Select Find Nodes.
3    Click    and select By Name or By Description. 4    Enter text for which to search.
Note:    You can use the asterisk ( * ) as a wildcard character.
ä    To find a node in a hierarchy: 1    From Browse, select a version. 2    Select a hierarchy, then select Hierarchies, then Open. 3    Select Find Nodes.
4    Click    and select By Name or By Description. 5    Enter text for which to search.
Note:    You can use the asterisk ( * ) as a wildcard character.
Node Security
You can be assigned different levels of access to nodes within and across hierarchies. The Limb and Leaf Access properties for a node indicate your level of access. Node security settings can only be assigned by a Data Relationship Management user with administrative privileges.
Finding Nodes    23
Using Shared Nodes
Shared nodes are multiple instances of a node within the same hierarchy. Explicitly shared nodes, created during manual maintenance and import processes, share global property values with the primary node. The global properties for shared nodes automatically reference the values of the primary node and can only be changed at the primary node. Local properties can be specific to each shared node.
You can: l    Automate the alternate naming of the shared nodes
l    Create system-level properties that map shared nodes l    Display the structure below a shared node l    Move between shared nodes and the primary node l    Remove and delete primary shared nodes
l    Rename the primary shared node (thus renaming all the shared nodes) l    Find and display a shared node list to be used for navigation and analysis purposes
Shared Node Properties
The following read-only, node properties are created automatically when a node is shared and provide information about primary and shared nodes
Note:    The Shared Info property category must be manually assigned to users in order to see the shared node properties.
Property
Primary Node
Shared Node
Primary Node
Primary Node
Primary Node
Primary Node
Shared Map
Name
Has Descendants
Descendants
Ancestors
Description
Indicates whether a node has shared nodes that point to it
Indicates whether the node is a shared node
The primary name portion of the shared node name. For non-shared nodes, this property returns the node name in its entirety.
Indicates whether the primary node has structure below it. Only populated on shared nodes.
List of descendants of the primary node. Only populated on shared nodes where the primary node has structure below it.
List of ancestors of the primary node. Only populated on shared nodes.
Associated nodes property that maps the shared and primary nodes. This property is populated for shared and primary nodes.
Indicates whether the shared node points to a primary node that does not exist
Indicates whether the primary node is not in the same hierarchy
Missing Primary Node
Primary Not in Hierarchy
24    Working with Nodes
Enabling Shared Nodes
To use shared nodes in an application, you must enable the SharedNodeMaintenanceEnabled system preference. For any hierarchy in which you want to share nodes, you must enable the EnableSharedNodes hierarchy property. These settings are disabled by default.
Note:    If shared nodes are enabled, the default shared node system preferences (delimiter, unique string, zero-pad length) should not be changed.
For information on configuring system preferences, see the Oracle Hyperion Data Relationship Management Administrator's Guide.
Adding and Inserting Shared Nodes
You can use the add or insert menu options to create a shared node. You can create a Shared Node by doing a Take/Put across Hierarchies, when the Node already exists in the target Hierarchy. You can accomplish the same thing by performing a drag/drop across two Hierarchies in a side-by-side Compare result.
Note:    Before creating a shared node, make sure you have completed Enabling Shared Nodes.
ä    To add a shared node: 1    Select the node where you want to insert a shared node. 2    From Nodes, select Add. 3    If the shared node is a leaf, select Leaf Node. 4    Enter the name of the existing node that you want to add. 5    Select If Node already exists, Insert the Node. 6    For Add As, select Child or Sibling. 7    Click OK.
ä    To insert a shared node: 1    Select the node where you want to insert a shared node. 2    From Nodes, select Insert. 3    For Insert From, make sure that Existing Hierarchy is selected. 4    Select a hierarchy. 5    From the Nodes list, select the node to share. 6    For Insert As, select Child or Sibling. 7    Click OK.
Using Shared Nodes    25
In this example, node ABC is a primary node under Node1 and a shared node under Node2.
Removing and Deleting Shared Nodes
When you remove a shared node, the system removes the shared node only and the primary node remains. If the primary node is removed and a shared node also exists, the shared node is removed and the primary is moved to the parent of the shared node that was removed. If multiple shared nodes exist, one of the shared nodes becomes the primary node.
When you delete a shared node, the system deletes the shared node and all of its shared nodes.
ä    To remove or delete a shared node: 1    Select a shared node. 2    From Nodes select Delete or Remove. 3    Select Delete Node or Remove Node.
When the hierarchy tree refreshes, the shared nodes are no longer displayed.
Renaming Shared Nodes
When you rename a primary node, the system renames the primary node and the shared nodes. Only the primary node can be renamed. The secondary shared nodes cannot be renamed.
ä    To rename a shared node: 1    Select the primary node. 2    In the property editor, select the Name value field. 3    Change the name and click Save.
When the hierarchy refreshes, the primary node name and the shared node names are updated with the new name.
Converting a Shared Node into a Primary Node
ä    To convert a shared node to a primary node: 1    Select the shared node. 2    From Nodes, select Convert to Primary.
26    Working with Nodes
ä
1 2
To display shared nodes:
Select a node. From Related, select Shared Nodes. Primary and shared nodes are displayed on the Relationships tab.

Imports in DRM

Using Data Relationship Management, you can import data extracted from external systems or manually created by users using a multi-section, text file format. Imports are always performed on new, empty versions created as part of the import process. This approach allows you to verify that data was imported correctly and resolve any issues before saving the data to the database or merging with data in other versions. After you verify the data, you can use the blender to combine imported data with data originating from other sources.
Any Data Relationship Management user authorized to run imports can customize and save.
Caution!
When running imports, the regional settings of your client session are used to define the expected format for date and time values that are being imported. If these settings are not detected, then the regional settings for the server are used. For example, if the regional setting for your session specifies that date should be formatted as dd.mm.yyyy, then the data given to the import should be in that format. Otherwise, the information does not display or displays incorrectly.


Import Elements
An import consists of the elements in the following table.
Table 9 Import Structure
Import Element
Import
Sections
Description
Attributes of the import, such as version, error-handling settings, and file names
Information about the import, such as hierarchy, node, and relationship (Configuring a section can include designating section headers and delimiters.)
Import Elements 85
Import Element
Columns
Description
Data attributes to be imported (An Import Column is mapped to a corresponding non-read-only property in Data Relationship Management, such as name and description. Configuring a column involves selecting a property to populate, ordering the column, and sometimes mapping the column to a set of hierarchies. If the input format is a fixed-width text file, the column width should also be configured.)


Import Sections
An import can contain any or all of the following sections:
Table 10 Import Sections
Import Section
Version
Hierarchy
Node
Relationship
Hierarchy Node
Description
Version property values
Required column: Version Name
Structural information about each hierarchy and top node to be imported and, perhaps, hierarchy property values.
Required columns: Hier Name, Top Node
Structural information about each node to be imported and, perhaps, node property values
Required column: Node
Parent-child information about each relationship to be imported and, perhaps, node property values for the child in each pair.
Required columns: Parent Node Name, Node
Node values specific to a specified hierarchy
Required columns: HierName, Node
Creating Imports
When you create or open an import, it is displayed on a named tab.
The import wizard is used to define the parameters and criteria for the import. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä To create an import: 1 From the Data Relationship Management navigation bar, select Import.
2 Click . 3 On the Source tab, select the import source from the Device list.
l
If you selected Client File, click Browse and navigate to and select the import file.
86 Working with Imports
If you selected Server File, select the connection and a file name. 4 Select File Format options:
l Character Encoding — UTF8, ANSI, ASCII, UTF16BE, UTF16LE. l Strip Quoted Strings — Select to remove quotation marks during data import.
Note: Single ( ' ) and double quotation marks ( “ ) are removed. If both types of quotation marks are used at the same time, only the outer set of quotations is stripped.
l Fixed Width or Delimited — For Delimited, enter the delimiter character. For Fixed Width, enter fixed width column values in Columns Options of the Columns tab.
5 Select from the following Section Headings options: l Prefix Delimiter — A character that is displayed at the beginning of a section heading,
such as /, /**, or [.
l Suffix Delimiter — A character that is displayed at the end of a section heading, such as /, /**, or [. The delimiter suffix is optional.
l Select section headings that are in the import source and enter text for the section heading.
Note: All import sections are selected by default. Uncheck sections that are not in the import source.
6 Select the Style tab and choose Relationship Sorting options:
l Sort Relationships — Select to enable the import to sort the nodes based on the order in which they are displayed in the relationship section of the source file, and complete both of the following actions:
l
m
m
Sort Property to Populate — Select the node property in which to store the sort order.
Hierarchy to be Sorted — Select the hierarchies to which to apply the sort.
l Determine Leaf Nodes at the End of Import Process — Select to specify that, at the end of the import process, the import automatically sets the leaf property to True for any node that has no children.
Note: This option requires a second pass of the imported data and may require additional time to process. If this option is not selected, all nodes will be imported as limb nodes unless the Leaf property is specified as a column in the Node or Relationship section of the imported data.
7 Select Duplicate Handling options:
l
Append Unique Text to the End of the Node Name — Select to append the unique portion of the name to the end of the original node name.



Creating Imports 87
8
9
On the Columns tab, from the Section list, select a file section. From the Available list on the Select Columns tab, select the columns for the import.
Note: Use the Category list to select a property category to ease navigation. A special column called Ignore Column is available as a placeholder for any column in the
input source that should not be processed during the import.
Tip: Use the arrows to position the column in the Selected list. The first item in the list is the first column, the second item in the list is the second column, and so on.
88
Working with Imports
Note: If you select this option, use the Unique String, Delimiter, Unique ID Seed, and Zero Pad Length parameters to create a naming convention for duplicate nodes. The unique portion of the name is added to the end of the original node name. If not selected, the unique portion of the name is prefixed to the beginning. For example, 001NodeA, 002NodeA.
l Unique String — Enter a string to be used to form part of the new unique node name. l Delimiter — Enter a delimiter character to be used to separate the original node name
from the unique portion of the name. l Unique ID Seed — Select a starting point for this ID.
For example, if NodeA occurs three times in a hierarchy and the unique ID seed is 1, the original node is not changed, and the other node names are replaced with NodeA1 and NodeA2. This example ignores the other Duplicate settings in order to illustrate the use of unique ID seed.
l Zero-Pad Length — Enter the minimum number of digits required in the unique ID portion of the duplicate name.
For example, a value of 3 for zero-pad length creates duplicate nodes named NodeA001, NodeA002, and so on. A value of 2 creates duplicate nodes named NodeA01, NodeA02, and so on.
l Associated Property — Select a property to enable duplicate nodes to be grouped so they can be easily queried after the import is complete.
If an associated property is set, the property is populated with the node name of the original node in all duplicate nodes. This option must refer to a global, associated node property.
l Duplicate Error Mode — Select a mode to determine the severity with which the import processor treats a duplicate:
m
m
Generate Warning — Warning message is added to the log for each duplicate. Generate Error — Error message is added to the log for each duplicate.
Note: Processing stops if the number of errors exceeds the Max Errors value (on Target tab).
10 On the Column Options tab, you can map a column to hierarchies. Double-click a column name row and select from these options:
l Select Apply Value to All Hiers if values in the column should be applied to all hierarchies. By default, this option is selected.
l In the Hierarchy Listing field, enter the name of each hierarchy to which the column applies. The property value is set only in the hierarchies designated in the list.
Note: The listed hierarchies must match the names of hierarchies specified in the import source.
l If you selected Fixed Width on the Source tab, enter a value in the Fixed Width column. 11 On the Filter tab, make selections to skip blank and use defaults for certain property types.
Note: It is recommended to skip blank and use default values to minimize the size of the imported version.
12 On the Target tab, enter a name and, optionally, a description for the new version that will be created by the import.
13 Select a value for the maximum number of errors that can occur during processing before the import stops.
Note: The recommended maximum number of errors is 20. 14 Do either or both of the following:
l
l
Click to save the import. Click to run the import.



Running, Copying, and Deleting Imports
You can run, copy, and delete imports. You must open an import before you can run it. ä To run an import:
1 On the Import tab, select an import. 2 Click . 3 Click the tabs to modify import parameters, and then click to run the import.
ä To copy an import: 1 On the Import tab, an import. 2 From Imports, select Copy. 3 Enter a new name and description for the import.
Running, Copying, and Deleting Imports 89
4 From Object Access Level, select User, Standard, or System (depending on your user role) and click OK.
ä To delete an import: 1 On the Import tab, select an import. 2 From Imports, select Delete.

Exports in DRM

Data Relationship Management allows you to export information in a variety of formats to meet the different needs of each system and user. From the Export task on the Home page, you can create, open, and manage exports and books. You can open multiple exports in separate tabs, but only one export can be in focus at a time. You can also run exports from a selected data object being browsed.

Creating Exports
Data Relationship Management provides several export types to output data in different formats. The following table lists the export types for Data Relationship Management.
Note:    Some clients may have more classes if they have custom export classes for their specific implementation.
Export Type
Hierarchy Export
Hierarchy Export XML
Generation Export
Compare Export
Output Formats
File, Database Table
File
File
File, Database Table
Description
Usage Frequency
Outputs a record for each node and its properties for hierarchies. This export can be used to create a parent-child type format or a basic list of hierarchy nodes.
High
Outputs nodes, their relationships, and properties from hierarchies in an XML format.
High
Creates a generation- or level-based format for nodes in hierarchies. Outputs a record for each node, its ancestor nodes, and their properties. This export type can be used to create a format where hierarchy relationships are represented as columns.
Medium
Compares two hierarchies and outputs a record for each node that met the comparison criteria. This export can be used to provide incremental changes to target systems.
Medium
Creating Exports    59
Description
Usage Frequency
Compares two hierarchies and outputs a record for each difference found. This export can be used for reporting incremental changes to users.
Low
Outputs a record for each node and its properties for an entire version. Hierarchy relationships and local properties are not available for this export type.
Medium
Outputs a record for each item in the list of values for a property definition. This is a special use case export type.
Low
Outputs a record for each key-value pair in the lookup table for a property definition. This is a special use case export type.
Low
Outputs a record for each item in the transaction log that met the filter criteria. This export can be used for audit purposes.
Medium
Outputs a record for each item in the merge log that met the filter criteria. This export is only applicable if the Merge feature is used.
Low
Export Type
Difference Export
Version Export
Property List Export
Property Lookup Export
Transaction Log Export
Merge Export


Creating Hierarchy Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a hierarchy export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Hierarchy as the export type. 4    Select the Source tab and select a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    Click Add and select top nodes. Use the arrows to reposition the top nodes, which determine the export column order.
6    Select the Style tab and choose options: l    Node Selection — Determines which node types (All Nodes, Limb Nodes Only, Leaf
Nodes Only) are included in the export
l    Recurse from Top Node — Select to include output for all nodes below the top node. If cleared, only the top node is included (which is typically not the desired result).
l    Include Inactive Nodes — Select to include inactive nodes in the export.
Output Formats
File
File, Database Table
File
File
File, Database Table
File
60    Working with Exports
l    Include Implicitly Shared Nodes — Select to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are exported only if not filtered out by another option.
m    If a query filter is used in the export, the administrator must explicitly include the shared nodes. For example, the filter (#Children=0) must be changed to ((#Children=0 OR (Shared Node Flag = True)).
m    For the implicitly shared node, Parent properties reflect the values of the actual node (the primary node). For example, if your export includes the Parent Node property for an implicitly shared node, it will show the parent as the primary node.
l    Remove Duplicates Based on Key — Select to use the primary key (defined on the Column Options tab) to suppress.
l    Tabbed Output — Select to indent the nodes for each level of a hierarchy using tab characters to produce a structured output format.
7    In the Repeat Parameters section, choose options:
l    Repeat Number Property — References a local, node-level, integer property that repeats a node within an export structure. For example, given an A-B-C parent-child hierarchy, if a Repeat Num Property has a value of 2 for node B and a value of 1 for nodes A and C, then the export looks like A,B,B,C (node B is repeated twice).
Note:    When using Repeat Number Property , the value must be set to at least 1 for nodes to be included in the export results. Setting the Repeat Number Property default value to 1 is recommended.
l    Bottom Level Property and Bottom Level Value — Determines the maximum depth of the export structure. This value can be defined as a hierarchy-level, integer property (Bottom Level Property) or as an absolute value (Bottom Level Value.)
If a bottom level is defined, the repeat options are enabled to automatically repeat nodes down to the defined level in the export structure. For example, for nodes A-B-C in a parent-child hierarchy, if the Bottom Level Value is defined as 6, node B has a Repeat Number Property value of 2, and the Repeat Bottom Node option is selected, then the export structure is A,B,B,C,C,C (the export structure is six levels deep, the leaf node C is repeated until level 6 is reached, and node B is repeated twice).
8    Select the Filter tab and select from these options: l    From Validation, select a validation to use to filter the export.
l    From Query, select a query to apply to the export or, to define a query, click    .
l    Use text file to include/exclude descendant nodes — Select if you have created a text file with nodes to be included or excluded from the export. The file format is a list of node names with one per line. Select a connection, enter a file name, and select whether to include or exclude the nodes from the export.
9    Select the Columns tab and from the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Creating Exports    61
Note:    Use the Category list to select a property category to ease navigation. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
10 Select the Column Options tab, and choose options:
11 12
l    Pivot — If the field contains a comma-delimited value then, for each value in the list for that column, a row is exported with all other fields set to the same values. The Pivot option may be selected on one column.
l    Skip Defaults — To place a blank in the export if the field value equals the default value of the property
l    Primary Key — To define a field (or fields) as the primary key to be used when determining whether duplicates exist. (This is also used by the Remove Duplicates option on the Style tab).
Select the Target tab and choose where to export the results: Client File, Database Table, or Server File. Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export.
m    Quoted Strings — Puts quotation marks around strings in the export.
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE.
m    Replace options — Select up to three characters from the lists to be replaced. All instances in the export are replaced as specified. For example, all commas can be replaced by tabs.
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character.
l    If you selected to export to a Database Table, you must set your connection and select the database table. You can also select from these options:
62
Working with Exports
m
Clear table options
o    Do Not Clear Table — Appends to data in the specified table.
o    Clear Based on Version ID(s) — deletes data in the table where the specified key field equals the current version ID of the data being exported. If this option is selected, a Key field must be specified in the Database Column Options section. When the export is run, all data in the table is first deleted where the
l
l
Click    to save the export. Click    to run the export.
o
Key field equals the current version ID of the data being exported. For the other Clear Table options, the Key field is ignored.
Clear All Rows — Deletes data from the table before writing the export output.
m    Use Transactions — The export is performed within a database transaction and allows the entire operation to be rolled back if an export error occurs.
m    Use Fast Appends — Performs a bulk insert operation into the target database table for improved export performance. Only available with a database-specific connection.
m    Database Column Options — Each column being exported must be mapped to a field in the external database table. Under Field Name, select the name of a field. If you selected Clear Based on Version ID(s), specify a Key field.
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
13 Do either or both of the following:
Creating Hierarchy XML Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
Creating Exports    63
ä    To create a hierarchy XML export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Hierarchy XML as the export type. 4    On the Source tab, select a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    Click Add and select top nodes. Use the arrows to reposition the top nodes, which determine the export column order.
6    Select the Style tab, and choose options: l    Node Selection — Determines which node types (All Nodes, Limb Nodes Only, Leaf
Nodes Only) are included in the export
l    Recurse from Top Node — Select to include output for all nodes below the top node. If cleared, only the top node is included in the export (which is typically not the desired result).
l    Include Inactive Nodes — Select to include inactive nodes in the export. 7    Select the Filter tab and select from these options:
l    From Validation, select a validation to apply to the export. l    From Query, select a query to apply to the export or, to define a query, click    .
l    Use text file to include/exclude descendant nodes — Select if you have created a text file with nodes to be included or excluded from the export. The file format is a list of node names with one per line. Select a connection, enter a file name, and select whether to include or exclude the nodes from the export.
8    Select the Columns tab and from the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Note:    Use the Category list to select a property category to make navigation of the Available list easier.
Tip:    Use the arrows to position the column in the Selected list. The first item in the list is the first column, the second item in the list is the second column, and so on.
9    Select the Target tab and choose where to export the results: Client File or Server File. 10 Perform an action:
l    If you selected to export to a Client File, go to the next step. l    If you selected to export to a Server File, you must set your connection and enter a file
name.
11 Do either or both of the following:
64    Working with Exports
l
l
Click    to save the export. Click    to run the export.
Creating Generation Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a generation export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Generation as the export type. 4    On the Source tab, select a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    Click Add and select top nodes. Use the arrows to reposition the top nodes, which determine the export column order.
6    On the Style tab, select from these options: l    Node Selection — Determines which node types (All Nodes, Limb Nodes Only, Leaf
Nodes Only) are included
l    Recurse from Top Node — Select to include output for all nodes below the top node. If this option is not selected, then only the selected top node is (which is typically not the desired result).
l    Include Inactive Nodes — Select to include inactive nodes.
l    Include Implicitly Shared Nodes — Select to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are only exported if not filtered out by another option such as top node selection or a property query filter. The structure of implicitly shared nodes below a shared parent node is reflected in the ancestor section of the hierarchy export.
m    If a query filter is used in the export, the administrator must explicitly include the shared nodes. For example, the filter (#Children=0) must be changed to ((#Children=0 OR (Shared Node Flag = True)).
m    For the implicitly shared node, the Parent properties reflect the values of the actual node (the primary node). For example, if your export includes the Parent Node property for an implicitly shared node, it will show the parent as the primary node.
Creating Exports    65
l
Root to Node — Select to set the export order (if not selected, the order is Node to Root.) For example, if node A is a parent to node B and this option is selected, then the output is A,B. Otherwise, with this box unchecked, it is B,A.
7    From Repeat Parameters, select from these options:
l    Repeat Number Property — references a local, node-level, integer property that repeats a node within an export structure. For example, given an A-B-C parent-child hierarchy, if a Repeat Num Property has a value of 2 for node B and a value of 1 for nodes A and C, then the export looks like A,B,B,C (node B is repeated twice).
Note:    When using Repeat Number Property , the value must be set to at least 1 for nodes to be included in the export results. Setting the Repeat Number Property default value to 1 is recommended.
l    Bottom Level Property and Bottom Level Value — determine the maximum depth of the export structure. This value can be defined as a hierarchy-level, integer property (Bottom Level Property) or as an absolute value (Bottom Level Value.)
If a bottom level is defined, repeat options are enabled to automatically repeat nodes down to the defined level in the export structure. For example, for nodes A-B-C in a parent-child hierarchy, if the Bottom Level Value is defined as 6, node B has a Repeat Number Property value of 2, and the Repeat Bottom Node option is selected, then the export structure is A,B,B,C,C,C (the export structure is six levels deep, the leaf node C is repeated until level 6 is reached, and node B is repeated twice).
8    From Ancestor Options section, select from these options: l    Max Ancestor Levels — Defines the maximum number of ancestor levels in the export
structure.
l    Use Inverted Levels — The Oracle Essbase level methodology is used where the leaves are at 0 and count up. For a node that has multiple branches under it, the node is the largest of the possible values.
l    Blank Repeated Levels — Prevents repeated nodes from appearing in the output. If cleared, a node may be repeated in the output to achieve the specified level.
l    Group Repeated Columns — Repeated columns are grouped property in the ancestor columns.
9    Select the Filter tab and choose options: l    From Validation, select a validation to apply to the export.
l    From Query, select a query to apply to the export or, to define a query, click    . Note:    The inclusion filter determines the set of nodes to include in the results. The
exclusion filter restricts the nodes displayed as ancestor columns.
l    Use text file to include/exclude descendant nodes — Select if you have created a text file with nodes to be included or excluded from the export. The file format is a list of node names with one per line. Select a connection, enter a file name, and select whether to include or exclude the nodes from the export.
66    Working with Exports
10 On the Columns tab, from the Column Set list, select one of the following options: l    Pre Columns — properties to export at the beginning of each row l    Bottom Node Columns — properties for the specified bottom node l    Ancestor Columns — node properties for the ancestor list of the specified bottom node l    Post Columns — properties to export at the end of each row
11    From the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Note:    Use the Category list to select a property category to make navigation of the Available list easier.
Tip:    Use the arrows to position the column in the Selected list. The first item in the list is the first column, the second item in the list is the second column, and so on.
12 Select the Column Options tab and choose options:
l    Pivot — If the field contains a comma-delimited value, for each value in the list for that column, a row is exported with all other fields set to the same values. The Pivot option may be selected on one column.
l    Skip Defaults — To place a blank in the export if the field value equals the default value of the property
l    Primary Key — To define a field (or fields) as the primary key to be used when determining whether duplicates exist. This is also used by the Remove Duplicates option on the Style tab.
13 Select the Target tab and choose where to export the results: Client File or Server File. 14 Perform an action:
l    If you selected to export to a Client File, choose options: m    Column Headings — Includes column headings in the export m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
Creating Exports    67
l
l
Click    to save the export. Click    to run the export.
m
Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
15 Do either or both of the following:
Creating Compare Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a compare export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click    . 3    Select Compare as the export type. 4    Select the Source tab and select versions, hierarchies, and top nodes to compare.
Note:    You must select a top node for the current and previous versions.
68    Working with Exports
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    Select the Style tab and select from these options: l    Node Selection — Determines node types (All Nodes, Limb Nodes Only, Leaf Nodes
Only) included in the export
l    Join Property — By default, compares map nodes from each hierarchy that have the same name. You can also join nodes based on other properties. For example, if a property named SortCode has a unique key in the specified hierarchies, then this property is used to identify differences between nodes having the same SortCode in each hierarchy.
l    Additions — Includes all nodes in the target (to) hierarchy that are not in the source (from) hierarchy.
l    Deletions — Includes all nodes in the source (from) hierarchy that are not in the target (to) hierarchy.
l    Merges — Includes merge information in the export (if the merge feature is enabled.) l    Moves — Includes all nodes that have different parent nodes in the compared
hierarchies.
l    Renames — Includes all nodes that have different names but the same internal NodeID in the compared hierarchies.
l    Property Updates — Includes all nodes that have different values in the specified list of properties in the compared hierarchies. Select Edit to choose properties.
6    Select the Filter tab and choose options: l    From Validation, select a validation to apply to the export.
l    From Query, select a query to apply to the export or, to define a query, click    . Note:    The inclusion filter determines the set of nodes from each hierarchy to be
compared. The exclusion filter excludes nodes from export results.
7    On the Columns tab, from the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Note:    Use the Category list to select a property category to ease navigation. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
8    Select the Column Options tab and choose options:
l    Pivot — If the field contains a comma-delimited value, for each value in the list for that column, a row is exported with all other fields set to the same values. The Pivot option may be selected on one column.
l    Skip Defaults — To place a blank in the export if the field value equals the default value of the property
Creating Exports    69
l
Primary Key — To define a field (or fields) as the primary key to be used when determining if duplicates exist
9    On the Target tab, from the Device list, select where to export the results: Client File, Database Table, or Server File.
10 Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Database Table, you must set your connection and select the database table. You can also select from these options:
m    Clear table options
o    Do Not Clear Table — Appends to data in the specified table.
o    Clear Based on Version ID(s) — deletes data in the table where the specified key field equals the current version ID of the data being exported. If this option is selected, a Key field must be specified in the Database Column Options section. When the export is run, all data in the table is first deleted where the Key field equals the current version ID of the data being exported. For the other Clear Table options, the Key field is ignored.
o    Clear All Rows — Deletes data from the table before writing the export output. m    Use Transactions — The export is performed within a database transaction and
allows the entire operation to be rolled back if an export error occurs.
m    Use Fast Appends — Performs a bulk insert operation into the target database table for improved export performance. Only available with a database-specific connection.
m    Database Column Options — Each column being exported must be mapped to a field in the external database table. Under Field Name, select the name of a field. If you selected Clear Based on Version ID(s), specify a Key field.
70
Working with Exports
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
11 Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.
Creating Difference Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a difference export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Difference as the export type. 4    On the Source tab, select versions, hierarchies, and top nodes for which you want to export differences.
Note:    You must select a top node for the current and previous versions.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
Creating Exports    71
5    On the Style tab, select from these options: l    Node Selection — Determines which node types (All Nodes, Limb Nodes Only, Leaf
Nodes Only) are included in the export
l    Join Property — By default, compares map nodes from each hierarchy that have the same name. You can also join nodes based on other properties. For example, if a property named SortCode has a unique key in the specified hierarchies, then this property is used to identify differences between nodes having the same SortCode in each hierarchy.
l    Include Summary — Includes summary of differences in the export result. l    Additions — Includes all nodes in the target (to) hierarchy that are not in the source
(from) hierarchy.
l    Deletions — Includes all nodes in the source (from) hierarchy that are not in the target (to) hierarchy.
l    Merges — Includes merge information in the export (if the merge feature is enabled.) l    Moves — Includes all nodes that have different parent nodes in the compared
hierarchies.
l    Renames — Includes all nodes that have different names but the same internal NodeID in the compared hierarchies.
l    Property Updates — Includes all nodes that have different values in the specified list of properties in the compared hierarchies. Click Edit to select properties.
6    Select the Filter tab and choose options: l    From Validation, select a validation to apply to the export.
l    From Query, select a query to apply to the export or, to define a query, click    . Note:    The inclusion filter determines the set of nodes from each hierarchy to be
compared.
7    On the Columns tab, from the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Note:    Use the Category list to select a property category to ease navigation. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
8    Select the Column Options tab and choose options:
l    Pivot — If the field contains a comma-delimited value, for each value in the list for that column, a row is exported with all other fields set to the same values. The Pivot option may be selected on one column.
l    Skip Defaults — To place a blank in the export if the field value equals the default value of the property
72    Working with Exports
l
Primary Key — To define a field (or fields) as the primary key to be used when determining if duplicates exist
9    On the Target tab, from the Device list, select where to export the results: Client File or Server File. 10 Perform an action:
l    If you selected to export to a Client File, choose options: m    Column Headings — Includes column headings in the export. m    Quoted Strings — Puts quotation marks around strings in the export.
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE.
m    Replace options — Select up to three characters from the lists to be replaced. All instances in the export are replaced as specified. For example, all commas can be replaced by tabs.
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character.
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
11 Do either or both of the following:
Creating Exports    73
l
l
Click    to save the export. Click    to run the export.
Creating Version Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a version export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Version as the export type. 4    Select the Source tab and choose a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    Select the Style tab and choose options: l    Node Selection — Determines which types of nodes (All Nodes, Limb Nodes Only, Leaf
Nodes Only) are included in the export
l    Include Implicitly Shared Nodes — Select to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are exported only if not filtered out by another option such as top node selection or a property query filter. The structure of implicitly shared nodes below a shared parent node is reflected in the ancestor section of the hierarchy export.
m    If a query filter is used in the export, the administrator must explicitly include the shared nodes. For example, the filter (#Children=0) must be changed to ((#Children=0 OR (Shared Node Flag = True)).
m    For the implicitly shared node, the Parent properties reflect the values of the actual node (the primary node). For example, if your export includes the Parent Node property for an implicitly shared node, it will show the parent as the primary node.
6    Select the Filter tab and choose options: l    From Validation, select a validation to apply to the export.
l    From Query, select a query to apply to the export or, to define a query, click    . Note:    The inclusion filter determines the set of nodes from each hierarchy that will be
compared.
74    Working with Exports
7    On the Columns tab, from the Available list, select the properties to display as columns in the export results by moving them to the Selected list.
Note:    Use the Category list to select a property category to ease navigation. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
8    On the Target tab, from the Device list, select where to export the results: Client File, Database Table, or Server File.
9    Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Database Table, you must set your connection and select the database table. You can also select from these options:
m    Clear table options
o    Do Not Clear Table — Appends to data in the specified table.
o    Clear Based on Version ID(s) — deletes data in the table where the specified key field equals the current version ID of the data being exported. If this option is selected, a Key field must be specified in the Database Column Options section. When the export is run, all data in the table is first deleted where the Key field equals the current version ID of the data being exported. For the other Clear Table options, the Key field is ignored.
o    Clear All Rows — Deletes data from the table before writing the export output.
m    Use Transactions — The export is performed within a database transaction and allows the entire operation to be rolled back if an export error occurs.
Creating Exports    75
m    Use Fast Appends — Performs a bulk insert operation into the target database table for improved export performance. Only available with a database-specific connection.
m    Database Column Options — Each column being exported must be mapped to a field in the external database table. Under Field Name, select the name of a field. If you selected Clear Based on Version ID(s), specify a Key field.
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
10 Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.
Creating Property List Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä
1
2 3
To create a property list export:
From the Data Relationship Management navigation bar, select Export. Click    .
Select Property List as the export type.
76
Working with Exports
4    Select the Source tab and choose a version. You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal
versions. To select a Baseline or As-Of version, click Normal under the Version list.
Note:    Even though the results are not filtered by version, for this release you must select a version.
5    From the Available list, select a property upon which to base the export. 6    Select the Target tab and choose where to export the results: Client File or Server File. 7    Perform an action:
l    If you selected to export to a Client File, choose options:
m
m
Quoted Strings — Puts quotation marks around strings
Column Headings — Includes column headings
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m
m
Quoted Strings — Puts quotation marks around strings
Column Headings — Includes column headings
8    Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.
Creating Property Lookup Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Style, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a property lookup export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Property Lookup as the export type. 4    Select the Source tab and choose a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
Note:    Even though the results are not filtered by version, for this release you must select a version.
Creating Exports    77
5    From the Available list, select a property upon which to base the export. 6    Optional: Select the Style tab, and choose Differences Only to filter out lookup pairs where the Lookup
Key and Result Value are the same. 7    Select the Columns tab and choose the columns for the export.
Only two columns are available because the Lookup Key and the Result Value are the only relevant columns for this export type.
Tip:    Use the arrows to position the column in the Selected list. The first item in the list is the first column, the second item in the list is the second column, and so on.
8    On the Target tab, from the Device list, select the location to which you want to export the results: Client File or Server File.
9    Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
78    Working with Exports
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
10 Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.
Creating Transaction Log Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a transaction log export: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select Transaction Log as the export type. 4    Select the Source tab and choose a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
Note:    You can also select the Run Export for All Versions option.
5    To select hierarchies and nodes for the export, click    . 6    Select the Filter tab and choose options:
l    Levels — Click l    Actions — Click l    Properties — Click l    Users — Click
to specify levels. to specify transaction log action types.
to specify a list of properties. to specify users.
Creating Exports    79
l    Include Child Nodes — Select to include child nodes.
l    Include Shared Nodes — Select to include shared nodes
l    From/To Date — Select to specify a date range
l    From/To Transaction — Select to specify a range of transaction IDs.
l    Filter to Current Session — Filter transactions to those performed during the current session.
7    On the Columns tab, select the columns for the export. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
8    On the Target tab, from the Device list, select the location to which you want to export the results: Client File Database Table, or Server File.
9    Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Database Table, you must set your connection and select the database table. You can also select from these options:
m
Clear table options
o    Do Not Clear Table — Appends to data in the specified table.
o    Clear Based on Version ID(s) — deletes data in the table where the specified key field equals the current version ID of the data being exported. If this option is selected, a Key field must be specified in the Database Column Options section. When the export is run, all data in the table is first deleted where the Key field equals the current version ID of the data being exported. For the other Clear Table options, the Key field is ignored.
80    Working with Exports
Clear All Rows — Deletes data from the table before writing the export output.
m    Use Transactions — The export is performed within a database transaction and allows the entire operation to be rolled back if an export error occurs.
m    Use Fast Appends — Performs a bulk insert operation into the target database table for improved export performance. Only available with a database-specific connection.
m    Database Column Options — Each column being exported must be mapped to a field in the external database table. Under Field Name, select the name of a field. If you selected Clear Based on Version ID(s), specify a Key field.
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m    Column Headings — Includes column headings
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
10 Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.
o
Creating Merge Log Exports
When you create or open an export, it is displayed on a named tab.
The export wizard is used to define the parameters and criteria for the export. The wizard content is organized across Source, Filters, Columns, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a merge log export: 1    From the Data Relationship Management navigation bar, select Export.
Creating Exports    81
2    Click . 3    Select Merge Log as the export type. 4    On the Source tab, select a version.
You can select Normal, Baseline, or As-Of versions. The Version list defaults to the Normal versions. To select a Baseline or As-Of version, click Normal under the Version list.
5    On the Filter tab, select from these options: l    Begin/End Dates — Set the beginning and ending date for the export l    Deleted Node — Enter name of deleted nodes.
l    Merge Node — Click    to specify a merge node l    User — Select a user l    Status — Select a status
6    On the Columns tab, select the columns for the export. Tip:    Use the arrows to position the column in the Selected list. The first item in the list is
the first column, the second item in the list is the second column, and so on.
7    On the Target tab, from the Device list, select the location to which you want to export the results: Client File or Server File.
8    Perform an action: l    If you selected to export to a Client File, choose options:
m    Column Headings — Includes column headings in the export
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
l    If you selected to export to a Server File, you must set your connection and enter a file name. You can also select from these options:
m
Column Headings — Includes column headings
82    Working with Exports
9
m    Quoted Strings — Puts quotation marks around strings
m    Fixed Width — Allows you to specify field widths, left or right justification for the column, and number of pad characters. You can enter column information in the Fixed Width Option section.
m    Character Encoding — To export the results as UTF8, ANSI, ASCII, UTF16BE, UTF16LE
m    Replace options — Select up to three characters from the lists to be replaced. For example, commas can be replaced by tabs
m    Header/Footer — Add a line between the header/footer and the body or enter text to be printed on the header and footer of the export results. Enter lines of text into
the text box or click    to open a text editor.
m    Delimiter options — To select a field delimiter character and a record delimiter character
Do either or both of the following:
l
l
Click    to save the export. Click    to run the export.



Creating Export Books
Saved exports can be grouped and run together in Export Books. This enables a set of commonly used exports to be executed with one action rather than individually.
Note:    Book exports cannot reference multiple versions. All exports for a book must reference the same version.
ä    To create an export book: 1    From the Data Relationship Management navigation bar, select Export.
2    Click . 3    Select the Source tab and choose a version from which to select exports for the book.
Note:    All exports for a book must reference the same version. 4    From Object Access, select an access type for the book: User, Standard or System. 5    Select exports from the Available list and move them to the Selected list to include them in the book.
Note:    You can use the Export Type list to filter the list of available exports.
6    Optional: If the output is to be combined, select the Target tab, select Combine Export Output and specify the device (combined file), connection and file names.
Creating Export Books    83
Pre File and Post File can be used to specify data that is prepended and appended to the combined output file.
Note:    When a book contains both exports configured to output to a file and some configured to output to a database table, the Combine option affects only the exports that are writing to files.
7    Click    to save the export book.

Running, Copying, and Deleting Exports
You can run, copy, and delete exports. You must open an export before you can run it. ä    To run an export:
1    On the Export tab, select an export. 2    Click . 3    Click the tabs to modify the export parameters, and then click    to run the export.
ä    To copy an export:
1    On the Export tab, select an export.
2    From Exports select Copy.
3    Enter a new name and description for the export.
4    From Object Access Level, select User, Standard, or System (depending on the role of the user) and click OK.
ä    To delete an export: 1    On the Export tab, select an export. 2    From Exports, select Delete.