AB INITIO SOFTWARE LLC 201 Spring St. Lexington MA 02421 Voice +1 781.301.2000 support@abinitio.com
Wells Fargo Enterprise Data Analytics : S/N: 41774
NOTICE
This document contains confidential and proprietary information of Ab Initio. Use and disclosure are
restricted by license and/or non-disclosure agreements. You may not access, read, and/or copy this
document unless you (directly or through your employer) are obligated to Ab Initio to maintain its
confidentiality and to use it only as authorized by Ab Initio. You may not copy the printed version of
this document, or transmit this document to any recipient unless the recipient is obligated to Ab Initio
to maintain its confidentiality and to use it only as authorized by Ab Initio.
Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under copyright law or license from Ab Initio.
All provided documentation is confidential and a trade secret of Ab Initio. This documentation is furnished under a license and may be used only in accordance with the terms of
that license and with the inclusion of the copyright notice set forth below.
TRADEMARKS
The following are worldwide trademarks or service marks of or licensed to Ab Initio (those marked ® are registered in the U.S. Trademark Office, and may be registered in other
countries):
® ® ®
> Cooperating I>O
® ®
Ab Initio Data>Profiler Init.com
® ® ®
Ab Initio I>O Director INIT
® ® ®
Abinitio.com Dynamic Data Mart Meta Operating System
® ® ®
BRE E2E Meta>Operating System
® ® ®
Co>Operating Enterprise EME Meta OS
® ® ®
Co>Operating System EME Desktop Portal Meta>OS
® ®
Co>Operating EME Management Console Metadata Portal
® ® ®
Co>Operation EME Portal Plan>It
® ®
Co>Operative Engine by Ab Initio Query>It
® ® ®
Co>OpSys Enterprise Meta>Environment Re>Posit
® ® ®
Co>Ordinate Enterprise Metadata Environment Re>Source
® ® ®
Co>Ordinator Enterprise MetaEnvironment Server++
® ® ®
Conduct>It Express>It Server+Server
® ® ®
Continuous Flows GDE Shop for Data
® ®
Continuous>Flows Graphical Development Environment The Company Operating System
® ®
Cooperating Enterprise Graph It
® ®
Cooperating System Graph>It
Certain product, service, or company designations for companies other than Ab Initio are mentioned in this documentation for identification purposes only. Such designations are
often claimed as trademarks or service marks. In instances where Ab Initio is aware of a claim, the designation appears in initial capital or all capital letters. However, readers
should contact the appropriate companies for more complete information regarding such designations and their registration status.
If any Ab Initio software or documentation is acquired by or on behalf of the United States of America, its agencies and/or instrumentalities (the “Government”), the Government
agrees that such software or documentation is provided with Restricted Rights, and is “commercial computer software” or “commercial computer software documentation.” Use,
duplication, or disclosure by the Government is subject to restrictions as set forth in the Rights in Technical Data and Computer Software provisions at DFARS 252.227-7013(c)(1)(ii)
or the Commercial Computer Software – Restricted Rights provisions at 48 CFR 52.227-19, as applicable. Manufacturer is Ab Initio Software LLC, 201 Spring Street, Lexington, MA
02421.
WARRANTY DISCLAIMER
The information in this documentation is subject to change without notice. Ab Initio makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. Ab Initio shall not be liable for errors contained herein or for incidental or consequential damage in
connection with the furnishing, performance, or use of this material.
Installation prerequisites 12
Installation overview 13
2. Post-installation tasks 16
Managing Data Discovery project specifications 17
A. Parameter reference 21
Required parameters 22
Optional parameters 24
Audience
This document is intended for technical staff who install and administer Data Discovery applications in
Express>It.
Documentation conventions
Unless otherwise noted, this documentation uses the conventions described below.
Following are the typographic conventions for code examples and DML function syntax:
Bold text, symbols, and Literal text that must be entered exactly • CLI command:
punctuation as shown. m_env -version
• DML function syntax (literal text
shaded):
Non-bold, non-italic text (in The data type of the return value of a DML function syntax (data types shaded):
DML function syntax only) function, and the data types of function
arguments.
Following are the conventions for non-bold symbols used in syntax descriptions, such as descriptions of
commands and functions:
= (DML function syntax only) An equal sign indicates, and is followed by, an argument’s default
value.
... An ellipsis indicates that the preceding item can be repeated one or more times.
[ ] Square brackets group the enclosed items and indicate that the group is optional.
Example Meaning
2 + 2 ⇒ 4 2 plus 2 equals 4
a[,b[,c]] a or a, b or a, b, c
a|bc|de a or b c or d e
[a|b] a or b or nothing
{a|bc}d a d or b c d
[a|bc]d a d or b c d or d
The following annotated example illustrates the typographic and symbol conventions used in the syntax
description of a DML core function (the function signature):
6. The name of the argument (text that must be replaced by a valid value or expression)
Byte conventions
The example represents a block of nine bytes. The bytes contain, in order, the native codes for the characters
J, o, h, n, 4, 2, and three spaces. Note the following:
• Each cell represents a single byte of data.
The “first” byte in memory — the one with the lowest address — is leftmost.
Unless otherwise specified, characters are in the native character set of the computer running the Ab
Initio software.
Getting assistance
Product documentation is available in online help and, for most books, as PDFs. You can also find the
documentation, reusable solutions, and user discussions through the Ab Initio online discussion browser.
(To install the browser, see Ab Initio Help.) To report documentation issues, please send email to
documentation@abinitio.com.
• The platform (operating system and version) your Co>Operating System is running on
• A description of what you were doing when the error message (if any) appeared
For information on installing the Co>Operating System, see the Server Software Installation and
Administration Guides.
For information on installing Express>It, see the Express>It Installation and Administration Guide. If you
plan to use the Metadata Hub with Data Discovery, Express>It should be installed with the Metadata
Hub integrated.
• (Optional) Metadata Hub Version 3.2.2 or later.
For information on installing the Metadata Hub, see the Metadata Hub Installation Guide.
• Ensure that the Ab Initio Environment has been installed. For more information, see the following topics
in the Ab Initio Environment Guide and Reference:
• About the Ab Initio Environment
• If you plan on using Data Discovery with the Metadata Hub, ensure that the following configuration
variables are set:
• AB_MHUB_HOME — The directory in which the Metadata Hub administration and import tools are
installed.
• AB_MHUB_DEPLOYMENT_DIR — The Metadata Hub deployment directory.
• Ensure that the user who is installing Data Discovery has write permission to the directory specified by
the AB_APPCONF_ROOT_DIR configuration variable. Write permission is required in order for the icons
for the Data Discovery user interface to be written to the $AB_APPCONF_ROOT_DIR/images/datad directory.
• If you are upgrading to Data Discovery from a previous version, follow the instructions in “Upgrading
from a previous version”.
If you are upgrading to the current version of Data Discovery from a previous version, see “Upgrading from
a previous version”.
2. In the directory where the installation files are located, run the dd_install.ksh script.
NOTE: You must have Technical Repository administrator privileges to run this script.
When you have finished installing Data Discovery, continue with “Post-installation tasks”.
3. Log in to Express>It in order to refresh the contents of all private project sandboxes containing Data
Discovery configurations.
4. Back up the psets of all private projects containing Data Discovery configurations.
5. Check in all Data Discovery configurations in all projects to the technical repository.
6. Install the new version of the Data Discovery software by running the dd_install.ksh script in the
directory where Data Discovery was previously installed.
7. Refresh all Data Discovery configurations by running the ac-appconf refresh utility as follows:
ac-appconf -i app-id refresh path-to-config-name.appconf [--import-changes]
Where:
• app-id is the application identifier that tells the utility where to perform the command.
For more information, see “ac-appconf refresh” in the Express>It Installation and Administration Guide.
• The expressit_common public project — Included in the datad project. The expressit_common project
includes compound control templates, dynamic subgraphs, and other artifacts that are required for Data
Discovery source data.
• The data_discovery private project — Includes useful examples, such as examples demonstrating data
profiling and functional dependency calculation. This project is a good starting place for users who are
new to Data Discovery.
The datad and expressit_common public projects are typically checked out as global projects. For more
information, see “Checking out common projects to the global directory” in the Express>It Installation and
Administration Guide.
For more information about the .projects.xml file, see “Managing project specifications” in the Express>It
Installation and Administration Guide.
Once you have finished adding the Data Discovery projects to the project specification file, continue with
“Setting up a Data Discovery private project”.
For more information about this command, see “create-project” in the Co>Operating System Graph
Developer’s Guide.
3. Lock the project's pset by running the air sandbox lock command:
air sandbox lock -parameters -set
For more information about this command, see “air sandbox lock” in the Technical Repository Command
Reference.
4. Include the global datad project in the private project by running the air sandbox parameter command:
air sandbox parameter -basedir . datad -common datad-project-sandbox-path
For more information about this command, see “air sandbox parameter” in the Technical Repository
Command Reference.
5. Create the required data directories for the new project by running the project-directories command:
project-directories -create
For more information about this command, see “project-directories” in the Co>Operating System Ab
Initio Environment Guide and Reference.
6. In the directory to which you extracted the installation package, run the dd_setup.ksh script.
This script prompts you to provide parameter values for the project you just created. For more
information about these parameters, see “Parameter reference”.
8. Add the private project to the Express>It .projects.xml project specification file.
For more information about adding projects to this file, see “Managing project specifications” in the
Express>It Installation and Administration Guide.
If you will be using Data Discovery with the Metadata Hub, continue with “Customizing the Metadata Hub
for use with Data Discovery”.
2. Navigate to the datad project sandbox, and then navigate to the mhub/customizations/load
subdirectory.
For more information, see “Loading extension sets into a Metadata Hub datastore” in the Metadata
Hub Customization Guide.
For more information about running this command, see “mh-import rule save” in the Metadata Hub
Import Command Reference.
• Optional parameters
For more information about parameters, see “Parameters” in the Co>Operating System Graph Developer's
Guide.
PRIVATE_DB $AI_DB
PRIVATE_DML $AI_DML
PRIVATE_MP $AI_MP
PRIVATE_PSET $AI_PSET
PRIVATE_RUN $AI_RUN
PRIVATE_XFR $AI_XFR
AI_DATAD_MHUB_APPLICATION The Metadata Hub application to which Data Discovery datasets are to be
assigned. This is typically the name of the specific private project.
$[ string_substring(PROJECT_DIR,string_rindex(PROJECT_DIR,"/")+1,
length_of(PROJECT_DIR)) ]
AI_DATAD_MHUB_DEPLOYMENT_DIR The location of the Metadata Hub deployment directory. The recommended
setting is the value of the AB_MHUB_LOCAL_DIR configuration variable.
AB_MHUB_HOME The location of the directory in which the Metadata Hub administration
and import tools are installed.
AI_DATAD_MHUB_INSTALLED A boolean specifying whether Data Discovery is used with the Metadata
Hub.
AI_DATAD_MHUB_SYSTEM The Metadata Hub system to which Data Discovery datasets are to be
assigned.
Default: $PRIVATE_DML
Default: $PRIVATE_DML
Default: $AI_SERIAL
Default: $AI_SERIAL
Default: $AI_MFS_TEMP
Default: 10
Default: $AI_SERIAL
Default: $AI_SERIAL_TEMP
Default: 25
Default: $AI_MFS