Instructions and Standards for Connection Objects in PowerCenter 7.1.3 Workflow Manager Written by e!

in "illenwater # 1$%&%$3 '()IS(* by e!in "illenwater # 11%11%$3

+ackground,
In an effort to maintain consistency within the PowerCenter Development and Production Repositories and ensure that security has been sufficiently addressed, this document provides the standards that should be followed for creating and maintaining connection objects (relational and ftp) using PowerCenter or!flow "anager# $ote that the standards for the Development and Production Repositories differ in order to manage the process in the most efficient manner possible without compromising security# %he following information is divided by repository and provides detailed information regarding the standards for each, in addition to instructions and responsible parties#

*e!elo-.ent 'e-ository
Relational and &%P connections in the Development Repository may be created by '%( developers, D)*+s, and '%( *dministration, adhering to the following guidelines and standards# '%( *dministration will monitor the repository to ensure that connections have been set up correctly, have not been duplicated, and to ensure that permissions on the objects have been set according to standards# *ny connections that do not meet the standards will be addressed with the owner of the connection in order to rectify any problems that e,ist#

-# Relational connections should be named to provide

information as to the database being accessed and the user accessing the database# %his will not only help to identify a connection in a listing, but will minimi.e the number of connections that are created, as the connection may be reused by others having the proper privileges to use such connection# %herefore, t/e for.at for na.ing is, database_username (i#e# dssdev_complete where the database is /dssdev+ and the username accessing the database in the connection is /complete+)# Right is a screen print of a connection named according to standards# 0O1(0 hen creating a 12( 1erver database connection, the process is slightly different than that of an 3racle relational connection# Due to the fact that the Power"art server applications are installed on a 4$I5 6P745 operating system, two tas!s need to be completed in order to set7up and successfully run a wor!flow which uses a 12( 1erver connection as the source, target, or both# &irst, the relational connection needs to be created as an /3D)C+ type connection in the Relational Connection 'ditor within PowerCenter or!flow "anager# 1econd, an entry needs to be made in the #odbc#ini file located on the server by the '%( *dministrator which PowerCenter accesses when running wor!flows with /3D)C+ type connections# %his entry provides the physical location of the database and the necessary port number for usage# %he naming standards for the connection remain the same as indicated above for relational connections with the e,ception that the prefi, /s8l9server+ precedes the database9username# %he following illustration

shows an e,ample of a 12( 1erver /3D)C+ type connection set up using the connection editor (named s8l9server9oir9!tgillen)# %he connect string is derived by using the prefi, /s8l9server+ with the database name immediately following (named s8l9server9oir)# %he '%( *dministrator will create an entry in the #odbc#ini file on the server which PowerCenter uses to access information related to the physical location of the database# *n entry is set up for each database in the #odbc#ini file on the server, while a relational connection is to be established for each schema within the database in PowerCenter or!flow "anager#

:# &%P connections should be named to provide information as to the nature of the ftp connection and the location of the machine involved in the ftp connection# 1ince the ftp may involve the mainframe or another 4$I5 machine, the name should be descriptive enough to enable a user to identify the connection and help prevent multiple connections with the same properties being set# Right is a screen print of a connection that is named according to standards#

;# &ollowing the creation of a new connection, permissions need to be reviewed to ensure that the 3wner, <roup, and orld have the correct permissions set# W/en a new connection is created2 t/e -er.issions are defaulted to R, , ' for 3wner= R, ' for <roup, and no permissions for orld (any user outside of the owner and the owner+s group)# 1/ese -er.issions are t/e standards t/at we will follow. *o not c/ange t/e owner or t/e grou- w/en editing -er.issions. '%( *dministration is responsible for assigning groups and ownership# If you feel that the object has an incorrect group or owner, or if the connection needs to be accessed by a user outside of the owner or the group, contact '%( *dministration# Read, rite, and ',ecute are defined as0 Read > ?iew the connection object in the or!flow "anager and Repository "anager rite > 'dit the connection object ',ecute > Run sessions that use the connection object It should be noted that, once a connection has been edited, any sessions and transformations using the connection will automatically pic! up the changes to the object within the repository in which the edit occurs# &or e,ample, if the dssdev_complete connection is changed to dssdev_admin and the properties within the connection now show the user as admin, then any objects using the dssdev_complete connection will now list the connection as dssdev_admin# $o further changes need to be made to individual sessions and transformations within wor!flows#

Production 'e-ository
'%( *dministration is responsible for creating and editing all object connections within the Production Repository according to the guidelines that e,ist as listed in the section /Development Repository+ above# D)*+s should contact '%( *dministration when changes need to be made to e,isting connections, or if a new connection needs to be created#