www.insightsoftware.com for JD Edwards World and EnterpriseOne Version: 3.3 Last Updated: September 2, 2011

Contents 1. Architecture... 3 Overview... 3 Deployment... 4 Database Space... 4 Using This Guide... 4 2. Administration Setup... 5 Using the Administration Application... 5 Functional Icons and the Control Interface... 5 Quick Access Toolbar... 10 Starting the Administration Application... 11 3. Repository Management... 25 Saving your Repository Selection File... 26 Exporting Lists to Excel... 27 JD Edwards Data Sources - ERP... 27 ERP Database Connections... 28 ERP Connection Profiles... 35 Environment and Model Business Unit... 48 Documents... 76 Import/Export... 87 Logging... 92 Reusable Inquiry Objects... 100 Users and Groups... 101 4. Module Security... 115 Basic Configuration... 116 Using Module Security... 119 Advanced Security Inheritance and Priority... 132 5. Repository Database... 134 Overview... 134 Creating a new database in Microsoft SQL Server... 135 6. Creating Data Sources... 146 Creating ODBC Data Sources... 148 Creating an ODBC Data Source to the Object Repository AS400 DB2... 154 Creating Other Data Sources and Connections... 156 Creating a Data Source Repository Connection using IBM DB2/400... 160 7. Troubleshooting... 163 8. Further Information... 164 Contacts... 164 Technical Support... 164 Notices and Disclaimer... 164 Page 2 of 164

Overview Insight is a Microsoft.NET Windows application that runs under a 2-tier architecture. The application has its own built-in database connectivity layer which is responsible for submitting the queries to the ERP database directly and independently from the ERP application. Insight configuration and inquiry parameters are stored in a centralized database (Object Repository) created during the initial installation. This Repository can be created on one of four different database servers: Oracle, SQL Server, DB2, and DB2 UDB. The architecture is shown in Figure 1-1. Figure 1-1: Typical Architecture Insight offers multiple deployment options: Manual desktop deployment Terminal server deployment Smart Client deployment which utilizes Microsoft s ClickOnce technology. A combination of all of the above options NB INSIGHTSOFTWARE.COM RECOMMENDS THAT THE OBJECT REPOSITORY IS ADDED TO YOUR DAILY DATABASE BACKUP ROUTINES Page 3 of 164

Deployment There are several options available to deploy Insight. When initially installing and configuring the software, the manual desktop deployment option is used. This same installation process can be used if a small number of additional desktops need to be installed. For larger desktop installations, a terminal server deployment, utilizing Windows Terminal Services or Citrix, is available. This option is best for those users who will be accessing the Repository and ERP databases from a Wide Area Network (WAN) connection. Terminal server deployment is shown in Figure 1-2. With the release of Version 9.0, Insight offers a Smart Client deployment option which utilizes Microsoft s ClickOnce technology. All of the above options can be used in combination to meet the needs of the user and IT department. Database Space Figure 1-2: Citrix Farm Architecture In order to set up and manage the Insight Repository, it is necessary to first have database space available and accessible so that you can create or install the application. Creating a new database is covered further on in this document; see the chapter New Repository Database: Creating a new database in Microsoft SQL Server Creating a new database in Oracle Creating a new library in IBM DB/2 with SQL collection Using This Guide NB In order to get the most out of this guide, we have used the following symbol to denote areas of special interest, supporting information on a topic and highlighting other important points: IMPORTANT INFORMATION Page 4 of 164

Using the Administration Application The Administration Application is used for working with the administration elements of Insight. This includes the creation and management of database repositories, setting up and managing user profiles and permissions and implementing individual business preferences. The Insight Administration Application s installation wizards and intuitive interfaces provide a user-friendly tool for managing your data. Functional Icons and the Control Interface The Administration Application uses various functional elements to manage the administration of Insight. Below is an overview of these functional elements, and more detailed information follows throughout the document. The Administration Application s main dialog has a functional Ribbon along the top and two display panes below. In the left-hand pane is the initial item Repository Database Connections (Figure 2-1). Figure 2-1: Administration Application Dialog Page 5 of 164

The right-hand pane of the Administration Tool displays the contents of the selected item from the left-hand pane. The display and tree-structure have the same look and feel of the Windows Explorer file management tool. The Ribbon Icons are active when they are in color and grayed-out when inactive. Clicking the different functional elements in the left-hand pane of the Administration Application will change the Ribbon to provide the icon tools appropriate to your selection. When there are multiple elements that an icon can be applied to, a small down arrow shows to the right of the icon. Drop-down options can then be selected by clicking with the mouse. For example the View Icon has four options: List, Details, Small Icons and Large Icons. See Figure 2-2. Figure 2-2 : Icons with Multiple Selections Some selected Ribbon options can also be accessed via the keyboard. These keyboard shortcuts are identified by pressing the ALT key (as shown in Figure 2-3). To then activate the ribbon option press the associated key displayed on the Ribbon. Figure 2-3: Ribbon Keyboard Shortcuts Page 6 of 164

The tables below list the icons within their function and description. Update the Ribbon for Budgeting Modeling Home Page Ribbon Edit Icon Function Description New Creates a new element within the Insight Administration Application Edit Edits an element Rename Renames an element you have created Delete Deletes the selection Permissions Sets the Permissions for the selected object Properties Reviews the properties and use of an object Clipboard Paste Table 2-1: Edit Icons Pastes from the clipboard Cut Cuts the selected text or element from its current location to the clipboard Copy Copies the selected text or element to the clipboard Table 2-2: Clipboard Icons Page 7 of 164

Navigation New Search Opens the Search tab on the left-hand pane Refresh Refreshes the view to reflect any changes you have made Up to Parent Moves your selection up the tree directly to the parent level Back Goes back to the last selection within the tree Forward Goes to your most recent selections after using Back List View Save View Sort List Table 2-3: Navigation Icons Saves the list you have in the right-hand pane to a Spreadsheet Compatible (Comma Separated) File Arranges the right-hand pane by List, Details, Small Icons, Large Icons Sorts the elements of the right-hand pane by Name, Type or Modified Selection Select All Table 2-4: List View Icons Selects all of the elements within the right-hand pane Invert Selection Selects the un-highlighted elements Initial Setup Initial Setup Table 2-5: Selection Icons Opens the wizard that creates a Repository Database Connection and Repository Table 2-6: Initial Setup Icon Page 8 of 164

Repository Ribbon Initial Setup Login/Logout Opens the wizard that creates a Repository Database Connection and Repository Backup Backs up the Repository Database Validate Validates the Repository connections and settings Table 2-7: Repository Initial Setup Icons DB Connection Manage Disconnect Disconnects from the Repository Database Connection Library/Schema Connects to a specific Library/Schema Table 2-8: Manage Connection Icons User Group Ribbon Licensing Assign Licenses Sets User Licenses Manage Keys Manages License Keys Table 2-9: Licensing Icons General Browse as User Browses As User Password Policy Sets Password Policy for the Repository Synchronize Users Synchronizes users against the ERP Table 2-10: General Icons Page 9 of 164

Import/Export Ribbon Import Open File Opens an Export RDF File Export Begin Table 2-11: Import Icons Creates a blank Repository area for copying multiple objects Clear Clears the Repository area created by the Begin Icon Save Saves the Repository area and its contents into an RDF file Table 2-12: Export Icons Quick Access Toolbar You can customize the appearance of the Administration Application s Ribbons by creating your preferred selection of tools on a Quick Access Toolbar. The icons are smaller and are without a label, so they take up less screen space. The Quick Access Toolbar can be arranged above or below the Ribbon. You also have the option to hide the Ribbon completely. To open the standard Ribbon, click on the rightmost double down arrow on the Quick Access Toolbar and select or deselect Minimize the Ribbon (Figure 2-4). Figure 2-4 : Customize Quick Access Toolbar Page 10 of 164

Starting the Administration Application Once the Insight software is installed, the application can be run. Navigate to the Start/Programs/InsightSoftware.com/Insight 9.0/Administration shortcut that you previously configured and click the icon to launch the application (Figure 2-5). Initial Setup Wizard Figure 2-5: Start Menu On opening the Administration Application, you will see the main display dialog and functional ribbon. The first time you use the Administration Application after installation, the Initial Setup Wizard dialog will automatically open. The Initial Setup wizard is a tool for administrators to quickly get their installation of Insight up and running. It takes you through the necessary steps to both create a new instance of Insight and/or to upgrade from a previous version. You can cancel the Wizard by clicking Cancel or by clicking the Close Window (X) on the top right corner of the wizard dialog. The Initial Setup Wizard dialog opens with the Insight Repository Setup welcome page. Click on Next. NB IF YOU ACCIDENTALLY CANCELLED THE WIZARD AND NEED TO OPEN IT AGAIN CLICK ON THE INITIAL SETUP ICON FOUND WITHIN THE RIBBON Page 11 of 164

The Choose Configuration Method dialog opens (Figure 2-6): Figure 2-6: Choose Configuration Method At this point in the Wizard we must choose either: Provide the information now, using this wizard: The subsequent sections of the wizard will configure a new Repository Connection Read it from an existing Repository Selection File: Allows the selection of an existing Repository Connection by using the Repository Selection File. The user can navigate to the saved.xml file by selecting the radio button and clicking the button. The.xml file is commonly found within the Insight program directory. For more information on the Repository Selection File please refer to the Saving your Repository Selection File section. Page 12 of 164

In order to create a workspace or Repository for Insight via the previous Provide the information now, using this wizard, we must first set up a Repository Database Connection. This will define where the Insight Repository will be stored and how the software will connect to it. Figure 2-7: Repository Database Connection Microsoft SQL Server Identification Use this to specify the name for this Repository Database Connection. You can create separate repositories for Insight by setting up different Repository and Repository Database Connections (for example when setting up a separate test environment). To identify these you will need different Identifications. There is a default name and description that can be overtyped. Page 13 of 164

Data Source Use this to specify the Type of database in which your Insight Repository will be stored and also the Provider or driver you are using to connect to the Repository from your client machines. Data Source Type options include: Microsoft SQL Server Oracle IBM DB2 UDB Local Database file The Data Source Provider options for creating connections are appropriate to the data sources: SqlClient Data Provider Built-in Data Provider OracleClient Data Provider ODBC Data Provider Click on Next when you have selected your Data Sources. You are now ready to configure the Connection. NB AFTER THIS POINT, THE REPOSITORY DATABASE CONNECTION GUIDE IS BROKEN DOWN INTO SEPARATE SECTIONS FOR:.NET Framework Microsoft SQL Server ODBC IBM and Oracle Specific Oracle Client Page 14 of 164

.NET Framework Microsoft SQL Server Configure Connection Now that the Provider and Data Sources for the Repository are set, you can specify the Server and the Database where the Repository is located. This information is then used by the driver or data provider whenever you connect to the Repository (Figure 2-8). Figure 2-8: Repository Database Connection Configuration SQL Server Server Use the drop-down box to select the Server your Repository Database is stored on, or type in the location. Login Specify the Login details needed to access the server on which the Repository will be located. If you have no password, click the Blank checkbox. Page 15 of 164

Database Select the Database in which you are storing the Insight Repository. If you have not already created a Database, there is additional information on how to do so in the chapter New Repository Database: Creating a new database in Microsoft SQL Server Test Connection Click on the Test Connection button and the Administration Application will check that all of the connection details are working as you expect. If there are any errors, a message box will appear and identify them so they can be addressed. When the configuration is working, the Test Connection message confirms that it is successful (Figure 2-9). Figure 2-9: Test Connection Message After you have configured the Repository Database information, click on Next. Page 16 of 164

Select or Create a Repository The Initial Setup Wizard dialog Select Repository opens. This shows a list of any existing Repositories on the specified Database; the same dialog allows you to create a new Repository (Figure 2-10). Figure 2-10: Select or create a new Repository Select an existing Repository If you have an existing Repository, select the Repository you want to connect to from the list provided. If there is only one Repository in the Database, it will be selected by default. Click the Next button. Create a new Repository If you want to create a new Repository, click on the radio button next to Create a new Repository and then enter the following: A unique Repository Name for the Repository, comprising of up to 16 letters and digits A Description of the Repository (optional field) The Initial Administrator is the username to access the Repository. It initially defaults to Administrator however can be overtyped Administrator Password is set here and then confirmed in the later Confirm Password field License Key or Code (optional field) Page 17 of 164

To save and complete the creation of your new Repository, you must click both Next and Finish on the Wizard completion page (Figure 2-11). Your Insight Repository is now ready! Figure 2-11: Final Page of the Repository Setup Wizard Page 18 of 164

ODBC IBM and Oracle Specific Configure Connection Now that the Provider and Data Sources for the Repository are initially defined, you can configure the driver to specify the location of the Repository as well as the login credentials to the server (Figure 2-12). Figure 2-12: Repository Database Connection Configuration ODBC ODBC Use Data Source Name to select the specific ODBC you will be using to connect to the Repository. If the default is not your choice, complete the Connection String field with the location for the ODBC. Use the Build function to navigate to the File Data Source or an alternative Machine Source File where you are sharing the ODBC. Login Specify the Login details needed to access the server on which the Repository will be located. Page 19 of 164

Test Connection Click on the Test Connection button and the Administration Application will check that all the connection details are working as you expect. Click Next to save the settings and move to the Select or Create a Repository. The Library for the repository will be chosen based on the user name. If you have not already created a Library, there is additional information on how to do so later in this document. See the chapter New Repository Database: Creating a new library in IBM DB/2 with SQL collection. Select or Create a Repository The Initial Setup Wizard dialog Select Repository opens. This shows a list of any existing Repositories in the specified Library. The same dialog allows you to create a new Repository (Figure 2-13). Figure 2-13: Select or Create Repository ODBC Select an existing Repository If you have an existing Repository, select the Repository you want to connect to from the list provided. If there is only one Repository in the Database, it will be selected by default. Click the Next button. Page 20 of 164

Create a new Repository If you want to create a new Repository, click on the radio button next to Create a new Repository and then enter the following: A unique Repository Name for the Repository, comprising of up to 16 letters and digits A Description of the Repository (optional) The Initial Administrator is the username to access the Repository. It initially defaults to Administrator however can be overtyped Administrator Password is set here and then confirmed in the later Confirm Password field License Key or Code (optional) To save and complete the creation of your new Repository, you must click both Next and Finish on the Wizard completion page. Oracle Built-in Data Provider Select Data Source/Type as Oracle and the default Provider is the Built-in Data Provider (Figure 2-14). Figure 2-14: Oracle Client Repository Database Connection Page 21 of 164

Configure Connection Now that the Provider and Data Sources for the Repository are initially defined, you can configure the driver to specify the location of the Schema and Repository as well as the login credentials to the server (Figure 2-12Error! Reference source not found.). Figure 2-15: Oracle Client Connection Configuration Server Specify the Host (Server) Name of your server, the Service Name (SID) of the instance you wish to connect to and its Port number. Login Specify the Login details needed to access the server on which the Schema and Repository will be located. Test Connection When you click on the Test Connection button, the Administration Application will verify that all the connection details are working as you expect. Click Next. Page 22 of 164

Select Schema Location The Library for the repository will be chosen based on the user name. If you have not already created a User/Schema for this, there is additional information on how to do so in the chapter New Repository Database: Creating a new schema in Oracle. Select or Create a Repository The Initial Setup Wizard dialog Select Repository opens. This shows a list of any existing Repositories in the specified Library. The same dialog allows you to create a new Repository (Figure 2-16). Figure 2-16: Oracle Client Select Repository Select an existing Repository If you have an existing Repository, select the Repository you want to connect to from the list provided. If there is only one Repository in the Database, it will be selected by default. Click the Next button. Page 23 of 164

Create a new Repository If you want to create a new Repository, click on the radio button next to Create a new Repository and then enter the following: A unique Repository Name for the Repository, comprising of up to 16 letters and digits A Description of the Repository (optional) The Initial Administrator is the username to access the Repository. It initially defaults to Administrator however can be overtyped Administrator Password is set here and then confirmed in the later Confirm Password field License Key or Code (optional) To save and complete the creation of your new Repository, you must click both Next and Finish on the Wizard completion page. Manually create a new Connection for your intended Repository To create a new Repository Database Connection without using the Initial Setup Wizard, click on New or right-click on Repository Database Connection and select New/ Repository Database Connection. Page 24 of 164

Now that a connection to the Insight Repository has been set up, use the Administration Application to define your Repository. In this chapter we focus on managing Repositories, Database connections, User Profiles and using the Insight with Microsoft and Oracle databases. After completing the Initial Setup Wizard or manually creating a Repository, the Administration Application main dialog opens. You will see the Repository Database Connection you have just created appear in the Left Hand Pane. If you click on the underlying Repository the Ribbon automatically displays the Repository Tab, click on the Login icon to open the Repository Login dialog. Alternatively double click on the Repository Name to also open the Repository Login dialog. Enter in the Repository Login dialog the login name and password that you specified in the Initial Setup for the Repository and click Login. The Repository Icon will change from Grey to Yellow (Figure 3-1) if you have correctly entered in your login credentials. Figure 3-1: New Active Repository To select a subfolder, you can navigate using the + icons in the left-hand pane or click on the folder in the right-hand pane of the Administration Application dialog. Page 25 of 164

Saving your Repository Selection File The Repository Selection File (or RepositorySelection.xml file) defines where the Insight Repository will be stored and how the software will connect to it. Once a Repository has been created/chosen, the repository selection should be saved in the Insight directory for subsequent use for all users on that machine. Right click on your Repository and select Save Repository Selection as per Figure 3-2 Figure 3-2: Save Repository Selection A Save As dialog will be displayed, allowing you to specify the Insight directory. NB IF THE REPOSITORYSELECTION.XML FILE DOES NOT EXIST IN THE INSIGHT DIRECTORY, THE LOGIN DIALOG WILL DISPLAY THE INITIAL SETUP WIZARD, WHICH WILL BE USED TO SELECT OR CREATE A REPOSITORY. The file can be copied by to other machines in order to use the same Repository selection. Page 26 of 164

Exporting Lists to Excel You can export any results within the right-hand pane to a spreadsheet compatible file (CSV), by right-clicking within the right-hand pane and selecting Save List. You can then name, save and open the results within any spreadsheet application, allowing you enhanced management and maintenance of the Repository. JD Edwards Data Sources - ERP Repository Data Sources refers to the business information you wish to manipulate and manage using the Insight Application (Figure 3-3). Figure 3-3: Repository ERP Data Sources Connections store the information (database type, user name and password) required to connect to your ERP Database(s). Profiles reference any associated connection(s) and define the parameters for Insight to derive correct information from your ERP System. You will need to have an ODBC Data Source Connection set up ready for use. For more information on this, please see the section ODBC Data Source Connection. Page 27 of 164

ERP Database Connections To create a new connection, right-click on the Connections icon in the left-hand pane of the Administration Application. Within the associated menu, Select New, then Database Connection as per Figure 3-4. Figure 3-4: New Database Connection Right-click Alternatively, you can use the New Icon and select Database Connection (Figure 3-5). Figure 3-5: New Icon for Database Connection Page 28 of 164

Clicking on New Connection will launch the Database Connection dialog (Figure 3-6). SQL Server Figure 3-6: Database Connection Identification Use this to specify the name of the ERP Connection. Data Source Use this to specify the Type of Database in which your ERP data is stored and also the Provider or driver you are using to connect to the Database from your client machines. Click Configure to specify the location of the Database. This information is then used to build the profile. Page 29 of 164

Figure 3-7: Database Connection Configuration SQL Server Server Use the drop-down box to select the Server on which your Database is located, or type in the location. Login Specify the Login details needed to access the server. If you have no password, click the Blank checkbox. Database Select the Database on which your ERP data, security, Data Dictionary or UDC tables are stored. Page 30 of 164

IBM DB2 Test Connection When you click on the Test Connection button, the Administration Application verifies that all of the connection details are working as you expect. If there are any errors, a message box will appear and identify them so they can be addressed. The Test Connection functionality can be disabled; so that a connection can be established for a server which is inaccessible (useful if the server is currently offline due to backup). After you have configured the Database information, click on OK. You may need to repeat the process if you require more than one connection to the ERP tables. Figure 3-8: Database Connection - IBM DB2 Identification Use this to specify the name of the ERP Connection. Data Source Use this to specify the Type of Database in which your ERP data is stored and also the Provider or driver you are using to connect to the Database from your client machines. Click Configure to specify the location of the Database. This information is then used to build the profile. Page 31 of 164

Figure 3-9: Database Connection Configuration IBM DB2 Server Type in the Host Name for the database and check the box if your database version is pre-v5r3. Login Specify the Login details needed to access the server on which the Repository will be located. If you prefer to enter the password each time, choose the second option. Settings Type in the default Library as well as the data, control and security libraries. Test Connection When you click on the Test Connection button, the Administration Application verifies that all of the connection details are working as you expect. If there are any errors, a message box will appear and identify them so they can be addressed. The Test Connection functionality can be disabled; so that a connection can be established for a server which is inaccessible (useful if the server is currently offline due to backup). After you have configured the Database information, click on OK. You may need to repeat the process if you require more than one connection to the ERP tables. Page 32 of 164

Oracle Figure 3-10: Database Connection Oracle Identification Use this to specify the name of the ERP Connection. Data Source Use this to specify the Type of Database in which your ERP data is stored as well as the Provider or driver you are using to connect to the Database from your client machines. Click Configure to specify the location of the Database. This information is then used to build the profile. Page 33 of 164

Figure 3-11: Database Connection Configuration Oracle Server Specify the Host (Server) Name of your server, the Service Name (SID) of the instance you wish to connect to and its Port number. Login Specify the Login details needed to access the server. If you prefer to enter the password each time, choose the second option. Test Connection When you click on the Test Connection button, the Administration Application verifies that all of the connection details are working as you expect. If there are any errors, a message box will appear and identify them so they can be addressed. The Test Connection functionality can be disabled; so that a connection can be established for a server which is inaccessible (useful if the server is currently offline due to backup). After you have configured the Database information, click on OK. You may need to repeat the process if you require more than one connection to the ERP tables. Page 34 of 164

ERP Connection Profiles A profile can be made up of multiple Connections. This is why the ERP Wizard allows you to create a new Connection or make use of an already existing one. Additionally, for ease of use, a Database Connection can also be reused by multiple Profiles. To create a New ERP Profile select Profile in the left-hand pane of the Administration Application Tool (Figure 3-12) and either click on the New Icon (Figure 3-13) and select ERP Profile or right-click to select New/ERP Profile (Figure 3-14). Figure 3-12: Profile Figure 3-13: New ERP Profile Icon Figure 3-14: New ERP Profile with Right-click The New ERP Profile dialog opens. Enter a unique name that identifies the Profile. Click on OK (Figure 3-15). Figure 3-15: Name your new ERP Profile Page 35 of 164

Create / Edit ERP Profile After you have named your new ERP profile, the Create/Edit ERP Profile Wizard will launch (Error! Reference source not found.). As it suggests, this wizard can be sed to either create new ERP profiles or to edit an existing one. Figure 3-16: New Profile Wizard Page 36 of 164

JD Edwards Connectivity (Main, Security, UDC and Data Dictionary Connection) Next we need to define the interconnectivity settings between the application and the JD Edwards database(s). These settings are shown below in Figure 3-17. Figure 3-17: JD Edwards All Connectivity Settings On this screen you may need to supply up to four Connections. These are the Connections that link the application with the JD Edwards database tables. The Data Connection setting links to the main JD Edwards data tables, such as F0902 and F0911. The Security Connection setting links to the JD Edwards security tables, such as F0092 and F0093. The Data Dictionary Connection setting links to the JD Edwards Data Dictionary table F9201 for World Installations or F9210 for EnterpriseOne installations. The UDC Connection setting links to the JD Edwards UDC data table, such as F0005. Simply choose the relevant connection from the previously defined list of available Connections. If a Connection has not been defined, click on the New button and you will be presented with the ODBC Connection dialog and from here a new connection can be created based on an existing ODBC Data Source. For more information on setting up a Connection, please refer to the previous section ERP Database Connections. Page 37 of 164

If the JD Edwards security, Data Dictionary or UDC tables reside in the same database on the same machine as the data tables, it is possible to use the same Connection for all connections. In such instances the Same as Data Connection tick box should be enabled for the relevant connection and no further Connection details need to be provided. Once established, click the Next button to proceed to the next screen of the configuration wizard. JD Edwards edition and version Since the application is compatible with World, EnterpriseOne and Coexistence customers, you will need to choose the edition of JD Edwards that matches your current setup. The configuration wizard will detect a JD Edwards EnterpriseOne or World installation. In the example shown in Figure 3-18, the World software option has been disabled because JD Edwards EnterpriseOne was detected. Figure 3-18: JD Edwards edition and version Select the version of the JD Edwards software implementation to which you will be connecting. If the version of JD Edwards software is unknown, please contact your JD Edwards system administrator. After clicking on the Next button, there will be a pause while the data source is analyzed for relevant control and data tables. The amount of time this process takes will vary depending on the size of the JD Edwards implementation. Page 38 of 164

Database Settings JD Edwards data can reside on different database platforms. Some of these have specific restrictions on what can be done with regards to SQL Commands and query sizes. The following screen of database specific settings will only appear for the database platform of DB2/AS400 (Figure 3-19). Figure 3-19: Database Settings Page 39 of 164

If using DB2/AS400, please select any of the applicable options. If you use a V5 release of OS400 you do not need to select any of these. When enabling the SQL setting Column Limit, you will specify a maximum limit on the number of columns allowed in a SQL Query. You can allow the configuration tool to attempt discovery of this value by using the Detect option when enabled. Figure 3-20 shows the Column Limit being detected. Figure 3-20: Detecting column limit NB DEPENDING ON YOUR DATABASE AND VERSION, THE NUMBER OF COLUMNS WILL DIFFER. IT IS RECOMMENDED THAT YOU USE THE DETECT FUNCTIONALITY AND ENABLE THE COLUMN LIMIT. Page 40 of 164

Module Selection The next task is to specify which Insight modules should be activated within this Connection. Only the modules that your organization has licensed will be available for selection on the dialog shown in Figure 3-21. Figure 3-21: Module Selection Localized Captions gives the ability to derive different language captions from the underlying JD Edwards system. Weekly reporting is available if you use this option in JD Edwards. The application of this is directly related to the Date Fiscal Patterns 52 Period Accounting Table (F0008B). Line of Business Support and Use Date Effective Categories are also available if you use these Accounts Receivable/Sales Order Processing options in JD Edwards. When Line of Business Support is enabled, Insight will use the Customer Master by Line of Business Table (F03012). If it is disabled, Insight will use the Customer Master Table (F0301). When Date Effective Categories is enabled, Insight will be able to derive data from the Customer Date Effective Category Codes Table (F03012A). Page 41 of 164

Table locations The next task is to define all of the tables needed for the Insight with the appropriate Owner, Library or Schema name. If there is uncertainty over any of the table selections explained below, please consult your JD Edwards administrator. The tables available are split between mandatory and optional, both of which can be defined on this screen. The default setting for the table definition is to only show those tables that have multiple selectable prefixes. If your database tables are only available in one library/schema or table owner, then this screen will be blank (see Figure 3-22). Figure 3-22: Table locations with single selectable prefix Page 42 of 164

If you would like to check the tables before continuing, you will need to check Show All Tables. This will populate the screen with all available tables, as shown in Figure 3-23.The associated modules are displayed next to the table names. Libraries & Table owners Figure 3-23: Show All Tables Databases are composed of tables. Tables are the structures that hold data. For administrative purposes, the tables are organized into groups so that all reference information is held together. In the IBM DB2/400 database, this grouping is called a library. For Oracle and SQL Server databases the equivalent of a library is the Table Owner (SQL Server) or schema (Oracle). A table owner/schema is associated with the database user who owns, and most likely created, the database table. During this Profile Wizard we use the term Owners/library names to cover all possibilities. If the correct default libraries have been supplied in the ODBC connection for DB2/400, Oracle or SQL Server, the library prefixes should automatically be completed. Please ensure that all of the tables in the list either have a valid prefix or are set to Do not use where appropriate. If this is not the case, valid prefixes can be manually entered by double-clicking on the appropriate prefix field and entering the name manually. Another option is to Page 43 of 164

highlight multiple rows and right-click. This will provide you with a selection of Library Prefix names that are common to all highlighted tables. When all of these prefixes have been applied, click on the Next button to continue. Budgeting Information (Optional) The screens shown in Figure 3-24 and Figure 3-25 (the latter for World connections only) will only appear if you have a valid license for the Budgeting module and have selected the Budgeting Module to be configured in this data source. (For budgeting information, please refer to the Budgeting User Guide.) Figure 3-24: JD Edwards Connectivity (Budgeting Connection) Page 44 of 164

Figure 3-25: Third Party Program Location Page 45 of 164

Data Dictionary This step requests the location of the Data Dictionary table, and allows you to choose whether you want to use any Data Dictionary overrides. This is illustrated in Figure 3-26. Figure 3-26: Defining the Data Dictionary Location The Data Dictionary library is an information library that contains data definitions to access when using Insight. If using EnterpriseOne or World version A81 or higher, the table name will be F9210. When using World versions lower than A81, the table name will be F9201. Therefore the syntax will either be <LIBRARY>.F9210 or <LIBRARY>.F9201. In some environments, the database name is needed. In such cases, the syntax will be <DATABASE>.<LIBRARY>.<TABLE>. More details on Data Dictionary overrides can be found in the section, Creating Data Dictionary Overrides for a JD Edwards Connection. Page 46 of 164

Testing the Configuration This step tests what has been entered so far in the Connection Wizard. To run the test click the Run Test button to begin. A successful test can be seen in Figure 3-27. Figure 3-27: Testing the Configuration If a warning message is received at this point, click on the Back button to return to the screen that is relevant to the issue highlighted in the message. Examine and alter those settings that are at fault before returning to test the configuration. Page 47 of 164

Environment and Model Business Unit The dialog shown in Figure 3-28 provides a way of specifying the associated JD Edwards Environment. This can be selected from the drop down list of options or it can be entered manually. Figure 3-28: Environment and Model Business Unit Selection Model Business Units Insight uses the JD Edwards Model Business Unit to validate object accounts selected by the user. The Model Business Unit should contain a complete list of all the object accounts used across all the business units. If there is no single model Chart of Accounts but there are separate model balance sheets and model profit and loss accounts, multiple Business Units can be entered. Initially the dialog allows for one General Model Business Unit Option, which is then applied to all Modules. When enabled the Override for specific modules functionality provides a way for the General Ledger, Job Cost and Fixed Asset Modules to have specific Model Business Units assigned. Either enter the Model Business Unit(s) manually (comma separated for multiple Models) in the field provided or press the Search button to the right of the field. Page 48 of 164

Model Business Units dialog By clicking on the Search button, the following dialog will appear (Figure 3-29). This dialog will only display Model Business Units (BU) from your JD Edwards system. In JD Edwards, Model Business Units (BU) are identified as such within the Business Unit Master table F0006. Typically a Model BU will be kept up to date and will contain a complete account structure. A Model BU typically does not have any transactional data. Please select all of the relevant Model Business Units and click on OK. Figure 3-29: Model Business Units If you do not have a complete Model BU available, you may opt to enter an alternative BU (one that is not defined as a Model BU in JD Edwards ). NB IF YOU CHOOSE TO ENTER A LIVE BUSINESS UNIT IN THIS DIALOG, ALL USERS WILL BE ABLE TO SEE THE TRANSACTIONAL DATA FOR THAT BUSINESS UNIT. Page 49 of 164

Options The next stage in the configuration process is to define other options, including Subledger locations, Balance Sheet overrides, World Security options, etc. NB THE TAB WORLD SECURITY OPTION WILL ONLY BE AVAILABLE IF CONFIGURING A JD EDWARDS WORLD CONNECTION. IF YOU ARE CONFIGURING AN ENTERPRISEONE LOCATION, THIS TAB WILL READ SECURITY. THE DB2 INDICES TAB WILL LIKEWISE ONLY BE AVAILABLE IF YOUR JD EDWARDS SYSTEM IS HOSTED ON A DB2 DATABASE. Figure 3-30: Options screen with all available tabs Page 50 of 164

Subledger Locations The first tab on the options screen is used to determine which subledgers are to be included or excluded from the Subledger Filter. Simply select Include or Exclude from the drop down list for each of the Subledger Types. Figure 3-31 illustrates this. If all Subledger Types are required, click the Select All button for expediency. When all items have been selected, this button changes to be a Deselect All option, which when pressed, will exclude all Subledger Types. Within the Subledger Types, `A` is for Address Book, `C` is for Business Unit and `W` is for Work Order. It is also possible to further select Sub Types. To do this, click on the Sub Type button next to the Sub Type field in the Address Book entry (Figure 3-31). The dialog shown in Figure 3-32will appear. Figure 3-31: Address Book Subledger Figure 3-32: Address Book Subledger Settings Page 51 of 164

When selecting from the list, hold down the control or shift keys to select more than one item. Click on the OK button to confirm the Sub Type selections and the sub type field within the dialog will show these new selections, as illustrated in Figure 3-33. Figure 3-33: Address Book Subledger Sub Type selections NB IF THE ADDRESS BOOK SUBLEDGER TYPE HAS BEEN SELECTED, ONLY INCLUDE THE SUB TYPES THAT ARE NEEDED AS THIS CAN DRAMATICALLY SPEED UP THE PROCESSING OF THE SUBLEDGER VISUAL ASSIST. Within the Subledger Type `A` Address Book, it is also possible to select which Address Book record description should be used within the Insight. To do this, click on the Advanced button next to Address Book entry in the Subledger List. The dialog shown in Figure 3-34 will appear. Figure 3-34: Address book Description Choices Select the Address Book description needed and click OK to continue. NB FOR SUBLEDGER TYPE `S` ONLY, WE WILL SUPPRESS ALL THE * SELECTIONS WHEN RETRIEVING THE STRUCTURED SUBLEDGER TYPE `S` ITEMS. THE * SELECTION IS WILDCARD SEARCHING FUNCTIONALITY THAT CAN BE ACHIEVED IN THE QUERY BY EXAMPLE (QBE) FILTERS OF THE QUERY ASSIST DIALOG. Some clients have experienced reduced performance when joining to JD Edwards Subledger tables in Insight. This is because the key fields are stored in a different format in the main and Subledger tables. In response to customer feedback the option Use temporary table in Subledger joins was added to assist with these performance concerns. Page 52 of 164

Balance Sheet Overrides The Balance Sheet Overrides tab (Figure 3-35) allows you to configure which Automatic Accounting Instructions values from the AAI table, F0012, define the start and end items for your balance sheet and profit & loss range of accounts. By default this is GLG2 and GLG5. Figure 3-35: Balance Sheet Overrides If you want to override the AAI range in the F0012 table you can do so by checking the Define an override system option. This will then enable the Override button. Page 53 of 164

To define the balance sheet account range, click the Override button and Figure 3-36 will appear. Figure 3-36: Balance Sheet Account Range Dialog To specify a new account range click the New button to specify the start and end account of your balance sheet account range and then click OK (Figure 3-37). Figure 3-37: Balance Sheet Account Range Inclusion To modify an existing account range click the Edit button to specify the start and end account of your balance sheet account range and then click OK. To remove an account range, click the Remove button. NB THESE OVERRIDE SETTINGS DO NOT GET WRITTEN BACK TO YOUR JD EDWARDS DATABASE AND THEREFORE THEY WILL NOT MODIFY THE VALUES IN THE AUTOMATIC ACCOUNTING INSTRUCTIONS (F0012) TABLE. THE OVERRIDE INFORMATION IS STORED WITHIN THE INSIGHT OBJECT REPOSITORY. Page 54 of 164

Options As shown in Figure 3-38, by clicking the Options tab, the dialog allows you to select advanced result options including: Object Account & Subsidiary Description, Data Settings and Financial Year setting. Figure 3-38: Options Tab Page 55 of 164

The Description Settings option specifies which combination of Business Unit Object Account and Subsidiary will be used to derive the description value which Insight will display. Option Model BU/First Subsidiary (also applies for Object Account) Exact BU/First Subsidiary (also applies for Object Account) Exact BU/Blank Subsidiary (also applies for Object Account) Exact BU/Exact Object/Exact Subsidiary (also applies for Object Account) Explanation This default option uses the configured Model Business Units for the inquiry result. This causes no change in behavior from previous versions. Stores in a temporary table the descriptions based upon selections from your account master. Joins directly to the F0901 Joins directly to the F0901 Data Settings Data contains NULL values - you may disable this option to increase performance if you know that your data definitely does not contain null data. If you are unsure about this setting, please do not change the default setting unless advised by Support. Load Data Dictionary at start-up causes the Data Dictionary Cache to be pre-populated at Login. Disabling this option will result in the Data Dictionary being directly queried when required. Depending on the size of your Data Dictionary, it may be better to cache the Data Dictionary in a temporary table instead of routinely searching the table. If you are unsure about this setting, please do not change the default setting unless advised by Support. Financial Year setting: Financial years in JD Edwards are stored in 2 fields, CTRY (century) and FY (financial year). If you hold date for the same year in different centuries, such as 2007 and 2107, you should be using the Use CTRY and FY to determine year. Otherwise if you know that your Company s Date Fiscal Patterns (F0008) only span across one century, you will be able to enable the option Use FY only to determine year (best performance). Page 56 of 164

Security Options World Security Options (JD Edwards World sites only) By clicking the World Security Options tab, you will access the dialog shown in Figure 3-39. Figure 3-39: World Security Options NB THIS SCREEN WILL ONLY APPEAR IF YOU ARE CONFIGURING A JD EDWARDS WORLD DATA SOURCE. Page 57 of 164

Security settings JD Edwards Business Unit Security turns on/off Business Unit Security Allow blanks gives you the option of allowing blanks in the Business Unit Security Settings. Implement security using temporary tables (recommended) creates temporary tables to handle the JD Edwards security settings. This was added as it improves inquiry performance times. Use Tax ID / Social Security Number Masking - Used in combination with the Capabilities for Social Security Number Options, Insight can mask the display of Tax IDs / Social Security Numbers. Connection Settings allow you to select which security authentication mode you want your users to use as part of the logon process. Option Description 1 Connect to the AS/400 using the user s entered username and password 2 Connect using the username and password entered in the configuration wizard (Step 2) but validate the entered username and password against the AS/400 3 Connect using option 1, and upon failure connect using option 2 4 Connect using the username and password entered in the configuration wizard (Step 2) but validate the entered username and password using the Insight Object Repository password management Page 58 of 164

Enterprise One Security Options (EnterpriseOne sites only) If you are configuring an EnterpriseOne location, you will see the Security tab, as shown in Figure 3-40. Figure 3-40: EnterpriseOne Security Settings Security Settings Use JD Edwards Security. This option allows you to select the security you wish to use. The three options you have are Company, Business Unit and Object Account. You are able to allow blanks when choosing your security settings. Implement security using temporary tables (recommended) - By selecting this option, the Insight will create temporary tables to handle the JD Edwards security settings; this was added as it improves inquiry performance times. Use Tax ID / Social Security Number Masking - Used in combination with the Capabilities for Social Security Number Options, Insight can mask the display of Tax IDs / Social Security Numbers. Page 59 of 164

DB2 Indices This tab will only be available if your JD Edwards system is hosted on a DB2 database. See Figure 3-41 below. Figure 3-41: DB2 Specific Settings If your JD Edwards system is hosted on a DB2 database, we have added this option, which will improve the performance for Object Account/Subsidiary validation. This option relies on your indices on the F0901 table. Click the Test button to verify that we can use your indices and then check the box as appropriate. Page 60 of 164

Joins The final tab within the Options Screen is the Joins tab. Within the Insight modules General Ledger and Job Cost, we are using tables F0901 and F0902. This tab allows us to define how we want to join the two files (Figure 3-42). Figure 3-42: General Ledger/Job Cost Table Join Option Full Join: joins on all aspects of an account, i.e. Account I.D, Company, Business Unit, Object Account and Subsidiary. By joining on all of these fields, you are sacrificing speed for integrity due to the additional checks Insight will need to perform. Account ID Only Join: only joins on Account ID. This type of join sacrifices integrity for speed. You can check the integrity of your system by running the Account ID Integrity Test under Extended Tests in the Integrity Checker; this will allow you to see if it is safe to use this faster option. Page 61 of 164

Finish Screen Click Next after defining all of the Options and the Finish Screen shown in Figure 3-43 opens. Figure 3-43: The Finish Dialog NB PRESSING CANCEL ON THIS SCREEN WILL RESULT IN YOUR PROFILE NOT BEING SAVED. Page 62 of 164

After clicking the Finish button on this screen, you will see the Updating ERP Profile screen, as shown in Figure 3-44. Figure 3-44: Updating ERP Profile This will run through two connections: Setup Standard Templates and Setup Budgeting Repository. This process will load all of the information and templates that will be used by the configured ERP Profile. Once completed, the status bar columns will show as OK. Click Close to exit the screen if it doesn t exit automatically. If the process has not updated correctly, the status column will show as Error. This will mean that your profile will not be completed. You will need to fix the error before re-running the process. Double-click on the line to receive further information. On completion, your ERP Profile will appear as an item within Profiles. Page 63 of 164

Integrity Checking a Profile The integrity checker is designed to detect any problems or inconsistencies within the database that might interfere with the operation of Insight. To run an Integrity Check, right-click on a specific Profile from the right-hand pane of the Administration Application dialog and select Integrity Checker. Use the check-boxes on the dialog to select which tests or groups of tests you want to run and then click on Run. The results of the test appear in the bottom pane of the dialog (Figure 3-45). Figure 3-45: Integrity Checker Dialog Page 64 of 164

On the top-half of the screen, expand the Full System Test node to view individual tests. Tests are separated into two categories: Common Tests recommended tests, which detect common inconsistent settings. Extended Tests additional tests designed to tackle more complex data issues, which may take considerably longer to run. When the results appear in the bottom-half of the dialog, you can export them to a CSV file by right-clicking on the results pane. If you have MS Excel installed, the results will launch in Excel. The feedback from the data integrity tool is divided into two categories: Warnings: these suggest that current database settings may result in unexpected behavior. Errors: these indicate settings that are not compatible with Insight and need to change in order to ensure a complete and proper configuration. If there are any errors or warnings, please seek advice from your Systems Administrator. Page 65 of 164

Tests Descriptions Tables Columns Data Dictionary Checks the existence of the Data Dictionary (F9210 for EnterpriseOne sites or F9201 for World sites). Also checks to see if the Data F9210/ F9201 Date Default Year and Date Pattern Date Week Data Ledger Level Of Detail Account ID Business Unit Category Currency Information Model Business F03012 Table Integrity Test AS/400 Accounts Master Index Test Object Category Dictionary is populated. This is split into two tests. One test checks that there is a date pattern and a default year set for the model company 00000 in the F0010. The second test checks that the default year and date pattern for the model company 00000 exists in the F0008. Checks the existence of data in the F0008B. Checks the existence of ledger data in the relevant table (F0025 for EnterpriseOne sites or F0005 for World sites). Checks that we can create a temporary table. This is used in hierarchy queries, including LOD queries. Checks that the combination of Company, Business Unit, Object Account and Subsidiary are unique to an account ID across the fact tables and then checks to see if an individual account ID is unique to the combination of Company, Business Unit, Object Account and Subsidiary. Checks that the category codes defined in table F0006 exist in Table F0005. a. Checks for currencies in the F0013. b. Checks that currencies used in the F0902 exist in the F0013 table. c. Checks in the F0010 that company 00000 has a default currency set. Returns a list of Object Accounts from the F0901 that are not included in the Model Business. Runs a test against the F03012 and F03B11 tables to see if a table join between the tables on columns CO and AN8 can be used. Tests the master index in the F0901 table. Checks that all the category codes in table F0901 exist in table F0005. F0010 F0008 F0008B F0005 F0025 F0901 F0902 F0902B F0911 F1202 FA F1602 - ACA F0006 F0005 F0013 F0902 F0010 F0901 F03012 F03B11 F0901 F0005 F0901 CCDTPN (Pattern) CCDFYJ (Year) DRKY (F0005) LHLT (F0025) CO MCU OBJ SUB OBJ AID MCRP01 MCRP30 DRKY CCRCD GBCRCD CCCRCD GOBJ GMMCU RPCO RPAN8 AICO AIAN8 DRKY GMR0xx (xx = Category Number) Page 66 of 164

Creating Data Dictionary Overrides for a Profile The Data Dictionary Override is designed to override settings held within the JD Edwards Data Dictionary in order to negate any inconsistencies within the database that might interfere with the operation of Insight. To set up overrides to the Data Dictionary, right-click on the profile that you wish to amend and select Assign Data Dictionary Override (Figure 3-46). Figure 3-46: Assign Data Dictionary Override Select the Override you wish to use (Figure 3-47). Figure 3-47: Assign Data Dictionary Override Page 67 of 164

If you need to create a new override, click on the Manage button and in the Data Dictionary Overrides dialog, click on New (Figure 3-48). Figure 3-48: Data Dictionary Overrides Dialog Enter a name for the new Override and click OK (Figure 3-49). Figure 3-49: Name new Override The naming convention for Data Dictionary Overrides ONLY allows for letters, numbers and underscores. Space characters are not valid. Page 68 of 164

Figure 3-50: Edit Data Dictionary Override Enter the Name of the item as entered on the Data Dictionary table, and click Retrieve to import the attributes to the override table. You can then modify the settings for that particular data item. These new settings will be the values used within the application. NB THIS DOES NOT MODIFY THE DATA DICTIONARY IN YOUR JD EDWARDS DATABASE. THE OVERRIDE INFORMATION IS STORED WITHIN THE INSIGHT OBJECT REPOSITORY. Page 69 of 164

Import and Synchronize Users against a Profile After creating Connections and Profiles, you can then import and synchronize user names and information from your Enterprise Resource Planning (ERP) system with Insight. Synchronizing allows you to check for new users not currently stored in the Repository and also to cross-reference user data such as Group or Role information. Any subsequent amendments to Group/Role structures in the ERP system can then be mirrored by running the Synchronize tool. NB IF YOU CHANGE A USER NAME IN THE ERP SYSTEM OR IN INSIGHT, THE SYNCHRONIZATION WILL BE LOST AND THE USER IS TREATED AS A NEW ADDITION. Synchronize ERP Users First Time Select a Profile from the right-hand pane of the Administration Application Tool and right-click on it. Select Synchronize (Figure 3-51). Figure 3-51: ERP User Synchronization Or alternatively select a Profile and click on the Synchronize Users Icon (Figure 3-52). Figure 3-52: Synchronize Users Page 70 of 164

The ERP User Synchronization dialog opens, defaulting to the Profile you selected previously (Figure 3-53). Figure 3-53: ERP User Synchronization Settings Before synchronizing users, it is recommended to check the default settings included under the Settings button. These settings are applied to all users being synchronized (Figure 3-54). Figure 3-54: ERP Synchronization Settings The synchronization program can automatically create a folder structure based on the groups or roles used within the actual data from the JD Edwards Profile. In this case the default setting is to Use Roles, but this could be changed to Use Groups. Additionally Password information can also be applied. Newly synchronized users can have a Default Insight login password set. Hide Passwords in Details form changes the settings associated with the display of passwords in the Details form. With this enabled, passwords are displayed as a series of dots. With this disabled, passwords are shown in plain text. Page 71 of 164

Expire passwords for new users changes the settings associated with the expiration of the default password. When this is enabled, passwords are automatically expired and users must change their password at the next login. When this is disabled, users can log in to Insight using the Default password. Disable new users is a high-level security setting, and when enabled it stops new users from logging into Insight until a deliberate decision is made to enable the user s account. Click OK to confirm the Default Settings and return to the main screen. To assess available users under that Profile, click on the Analyze button as shown in Figure 3-55. Figure 3-55: ERP User Synchronization The Analyze functionality then collects and cross-references user data from the ERP system and displays it in the dialog. The Analysis Pending bar then turns green and its status changes to Analyzed. NB ANY USERS DISPLAYED AT THIS POINT CAN BE RIGHT-CLICKED. THIS PROVIDES THE ABILITY TO OVERWRITE THE DEFAULT GROUP/ROLE OR TO MODIFY ANY ASSOCIATED USER DETAILS. Figure 3-56: ERP User Synchronization Right click User Options Page 72 of 164

Once the Analyze command populates the screen with potential users we can review them by selecting the particular user you wish to review and clicking Details. This will open the Details dialog for the specified user (Figure 3-57). Figure 3-57: Details Dialog for Specified User All the details associated with the user are available through this dialog. Revise the details and click on OK to return to the main ERP User Synchronization dialog. Click the check-box on the left-hand side of the dialog to select the users you wish to synchronize with Insight. Then click Synchronize as shown in Figure 3-58. Page 73 of 164

Figure 3-58: ERP User Synchronization Synchronize The user names and data will then be imported into the Insight Repository. When users are first synchronized against the ERP system, the Set User Licenses dialog opens to allow you to manage License Keys and Insight Module Licenses. Using the Set User Licenses tool is covered in the Users and Groups section. Synchronize Users Ongoing Maintenance Select a Profile from the right-hand pane of the Administration Application Tool, right-click on it, and select Synchronize. Once the ERP User Synchronization dialog opens, click on Analyze. Users that have previously been synchronized are listed at the foot of the list. When the status updates to Analyzed, you can then review any differences between the ERP system and Insight (Figure 3-59). Page 74 of 164

Figure 3-59: ERP User Synchronization In the example, the users who have yet to be imported are green, the user to be updated is in orange and the user with no change is grey. To update the Repository, use the check-box on the left-hand side of the dialog to select users and then click on Synchronize. Page 75 of 164

Documents Permissions Use the Permissions Tool to manage who can do what with files, folders or any saved object such as Reusable Inquiry Objects. You can assign Permissions to groups of users or to individual named users. When you first install Insight, the default settings deny all rights (other than Read rights) to all users except for Administrators. When a new folder or document is created, the user who created it is automatically granted all permissions for that folder or document. Permissions are retained by objects that are renamed or moved and are deleted when the object is deleted. Open the Permissions Tool by selecting the Permissions Icon in the Ribbon (Figure 3-60). Figure 3-60: Permissions Icon Alternatively, right-click on an object within the Administration Application, and select Permissions (Figure 3-61). Figure 3-61: Document Permissions Page 76 of 164

Permission Types When working with Permissions, there are several Types that can be assigned. Below is a table showing the Permission Types that can be assigned. NB PERMISSION TYPE CAN CONSIST OF SEVERAL INDIVIDUAL SUB TYPES For example, the Update permission gives the rights to Write and Lock on the associated object or document. Type Consists of Description Read Read The ability to view or open the folder or document. Update Write The ability to save changes to the folder or document. Create Lock New Document The ability to lock and unlock a folder or document. The ability to save a new document within a folder. New Folder The ability to create a new subfolder within a folder. Control Rename The ability to change the name of a folder or document. Move Delete Read Permissions Write Permissions The ability to move a folder or document into another folder. The ability to delete a folder or document. The ability to view the permissions of another user or group for a folder or document. The ability to change the permissions of any user or group for a folder or document. To select and assign individual sub types, check the Show Details box within the Permissions dialog (Figure 3-62). Figure 3-62: Permissions Show Details check box The Permission Rights that you select include: Grant Deny Inherited Mixed Permission will be given Permission will be denied The right is determined by checking the group(s) that the user belongs to The selected objects have been assigned a variety of rights Page 77 of 164

User Permissions Users within Insight can belong to Groups or have Roles (within Permissions we refer to groups of users but this is interchangeable with Roles), the default and largest of which is called Everyone. When synchronizing users against an ERP system, you can choose to use either Groups or Roles within the Setting control. When assigning access rights within Permissions, you can give rights to individual users OR to group(s). Users will inherit rights from the group that they belong to, unless those rights are then expressly denied to the individual user. If a user is within multiple groups and has been assigned contradictory rights, Insight will allow any assigned right that has been granted. If a user has been assigned more rights than a group they belong to, rights will not automatically transfer to the group. Any updates made within the Administration tool, such as user permissions, will take effect immediately. Administrator Permissions At least one Administrator role must be a direct or indirect member of the Administrator Group. Users who are members of the Administrator Group are immune to permissions and therefore have access and visibility to all stored objects. NB SYSTEM OBJECTS WITHIN THE INSIGHT REPOSITORY CANNOT BE DELETED, RENAMED OR MOVED EVEN BY ADMINISTRATORS. Page 78 of 164

Document & Folder Permissions Document Permissions will specify who can do what with a document. Within the Document section of the Administrator Tool, Permissions will also define who has visibility (Read) and management access to folders. Folder Permissions To assign Permissions to a folder, select and highlight the folder you are working with and open the Permissions dialog (Figure 3-63). Figure 3-63: Folder Permissions Dialog Page 79 of 164

From the left-hand pane of the Permissions dialog, select the User Group or individual User you are assigning the right to, and then right-click on the Permission Type that you want to assign and select Grant (Figure 3-64). Figure 3-64: Granting Permissions right-click To remove an already enabled right, select the option Deny (Figure 3-65). Figure 3-65: Deny Permissions You can use the dialog continuously to assign rights to users. Rights can differ between users and groups. When you have completed all of your changes, click the OK button. Page 80 of 164

Permissions assigned to a folder are not automatically inherited by documents within the folder. However any change to the folder can be copied to the folder s contents when the action has been completed. After clicking OK, the Copy Changes dialog opens (Figure 3-66). Document Permissions Figure 3-66: Apply Permission Changes to Every Document and Subfolder Permissions can be assigned to individual Documents in the same way that they are assigned to Folders. The Permission Types available to documents are fewer than for folders; they do not have NewDocument or NewFolder permission types. When selecting documents to apply the permissions to, you can use Multiple Selection and edit simultaneously. Multiple Selections can also be applied to folders, or combinations of documents and folders. Use the control key to select individual documents or the shift key to select a range then right-click and select the permission you want to apply. Where there are contravening permissions, the option is given as mixed. Page 81 of 164

Update Links As a result of customer feedback, the new Update Links function was added to the Administration Application. It allows a user to quickly analyze multiple inquiries and uncover instances where links to other inquiries/templates are not functional. Right-click on a specific document or the entire document folder as shown in Figure 3-67, and you will see a new option called Update Links. Figure 3-67: New Update Links The new Update Links Functionality allows users to display quickly any broken links within the Object Repository (as shown in Figure 3-68). Figure 3-68: Update Links Showing Broken Links Page 82 of 164

Links can be easily changed within this dialog by highlighting the inquiry, clicking on Change Link and specifying a new inquiry to link to as shown in Figure 3-69 and Figure 3-70. Figure 3-69: Specifying a New Inquiry for the Link Figure 3-70: Modified Link Now Valid After the change, the modified inquiries link will function correctly. Page 83 of 164

Search the Repository Use this function to trace reports and documents that have been misplaced or incorrectly saved. You can save, rename, delete, etc. and use the search facility as a reporting tool for the Repository. Within Documents, click on the New Search Icon (Figure 3-71). Figure 3-71: Search Icon in Ribbon Create a Search This will open a new tab in the left-hand pane of the Administration Application Tool called Search. Within the search pane you can define the search criteria that you wish to use by selecting the value from the Add Criteria drop down and clicking on the + (add) button (Figure 3-72). Figure 3-72: Search Pane You can remove criteria from a search by clicking on the X (delete) Icon. You can also add the same criteria multiple times in order to search for more than one value. This approach will reduce the result set of a search, only showing the results where ALL criteria and values were met. When you have defined your criteria, click on the Search button. The results of your search are displayed in the righthand pane of the Search dialog (Figure 3-73). Page 84 of 164

Save a Search Figure 3-73: Search Results Save a search for reuse by clicking on the Save button and using the File Save dialog to name and locate where you want to place the search. To open an existing search, navigate to the saved search within the Main tab/ Documents folder on the left-hand pane of the Administration Application Tool. If the file is not showing, you may need to click on the Refresh Icon. Right-click on your saved search and then select Open. The search will open in a new left-hand pane tab. Click Search to run the search (Figure 3-74). Figure 3-74: Saved Search To close a search, right-click on the tab header, and select Remove Tab Page (Figure 3-75). Figure 3-75: Remove Search Tab Page 85 of 164

Export Search Results to Excel You can export the results of your search to a spreadsheet compatible file (CSV), by right-clicking within the right-hand pane of the Administration Application Tool and selecting Save List (Figure 3-76). Figure 3-76: Right-click Save List Option The File Save dialog allows you to name and locate where you want to save the results. On clicking Save, the file will automatically launch within MS Excel (if installed). Page 86 of 164

Import/Export The Import/Export function within the Insight Administration Tool allows you to manage data between different Insight repositories. If you are able to connect to both Repositories simultaneously, then you can also use drag-and-drop (or copy-and-paste) items between them. Select Import/Export in the left-hand pane of the Administration Application Tool and the Ribbon bar will display functional icons (as shown in Figure 3-77). Importing to the Repository Figure 3-77: Import/Export Ribbon Insight uses Repository Data Files (RDF) to store Repository information. To review a Repository Data File, you can use the Open File Icon on the Ribbon (Figure 3-78). Figure 3-78: Import Open File Icon Alternatively, right-click on Import/Export and select Open File (Figure 3-79). Figure 3-79: Import Open File Option Using Right -click From the Open File dialog, navigate to and select the RDF file and click Open. Page 87 of 164

This will open the Repository within the Import/Export tree (Figure 3-80). Figure 3-80: Opening a Repository within another You can then select and copy Documents across to the main Repository. If you wish to add all elements of one Repository Data File to another, use the Restore function (covered later in this chapter). Exporting from the Object Repository Use the Export function to select and save single and multiple Repository elements to a Repository Data File (RDF). To Export the entire Repository, use the Backup function (see later in this chapter). Select Import/Export from the left-hand pane of the Administration Application Tool and click the Begin Icon. Alternatively, right-click on Import/Export, and select Begin Export. A BLANK Repository then opens within the Import/Export tree. Use this to paste or drag-and-drop the Repository elements that you want to export. For example, you may want to export two connections, one profile and a folder of Report documents. If you want to start a new BLANK Repository you can remove your changes and start again by clicking the Clear Icon. This will empty the Import/Export tree on the righthand pane of the Administration Application Tool. When the Save file dialog opens, name and select a location to store the Repository data. Page 88 of 164

Export Directly from the Repository If you want to export single elements from the Repository, you might prefer to work directly from the Repository by selecting the element (for example User Folders) then using right-click to select Export (Figure 3-81). Figure 3-81: Exporting Directly from the Repository When the Save file dialog opens, name and select a location to store the data. Backing Up an Object Repository To backup the Repository you have created, select the Repository you want to backup and click on the Backup Icon on the ribbon (Figure 3-82). Figure 3-82: Repository Backup Page 89 of 164

Alternatively, you can select the Repository from the left-hand pane of the Administration Application Tool and right-click to select the Backup function (Figure 3-83 Figure 3-83: Repository Backup The Backup function will create a Repository Data File (RDF). After clicking on Backup, the Save file dialog will open and you can specify the name for the backup and the location to save it in. To install a Backup file, use either the Import function to review and copy the Repository to a new one, or the Restore function to add it to a new Repository. Page 90 of 164

Restoring an Object Repository Use the Restore function to add an existing Repository to a new one. Create a New Repository or Open one that you wish to add to. Right-click on the Repository, and select Restore (Figure 3-84). Figure 3-84: Repository Restore When the Open File dialog opens, navigate to and select the Repository Data File (RDF) you want to restore. Click OK. The Repository being restored will then be appended to the open Repository. Any incompatible files will be reported through a message dialog. Page 91 of 164

Logging The logging facility records events including who did what, when and to whom. Basic logging is enabled automatically in all new repositories within the Repository itself and is stored in a table created automatically. The log will record when an inquiry object has been edited, but cannot record the details of what changed (for example formats or calculations). Default Logging Any new Repository created with Version 9 will have a new directory called Logging. This directory contains one Log Stream called Default, shown below in Figure 3-85. Figure 3-85: Default Log Stream NB THE LOGGING DIRECTORY CAN CONTAIN MULTIPLE LOG STREAMS WHICH CAN BE ENABLED/DISABLED FOR DIFFERENT LOGGING SCENARIO S. LOG STREAMS CAN BE TREATED LIKE ANY OTHER OBJECT WITHIN THE REPOSITORY, IN THAT THEY CAN BE CREATED, RENAMED, DELETED, COPIED ETC. Page 92 of 164

Configuring the Log To edit a Log Stream, right click on the Default Log Stream provided with the repository and select Edit. The Log Stream Configuration dialog will be displayed as per Figure 3-86. Figure 3-86: Log Stream Configuration Dialog NB WHEN EDITING A LOG STREAM THAT IS USED TO LOG ADMINISTRATION APPLICATION ACTIVITY, REMEMBER TO RESTART THE ADMINISTRATION APPLICATION FOR THE CHANGES TO BE CORRECTLY APPLIED. Page 93 of 164

The Log Stream Configuration dialog allows you to Enable/Disable the individual Log Stream via the Status tick box. It is recommended that you do not delete a Log Stream but disable it should you wish to re-enable the logging later. The Category section of the Log Stream Configuration dialog allows for logging to be targeted on very specific situations. The Severity drop down control specifies the level of information being recorded by the log stream. NB BE AWARE THAT SETTING THE CATEGORIES TO ALL OR SETTING THE SEVERITY TO THE DEBUGGING LEVEL CAN SUBSTANTIALLY INCREASE THE NUMBER OF LOG ENTRIES RECORDED, WHICH WILL IMPACT THE PERFORMANCE OF INSIGHT AND THE ADMIN TOOL. IT IS RECOMMENDED THAT THESE LOGGING SETTINGS ARE ONLY USED FOR SPECIFIC SITUATIONS AND ARE NOT ENABLED CONTINUOUSLY. The User field allows the selection of one User for logging (Groups cannot be selected). Click on the Icon to open the Select User dialog shown in Figure 3-87. Select a User and click OK to return to the main dialog. Figure 3-87: Select User Dialog The Machine field allows the entry of a PC name so that only activity originating from that PC is logged. Page 94 of 164

Viewing the Log The log can be viewed from the Administration Tool by choosing the View History command on any object as per Figure 3-88. Figure 3-88: View Log History The View History dialog shown in Figure 3-89 provides a way of looking for all logged activity for the previously selected object. For the example shown, the selection of the Document folder has populated Document in the Document Filter. However the pre population of filters will work with inquiries, templates, report packs, reusable inquiry objects, or profiles. NB ADMINISTRATORS ARE AUTOMATICALLY ENTITLED TO USE THE VIEW HISTORY DIALOG. NON- ADMINISTRATORS MUST BE GRANTED THE LOGGING CAPABILITY IN ORDER TO GET ACCESS TO THE DIALOG. Page 95 of 164

Figure 3-89: View History Dialog The View History dialog provides functionality to order and filter the logged events. Some of these filters match the ones provided in the Log Stream. These filters/options are: Severities: This can be set to narrow down the logged events to the required Severity level of Errors, Warning, Information or Debug specified in the Log Stream(s) Categories: This can be set to narrow down the logged events to the Categories specified in the Log Stream(s) Document: This can be set to narrow down the logged events by Document or Document Folder text. The logged events can be further narrowed down by using the associated drop down control s options of Equals, Begins With, Contains and Ends With. o For example, Begins With if used in conjunction with Document would return all the logged events associated with all documents, reports and templates stored within the Documents folder. Message: This can be set to narrow down the logged events by searching on specific text within the Message Column. The logged events can be further narrowed down by using the associated drop down control s options of Equals, Begins With, Contains and Ends With. Sort By: This can be set to order the logged events. Any of the associated filters can be selected and can be sorted by enabling/disabling the Descending tick box. Page 96 of 164

From Date/To Date: This can be set to narrow down the logged events by date ranges in each of these controls. If you click on the Downwards icon, you will be presented with the control shown in Figure 3-90. Figure 3-90: From Date Control o To restrict the amount of data please note that the logged events are initially limited to the last year s data through a predefined value in the From Date (this can be overwritten). User: This can be set to narrow down the logged events by searching on the specific user making the changes. (Useful when multiple users are accessing the same repository) Profile: This can be set to narrow down the logged events by searching on the specific Profile. (Useful for diagnosing whether issues are related to a Profile configuration issue). Code: This can be set to narrow down the logged events by searching on the specific Code that is included within a Categories group. o Categories are grouped in a tree structure. Within Repository and Logins is the 10024: User Authentication failed code, which can then be narrowed down by the Code filter. Log Stream: This can be set to narrow down the logged events by searching on the specific Log Stream. (Useful when one Log Stream provides more information than normal). Machine: This can be set to narrow down the logged events by searching on the specific Machine (PC/Server). Click on Run Query to refresh the logged events displayed in the lower half of the dialog. The View History dialog also allows the users to export the logged events via: Copy: This will copy any highlighted records into the local computers clip board, allowing the user to paste these records into an appropriate program Save: This will save all displayed Logged Events into a CSV file for later analysis Page 97 of 164

Deleting History The Log Data can be purged via the Delete History functionality. Individual objects within the repository can have their Logged Events purged or alternatively this can be done by individual Log Streams as per Figure 3-91. Figure 3-91: Delete History Figure 3-92 shows the Delete History dialog. Figure 3-92: Delete History Dialog Page 98 of 164

The purging of log entries can be deleted either by the Selected stream only or alternatively by All Streams. You can choose to delete log entries up until a certain date or turn the date off in order to delete all entries. Please note that the date specified is from a year ago. When you click OK you will be told how many log entries were deleted. Figure 3-93: Log Entries Deleted Page 99 of 164

Reusable Inquiry Objects Manage the Reusable Inquiry Objects within the Administration Tool by creating New Folders and defining User Permissions. Create a Reusable Inquiry Objects (RIO) Folder Select RIO in the left-hand pane of the Administration Application Tool and within the Global tree, right-click and select New and then Folder (Figure 3-94). Figure 3-94: Creation of Folders within RIO Structure Name the folder and use the Permissions dialog to define which users can Save/ Copy/ Rename and Delete within it. These steps can be repeated to generate folders within the Profile-related Reusable Inquiry Objects Folders (these are created at the same time as their associated Profile). NB IT IS RECOMMENDED THAT YOU HAVE SOME FORM OF FOLDER STRUCTURE WITHIN RIO TO ORGANIZE THE REUSABLE INQUIRY OBJECTS. Page 100 of 164

Users and Groups Set User Licenses When users are first synchronized against the ERP system, the Set User Licenses dialog allows you to manage License Keys and Insight Module Licenses. For more information on how to bring users into the Repository, please see Import and Synchronize ERP Users. To access the Set User Licenses dialog, select Users & Groups from the left-hand pane of the Administration Application Tool and click on the Assign Licenses Icon (Figure 3-95). Figure 3-95: Assign Licenses Alternatively, right-click on Users & Groups and select License Assignments (Figure 3-96). Figure 3-96: Users and Groups License Assignment Page 101 of 164

Figure 3-97 displays the Set User Licenses dialog. For each License Key selected, the module information is summarized in the rows In Use, Available, and Total Available at the bottom of the table. Assigning Modules to Users Figure 3-97: Set User Licenses Assign modules to users by checking the relevant box in the table, either individually or using the Mass Selection tool (click-and-hold on a cell to the left of the module check-boxes and use the mouse to drag the selection across the modules cells that you want to update). See Figure 3-98 below. Figure 3-98: Mass Selection for License Assignment The cells will be highlighted in blue, and you can then check or uncheck any cell within the selection to update all of the selected cells. Page 102 of 164

Exporting the License Assignment Table Click on the Excel Export button to generate an MS Excel Worksheet. You will be prompted to enter the name and location where the worksheet will be saved. When you review the file in Excel, the check boxes appear as True when checked and False when unchecked. License Key Management The License Key management dialog allows you to Add new License Keys, and when upgrading, use the Replace button. When using Replace, your existing License assignments are kept, and the new Key validates that it can accommodate all of your current License assignments. You can access the License Key Management dialog in several ways: Within a Repository, select Users & Groups on the left-hand pane of the Administration Application Tool and click on the Manage Keys Icon that is active in the Ribbon Bar (Figure 3-99). Figure 3-99: Manage Keys Alternatively, you can right-click on Users & Groups within a Repository and select License Keys (Figure 3-100). Figure 3-100: License Keys within Users and Groups Page 103 of 164

If you are working within the Set User Licenses dialog you can access the License Key Tool by clicking on the Manage button (Figure 3-101). Figure 3-101: Manage License Keys The Manage License Keys dialog opens. Listed will be all existing License Keys with their properties (Figure 3-102). Figure 3-102: Manage License Keys NB BE AWARE THAT FOR BACKWARDS COMPATIBILITY WITH PREVIOUS VERSIONS, THE KEY NAME OF DEFAULT NEEDS TO BE RETAINED FOR YOUR PRIMARY KEY (I.E. NON-TRIAL KEY). Page 104 of 164

Upgrade your License Key If you are installing Insight on a server that is also being used for a production installation of a previous version of Inquiry Suite, we recommend for backwards compatibility that you retain the License Key name of 'default'. To upgrade your License Key, select the key that is being replaced and then click on the Replace button (Figure 3-103). Figure 3-103: Replace a License Key When the Replace dialog opens, you can copy and paste to insert the new License Key. Click OK to validate the new key against your current License assignments (Figure 3-104). Figure 3-104: Replace License Key dialog A replaced License Key cannot revoke any existing Licensed Modules. Therefore, if an incompatible License Key is used, a message dialog opens to show you which Modules are not accommodated (Figure 3-105). Click OK to close the message; the License Key will not be updated until the license assignments are changed as required. Page 105 of 164

Figure 3-105: Incompatible License Key used in Replacement A valid replacement License Key will automatically update the registry and be reflected in your License Assignment tool. Add a new License Key If you are testing a new version of Insight, you may receive a trial License Key. You will need to add this separately from your default License. Add a new License key by clicking on the Add button. This will open the Add License Key dialog. After entering a unique name for the test, you can copy and paste to insert the trial License Key (Figure 3-106). Figure 3-106: Add License Key Click OK to insert the new License Key. Use the Set User Licenses dialog to assign any additional module(s) from the new License Key. NB THE LICENSE KEY MANAGEMENT TOOL WITHIN THE ADMINISTRATOR APPLICATION MUST BE USED TO MANAGE LICENSE KEY ADDITIONS AND AMENDMENTS. DIRECT MANIPULATION OF THE REGISTRY KEYS AND DIRECTORIES WILL LEAD TO PROBLEMS WITH OLDER INQUIRY SUITE APPLICATIONS. Page 106 of 164

User Capabilities Use the Capabilities function to manage access to functionality for users. You can also use this to assign limited functional rights within the Administration Tool to nonadministrators. The tool also allows you to manage users other abilities within Insight, such as being able to export data, build Hierarchies and Time Series, and other functional elements where you may wish to restrict capabilities to trained or authorized users. Open the Capabilities dialog by selecting the user or group of users you wish to assign functional rights to and then right-click and select Capabilities (Figure 3-107). Figure 3-107: Capabilities Page 107 of 164

The Capabilities dialog opens with default settings, allowing users to manage all Insight features (as shown in Figure 3-108 ). Uncheck the box of any feature you want to be disabled for the selected user(s). Figure 3-108: Set Capabilities Feature Control Manage the Print/Export and Budgeting functionality by clicking on the relevant tab as shown in Figure 3-109. Click OK to save the settings. Figure 3-109: Set Capabilities Administration Use the Administration tab to grant users capabilities within the Admin tool. Click OK to save the settings. Changes take effect immediately. Use the Advanced button to make amendments to specific elements of Insight. Page 108 of 164

Password Policy Use the Administration Tool Password Policy functionality to define and manage Password protection for all of your Insight users. A Password Policy can be set for any group, and will then apply to all users and sub-groups within that group. A password policy defined for Everyone can be overridden by a policy set at a lower level. The Password Policy options, such as minimum length, are enforced only when a password is being changed they are not retroactive. Password Policy is set to some minimum defaults at start-up and will cascade down the User Group tree. To update these, navigate to Users and Groups and select the Group Everyone. Click on the Password Policy Icon or right-click and select Password Policy (Figure 3-110). Figure 3-110: Password Policy Page 109 of 164

The dialog Password Policy dialog opens. Use the check-boxes to set and define any additional password criteria. Click OK to make the changes (Figure 3-111). Figure 3-111: Password Policy Dialog Page 110 of 164

Manually Managing User Groups Creating a New Group If you decide not to use the Synchronize Users tool within the Administration Tool, then you can manually create Users and Groups. Within Users and Groups in the left-hand pane of the Administration Tool, select the group item to which the new group will belong, right-click and select New and then Group (Figure 3-112). Figure 3-112: New Group The Group Definition dialog will open. The dialog has fields to enter the name and description (optional) of the group. Click OK to save the new Group (Figure 3-113). Figure 3-113: Group Definition Dialog Page 111 of 164

Editing a Group To edit a group, right-click on the group item and select Edit Group (Figure 3-114). Figure 3-114: Editing a User Group The editing interface is identical to the one that is used to create a new group, except it is not possible to change the name of an existing group. Deleting a Group To delete a group, right-click on the group item and select Delete Group. NB YOU CAN DELETE A GROUP IF IT CONTAINS SUB-GROUPS OR USERS. THERE IS A WARNING MESSAGE TO CONFIRM YOUR ACTION. YOU CANNOT DELETE THE GROUPS ADMINISTRATOR OR EVERYONE. Manually Managing Users Creating a New User If you have chosen not to Synchronize User details automatically with the ERP system, you can manually create a new user. Select the group to which the user will belong, then right-click and select New User (Figure 3-115). Figure 3-115: Create New User NB WHEN YOU SYNCHRONIZE A USER, THE SYSTEM AUTOMATICALLY ASSIGNS PERMISSIONS FOR THAT USER TO THE ASSOCIATED PROFILE. IF YOU MANUALLY CREATE A USER, YOU WILL HAVE TO MANUALLY ASSIGN PERMISSIONS FOR THE PROFILES. Page 112 of 164

The User Definition dialog has fields to enter the User Name and optionally, the first and last names (Figure 3-116). Figure 3-116: New User Definition Dialog Additionally, the administrator can force a password to expire on a certain date or force the user to change their password at the next logon. The password needs to be a valid one that follows the rules set in the password settings. For more information on password settings, see Password Policy earlier in this chapter. Editing a User To edit a user, right-click on the user item and select Edit User. The editing process is identical to the one used when creating a new user. As with groups, it is not possible to change usernames. NB YOU CAN ONLY DELETE THE ADMINISTRATOR USER WHEN THERE IS AT LEAST ONE OTHER ADMINISTRATIVE ACCOUNT AVAILABLE (OTHER THAN SYSTEM). THE SYSTEM USER CANNOT BE USED AS A LOGIN AND CANNOT BE DELETED AS IT S USED FOR INTERNAL OPERATIONS. BEFORE DELETING A USER YOU CAN REVIEW WHAT IS CONTAINED WITHIN THEIR PROFILE BY CLICKING ON BROWSE AS USER. Page 113 of 164

Browse as User If you want to review what permission and documents a user has been given access to, you can use the Browse as User function to open a new tab in the left-hand pane of the Administration Application Tool to see the folders that are visible to them. Select the user and either click on the Browse as User Icon or right-click and select Browse as User (Figure 3-117). Figure 3-117: Browse as User The user s view will open in the left-hand pane of the Administration Application Tool. This will be named after the user (Figure 3-118). Figure 3-118: Browse as User Tab If you make any changes and want to review them, use the Refresh Icon. Page 114 of 164

Module Security was created to allow greater control of what a user can see when using Insight. This feature works in conjunction with the standard security settings provided with JD Edwards products, e.g. Business Unit Security. The original Module Security feature was designed to work with the Payroll module only. However further developments within the software now allow for Module Security to be compatible with Timesheet and Human Resources modules. The feature is available within the new Administration Tool and is attached directly to a profile. By defining security conditions based on fields and values, you can choose what a user will be able to display. These security conditions can be made against a specific User ID, against a specified group or even a combination of the two. Brief examples of how the feature can be used include allowing administrative staff to see the contact details of staff while hiding their salary, or allowing the head of a department to only see the employees for whom he is responsible. Page 115 of 164

Basic Configuration Module security access is dependant upon a user fulfilling two criteria. First, the user must have Read and Update Permissions for the Profile they wish to configure. (For more information on Permissions please refer to the chapter called Permissions.) Second, the user must have the Module Security Capability. This capability is accessed by right-clicking the user or group and selecting Capabilities from the menu as shown in Figure 4-1. Figure 4-1: Accessing Capabilities Figure 4-2 shows the Capabilities dialog with Module Security enabled. Page 116 of 164

Figure 4-2: Activating Module Security Capability Once properly configured, Module Security can be assigned within a Profile with a right-click on the required Profile and then selecting Module Security from the menu as shown in Figure 4-3. Figure 4-3: Module Security Selected Within a Profile Selecting this option will display the main Module Security dialog as shown in Figure 4-4. Within this dialog, you can configure users or groups with simple Grant or Deny permissions. Page 117 of 164

It is also possible to switch between which modules are affected by Module Security by using the Choose Module drop down box. Figure 4-4: Module Security Dialog It is important to remember that users and groups will inherit permissions from their respective parent groups. (This will be explained in greater detail in Security Inheritance and Priority.) In the situation of large numbers of users or groups, we recommend that any associated groups are defined in accordance with Module Security to reduce the overall maintenance, i.e. place similar level users in similar groupings. Page 118 of 164

Using Module Security The fields which are available within Module Security are controlled using an xml table. This table can be configured by a member of the InsightSoftware.com s development team to contain any file/field combinations which you might require. This allows security to be applied to any file/field which isn t already covered by standard JD Edwards security. The software is shipped with a default selection of commonly restricted payroll fields. Over the next section, we will describe a few examples of how the feature can be configured to restrict or allow access to certain values. The examples are quite specific but the logic can be applied to any allowable fields. NB THE APPLICTION OF MODULE SECURITY ONLY COMES INTO EFFECT WHEN CREATING/OPENING A NEW INQUIRY. IF THE USER WHOSE SECURITY SETTINGS YOU ARE CHANGING IS ALREADY IN AN INQUIRY WHICH YOU WOULD LIKE TO RESTRICT, THE SECURITY WILL NOT BE ENFORCED. THE USER WOULD NEED TO CLOSE OUT OF THE INQUIRY AND THEN REOPEN IT. Page 119 of 164

Example 1: Denying Specific Values In the first example we are going to restrict a user from seeing specific employees payroll details using the Denied mode. The effect of using Module Security will be shown by comparing the results before and after changing the security. Figure 4-5: Payroll History Report before Module Security Applied In Figure 4-5 above, we have run a basic Payroll History template. The filter selections were left blank to ensure the display set was not affected. The filters were then hidden to maximize the display result set. Additionally all non-essential columns were removed. To apply module security, within the Administration Tool right-click on the profile and select Module Security. On the Choose Module drop down list, select Payroll. NB THE CHOOSE MODULE DROP DOWN LIST IS VERY IMPORTANT FOR SPECIFYING SECURITY CONDITIONS. THESE CONDITIONS ARE LINKED TO THE MODULE SO ONLY THAT MODULE WILL BE AFFECTED, EVEN IF THERE ARE SHARED FIELDS IN OTHER MODULES. Page 120 of 164

Select the User or Group to be amended. In this example we will be applying security to the Accounting Group as shown in Figure 4-6. This will affect all users within this group. Figure 4-6: Group Selection Next click the New button to the right side of the dialog window. This will display the window shown in Figure 4-7. Figure 4-7: Add Module Security Entry Dialog Page 121 of 164

Select the Field to be restricted from the drop down list. (In this example we need the AN8 record which is displayed as default.) Enter the values to which you want to apply security, as shown in Figure 4-8, and set the mode to Denied. Figure 4-8: Value Selections NB MULTIPLE SELECTIONS ARE SEPARATED WITH A COMMA. RANGES ARE SUPPORTED USING THE COLON CHARACTER. ONLY A SINGLE DEFINITION CAN BE MADE PER USER FOR ANY ONE FIELD. Click OK to save the selections and click OK again to exit back to the main dialog as shown in Figure 4-9. Figure 4-9: Current Module Security Selections Page 122 of 164

You have now applied a simple Module Security setting. Figure 4-10 shows the effect on the user after reopening the template. As you can see, the inquiry results no longer contain the Employee Numbers of 6002, 6078 and 2479, which we denied the user visibility to by using the Deny Option. Figure 4-10: Module Security Applied Page 123 of 164

Example 2: Granting Specific Values In the next example we can see the effect of using the Granted mode against specific criteria. To apply module security, within the Administration Tool right-click on the profile and select Module Security. Click on your previously entered security condition and click on Edit. Click on the Granted button, as shown in Figure 4-11. Figure 4-11: Values Granted Click OK to see the changes referenced in the dialog (Figure 4-12). Figure 4-12: Current Module Security Selections Page 124 of 164

Figure 4-13 shows that the inquiry results have now been amended so we can see only the records detailed in the Module Security dialog using the Granted option. Figure 4-13: After Module Security Settings Applied Page 125 of 164

Example 3: Suppress Label Columns Some fields can be set to suppress the display of sensitive information from a user. In this example we will suppress the display of Hourly Rate, a label column found with the Payroll History Template. Figure 4-14 shows the field before any security is applied. Figure 4-14: Hourly Rate before Security Applied Page 126 of 164

These Fields cannot be specified as in the previous examples, as the Values section of the dialog is grayed out to prevent data entry. Instead, the Values section of the dialog is populated with a * to indicate that all data returned will be affected (a select all). For this example we will apply a Denied Mode, as shown in Figure 4-15. Figure 4-15: PHRT Field (Hourly Rate) Once the Module Security is finalized, the associated user will see that the Hourly Rate (PHRT) is now suppressed as shown in Figure 4-16. Figure 4-16: Hourly Rate Hidden After Security Applied Page 127 of 164

Example 4: Suppressing Value Columns Module security also provides a way of suppressing the display of value columns. As with previous examples, you need to select the correct field from the drop down list within the Module Security dialog. In this example, we are going to restrict the Management group from viewing the Gross Pay Value Column. To specify this in Module Security, we need to use its Insight code. This code can be seen within the associated Visual Assist filter (shown below in Figure 4-17). Figure 4-17: Insight Amount Filter within the Payroll History Template NB THE FOLLOWING EXAMPLE ILLUSTRATES ONE VALUE COLUMN BEING AFFECTED. HOWEVER BY ENTEREING A * IN THE VALUE SECTION OF THE DIALOG, YOU CAN SELECT ALL VALUE COLUMNS, ALLOWING YOU TO GRANT OR DENY ALL VALUES. The Payroll History Template is based on data contained with the Employment Transaction History (F0618) and Employee Transaction Detail File (F06116) tables so this option must be selected as the applicable Field. To restrict the Gross Pay Value Column, enter the code GPA into the Values section of the dialog as shown in Figure 4-18 and click on OK. Page 128 of 164

Figure 4-18: Restricting Gross Pay Value Column As a result of the module security condition, the Gross Pay Label Column will no longer be displayed by all users in the management group. This security condition is shown in Figure 4-19. Figure 4-19: The display of Gross Pay has been suppressed NB IF YOU SUPPRESS ALL THE VALUE COLUMNS IN YOUR INQUIRY, NO DATA WILL BE RETURNED IN THE RESULT SET. TO SEE RECORDS, YOU MUST ENABLE THE ZERO BALANCES FEATURE. Page 129 of 164

Example 5: Combinations of security In the previous examples we have used single selections to Grant or Deny access to certain values. It is also possible to use multiple selections. The following example demonstrates how you may wish to grant access to a user for specific employees, but deny the user the ability to view payroll information such as Hourly Rate. For the first condition, we will repeat the condition established in the Example 1: Denying Specific Values section (Figure 4-20). Figure 4-20: First Condition For the second condition, we will repeat the condition established in the Example 3: Suppress Label Columns section (Figure 4-21). Figure 4-21: Second Condition Page 130 of 164

The module security dialog will then display both conditions (Figure 4-22). Figure 4-22: Module Security dialog with two conditions As shown in Figure 4-23, the user has been limited to the three employee s records via Granted Mode, and the hourly rate has been affected by the Denied Mode. The combination of security conditions allows for detailed and complicated authorities to be handled in a reasonably straightforward manner. Figure 4-23: Result set with both conditions applied Page 131 of 164

Advanced Security Inheritance and Priority Module Security is designed to work with large hierarchical organizational structures by allowing users and groups to inherit security conditions from their respective parent groups. The underlying security engine will combine all the levels for one particular Field. However a condition established with a Deny mode will take precedence over a Granted mode. Security Inheritance on a two level system Table 4-1 below shows how security condition priorities would be applied when security is set at the Group and User levels. Group Level Security User Level Security Result Grant 1000 Grant 2000 User can see 1000 and 2000 only Deny 1000 Deny 2000 User can see everything except 1000 and 2000 Deny 1000 Grant 1000 Denies everything; denying a specific field and setting takes precedence Grant 1000:2000 Deny 1500 User can see 1000:1499 and 1501:2000 Grant 1000 Deny * Will deny all Deny 1000 Grant * Will allow all Table 4-1: Security Priorities with Groups Configured Page 132 of 164

Security Inheritance on a three level system Table 4-2 below shows examples of how priorities would be applied when security is set on a three level system. Everyone Level + Group Level + User Level Everyone Level Security Group Level Security User Level Security Result Deny * Grant 1000:5000 Grant 7000 User can view records for employees 1000:5000 and 7000 Deny * Grant 1000:5000 Deny 3000 User can view records for employees 1000:5000 but not 3000 Deny * Deny 1000:5000 Grant 7000 User can view records for employee 7000 only Deny * Deny 1000:5000 Deny 7000 User cannot see any employee records Deny 3000 Grant 1000:5000 Grant 7000 User can view records for employees 1000:5000 and 7000 Deny 3000 Grant 1000:5000 Deny 4000 Grant * Grant 1000:5000 Grant 7000 Grant * Grant Deny 7000 1000:5000 Grant * Deny 1000:5000 Grant 3000 except for 3000 User can view records for employees 1000:5000 except for 3000 and 4000 User can view records for all employees User can view records to all employees except for 7000 User can view records for all employees except for 1000:2999 and 3001:5000. Grant * Deny 1000:5000 Deny 7000 User can view records for all employees except for 1000:5000 and 7000. Table 4-2: Security Priorities with Everyone Level and Groups Configured Page 133 of 164

Overview This section of the Administration User Guide covers the major proprietary software vendors that you might use to create a new database into which you will insert the Insight Repository. The Repository holds information stored for, and about, the users. Insight users need access to this stored information in the Repository, and the Insight application needs access to the Repository to perform processes like User Verification when the users attempt to log on. Access to the Repository requires a driver or Data Provider, such as an Open Database Connectivity (ODBC) connection from the application to the database where the Repository is located. The Data Provider is the messenger software that passes and translates information between your system and Insight. Data Providers are not restricted to ODBC you can use SQLServer Data Providers or OracleServer Data Providers (as well as others) to connect to the Repository. The Repository needs to be created on a relational database server that is available whenever the user logs on to the Insight application. The Repository contains a number of tables (files) to hold this information. The tables are created as part of the administration configuration process. These tables can be created in an existing database/schema/library, but we recommend that you create a separate database/schema/library in which to store the new tables. This database is unlikely to ever contain more than 500Mb of data and so it should not require any special configuration with regards to partitioning, etc. The database will need to be accessed by a user that has read/write permissions. No results sets from inquiries are stored in the database. Hierarchies and Reusable Inquiry Objects (RIO s) are kept in the Repository Database. Page 134 of 164

Creating a new database in Microsoft SQL Server This is done by starting up the SQL Server Enterprise Manager in the usual way and connecting to the database server where the Repository is to be created. In Figure 5-1, the local machine has been chosen as the location for the database. Figure 5-1: Enterprise Manager Select the Databases node, right-click and select New Database. The dialog shown in Figure 5-2 opens. Type in the name of the database (this can be any name required) and click on the OK button. Figure 5-2: New database dialog Page 135 of 164

Creating a New User in Microsoft SQL Server Figure 5-3: Navigating to Security Options To navigate to the Logins option, you need to select the correct server. On the lefthand panel of the screen, if you expand the Microsoft SQL Servers option and then expand the SQL Server Group, you will be a presented with a list of available servers. Select the server for which you wish to create a user. The example, Figure 5-3, shows a connection to the local SQL Server. Expand the server selection, and then need expand the Security folder. Page 136 of 164

Starting the New Login Dialog Underneath the Security folder, select the Login option, right-click (Figure 5-4) and then from the menu select New Login. Figure 5-4: New Login Menu Page 137 of 164

New Login Dialog On the general tab of the new login dialog (Figure 5-5), you need to enter a name for the new user. Select SQL Server Authentication and enter the password of your choice. You will then need to select the default database for this new user and select the database created for the Object Repository. Figure 5-5: New Login Dialog Page 138 of 164

Server Roles tab Leave the default selection (Figure 5-6). Figure 5-6: New Login Dialog Server Roles Page 139 of 164

Database Access Select the database created for the Object Repository and check the permit item from the list of databases (Figure 5-7). Select the database roles of public and db_owner. Figure 5-7: New Login Dialog Database Access When you click OK you will be asked to re-enter the new user s password. Page 140 of 164

Setting SQL Server Authentication Mode To use the created SQL Server user account, you must make sure that MS SQL Server authentication mode is set to SQL Server and Windows authentication. If the authentication mode is set to Windows authentication only, you will not be allowed to logon to the SQL Server database with the new user. To change the authentication mode, go to Windows Control Panel, double-click on the Administrative Tools Icon and then double-click on the Computer Management Icon. When the Computer Management dialog opens (Figure 5-8), navigate to the Service and Applications node and select Microsoft SQL Servers. Figure 5-8: Computer Management Dialog Right-click on your chosen server and the menu shown in Figure 5-9 will appear. Figure 5-9: Menu Page 141 of 164

If you select Properties, the SQL Server dialog opens (Figure 5-10). Select the security tab. Figure 5-10: SQL Server Properties To change the authentication mode, select the SQL Server and Windows radio button and click the OK button. Page 142 of 164

Creating a new schema in Oracle Since the process of creating new databases can be done in a variety of ways within Oracle, a step-by-step guide is not provided here. Rather, the steps are described at an abstract level and you may need to consult your Systems Administrator to complete this task. The user must either create a new, empty Oracle database or a new schema within an existing Oracle database. No tables need to be created at this time; the Repository will be populated during the software configuration process. The name of the new database is not as important as the database needing to be accessed through an ODBC data source. Creating a new library in IBM DB/2 with SQL collection There are two ways to create the library with a SQL collection: via SQL or the AS/400 Operations Navigator. The new Repository requires that Journaling must be enabled for the library (the database must allow support for database transactions) NB IT IS IMPORTANT THAT THE USER DOES NOT USE THE CRTLIB COMMAND ON THE AS/400. Option 1: Create the Library using a SQL command. When creating a library using SQL, use the CREATE COLLECTION function. Example: Create a collection called REPOSITORY. CREATE COLLECTION REPOSITORY Page 143 of 164

Option 2a: Create Libraries Using Older Versions of AS/400 Operations Navigator. When creating a library using AS/400 Operations Navigator, right- click on the library selection and select New Library from the menu as shown in Figure 5-11. Figure 5-11: New library option The new library dialog will then appear as shown in Figure 5-12. Enter the name of the new library and check the Create as an SQL collection option. Click on the OK button and the library will be created. Figure 5-12: New library dialog Page 144 of 164

Option 2b: Create Libraries Using Newer Versions of AS/400 Operations Navigator. In later versions of DB2 the dialogs have changed (Figure 5-13). The terminology has changed from Libraries to Schemas and Create as SQL collection has been removed. Figure 5-13: New Schema Dialog NB FOR CLIENTS THAT USE BUDGETING, WHEN CREATING A BUDGETING REPOSITORY, PLEASE ENSURE THAT THE ASSOCIATED SCHEMA IS NOT CREATED WITH THE OPTION CREATE AS A STANDARD LIBRARY SET. Page 145 of 164

You will use ODBC Data Sources to connect to the JD Edwards database and an IBM DB2 Object Repository. For Microsoft SQL or Oracle Object Repositories, you can also use ODBC Data Source Providers. To create a new ODBC Data Source, access the ODBC Data Source Administrator using your System Control Panel/Administrative Tools/Data Sources. When you open this application you are presented with the ODBC Administrator tool (Figure 6-1). Create ODBC Data Sources in the System DSN section rather than the User DSN section. If you create the ODBC Data Source in the User DSN section, only the current user will be able to access the ODBC connection. Figure 6-1: ODBC Data Source Administrator dialog Page 146 of 164

Select the System DSN tab then click the Add button to open the Client Access Express ODBC Setup Wizard (Figure 6-2). Figure 6-2: New data source dialog Within the New Data Source dialog, the user should choose the appropriate ODBC driver for the relational database that runs their JD Edwards system. In the example above, the Client Access ODBC Driver is selected to connect to JD Edwards World. The instructions to complete the process vary depending upon the database platform chosen. These are described below. Page 147 of 164

Creating ODBC Data Sources Create an ODBC Data Source for Microsoft SQL Server In the Create a New Data Source to SQL Server dialog, enter a Name for the new Data Source and optionally, enter a description that will help you to identify which Data Source it refers to. Enter the Server name to which the Data Source is connecting (Figure 6-3). Figure 6-3: New Data Source Dialog After completing this, you can keep default settings and click Finish to create the Data Source, or you can review and amend the default settings by clicking on the Next button. Page 148 of 164

This will open a new page with options to amend the default database that you will be working with on the server. Set this according to whether the ODBC connection is for an Object Repository or to JD Edwards database. Figure 6-4: Default database dialog Click Next (Figure 6-4) to navigate to the end of the connection wizard, making any necessary amendments to the Login criteria for the Server and default Languages. The final page of the wizard allows you to test the configuration. If your JD Edwards security tables or any other tables within your JD Edwards installation are located on a physically different machine or within a different database, you will need to set up an additional ODBC Data Source. Page 149 of 164

Create an ODBC Data Source for Oracle When creating the new Data Source, select the previously installed Oracle Driver and click Finish. NB WE RECOMMEND THE USE OF THE MICROSOFT ODBC ORACLE DRIVER, RATHER THAN ORACLE S OWN DRIVER, SINCE THERE ARE KNOWN ISSUES WITH KEEPING CONNECTIONS OPEN AFTER THEY HAVE BEEN USED. The New Data Source screen will show the Setup page. Choose a Data Source Name and Description along with a valid User Name for the Server you are using (Figure 6-5). Once the details have been completed, click on OK to return to the configuration wizard. Figure 6-5: Oracle ODBC connection If the JD Edwards security tables or other JD Edwards tables are located on a physically different machine or within a different database, you will need to set up an additional ODBC connection to this data source. Page 150 of 164

Connecting to JD Edwards using IBM DB2/400 Establishing a JD Edwards connection to a DB2/400 database is achieved by following the same steps as those taken to establish a Repository (described in chapter 4). On this occasion no new database is created; a connection is simply established to the JD Edwards data. Figure 6-6 illustrates the General tab of the Client Access ODBC setup screen. Here the name to give to the connection is specified and the database server hosting the JD Edwards database is selected. This may or may not be the same database server that hosts the Repository. Figure 6-6: IBM DB/2 Client Access setup General tab Next, click on the Server tab. This will display the dialog shown in Figure 6-7. Here it is important that the naming convention is set to SQL Naming Convention. Page 151 of 164

It is also highly recommended that the data, control and security libraries to the JD Edwards system are entered in the Library List. This is illustrated in Figure 6-7. NB IF YOU WISH TO UTILIZE THE HIERARCHIES FEATURE OF THE INSIGHT PRODUCT, IT IS NECESSARY TO ENSURE THAT THE CONNECTION TYPE IS SET TO READ/WRITE. Figure 6-7: IBM DB/2 Client Access setup Server tab Page 152 of 164

Finally, click on the Translation tab and ensure that the Convert binary data to text option has been checked as shown in Figure 6-8. Figure 6-8: IBM DB/2 Client Access setup Translation options Once all the settings have been made, click on the OK button to return to the ODBC administrator. Click OK again to return to the configuration wizard from which the new JD Edwards connection can be selected. If the JD Edwards security tables are located on a physically different machine or within a different database, the user will need to set up an additional ODBC connection to this data source. The ODBC connection is created in the same way as the data ODBC connection but the connection details will specify the data source details for the security tables. This secondary connection will then be selected as the security data source when using the configuration wizard for defining a data connection. Page 153 of 164

Creating an ODBC Data Source to the Object Repository AS400 DB2 NB IF YOU ARE STORING THE REPOSITORY ON AN AS400 DB2, YOU WILL NEED TO CREATE AN ODBC DATA SOURCE. ALL OTHER SERVERS WILL USE A.NET NATIVE PROVIDER INSTEAD. Access to the Object Repository is achieved by firstly creating an empty database within a relational database of the user s choosing, and secondly, establishing a connection to it. When the New button is pressed at the point in the configuration process where the Repository details have to be provided, the user is presented with the ODBC Administrator dialog shown in Figure 6-9. Figure 6-9: ODBC Administrator Dialog Page 154 of 164

Select the System DSN tab and click the Add button to create a new ODBC connection which will present the dialog shown in Figure 6-10: Figure 6-10: New Data Source Dialog Using the System DSN rather than the User DSN is vital for users who share PCs as connections created under the User DSN will only be available to the current user and will prohibit the use of the software by other users sharing the PC. Within the New Data Source dialog, the user should choose the appropriate ODBC driver for the relational database in which they wish to store the Repository. For example, in Figure 6-11 the Client Access ODBC Driver is selected to connect to a Repository stored within DB/2. The instructions to complete the process vary, depending upon which database platform is chosen. These are described below. Page 155 of 164

Creating Other Data Sources and Connections Creating a Data Source Repository Connection using Microsoft SQL Server When the SQL Server driver is selected, the user is presented with the dialog shown in Figure 6-11: Figure 6-11: Create a New Data Source Dialog A name for the Data Source should be entered. A description can also be useful for reconciliation purposes. The name of the server in which the Repository is located needs to be provided. This can be chosen from the drop down list. In the example shown in Figure 6-11, the local machine is hosting the Repository. To proceed click on the Next button. The next dialog that is presented is shown in Figure 6-12. Figure 6-12: Security Access Dialog Page 156 of 164

In this dialog, the user must provide a user name and password with sufficient privileges to read and write to the newly created database. Once the relevant security mechanism has been chosen, click on the Next button to continue. This will display the dialog shown in Figure 6-13. Figure 6-13: Selecting the Repository Database Here the user must check the Change the default database option and select the newly created Repository database name from the drop down list of selections by clicking on the down arrow button. Once the database has been selected, click on the Next button to continue to the final panel shown in Figure 6-14: Figure 6-14: Miscellaneous ODBC Settings Page 157 of 164

Click the Finish button to continue. All that remains is for the connection to be tested. A dialog will appear as shown in Figure 6-15. Figure 6-15: Testing the connection Click the Test Data Source button and the dialog shown in Figure 6-16 will be displayed. If there is an error in testing, contact your Systems Administrator for further assistance. If successful, click the relevant OK buttons to return to the ODBC administrator. Click OK once more to return to the wizard and choose the new connection from the drop down list. Figure 6-16: Connection results Page 158 of 164

Creating a Data Source Repository Connection using Oracle When the Oracle driver is selected, you will see a dialog similar to the one shown in Figure 6-17. Figure 6-17: Oracle ODBC Setup This dialog may vary between different versions and providers. The one shown in Figure 6-17 is the Microsoft Oracle Driver. NB WE RECOMMEND THE USE OF THE MICROSOFT ODBC ORACLE DRIVER, RATHER THAN ORACLE S OWN DRIVER, SINCE THERE ARE KNOWN ISSUES WITH KEEPING CONNECTIONS OPEN AFTER THEY HAVE BEEN USED. Provide a suitable name for the Repository connection in the Data Source Name field as well as the Service name in the Server field for the server hosting the newly created database. Once complete, click the OK button to return to the ODBC administrator. Click OK once more to return to the wizard and choose the new connection from the drop down list. Page 159 of 164

Creating a Data Source Repository Connection using IBM DB2/400 When connecting to a DB2/400 database, the user is presented with a DB2/400 ODBC dialog. This dialog may vary between different versions and providers. The one shown in Figure 6-18 is the IBM Client Access Driver. Figure 6-18: IBM DB/2 Client Access setup General Options Within the General tab, the first thing the user needs to do is to provide a name of the Repository connection in the Data Source Name field and select the name of the AS/400 system hosting the Repository database. Details of how to create the database are documented below. Page 160 of 164

Next click on the Server tab (Figure 6-19). Figure 6-19: IBM DB/2 Client Access setup Server Options Be sure to use SQL Naming Convention as the naming convention. Next, specify the newly created library name in both the SQL Default Library and Library List fields. Also, ensure that the connection type is set to Read/Write. Page 161 of 164

Finally, click on the Translation tab and ensure that you check Convert Binary Data to text as shown in Figure 6-20. Figure 6-20: IBM DB/2 Client Access setup Translation Options Once complete, click OK to return to the ODBC administrator. Click OK once more to return to the wizard and chose the new connection from the drop down list. Page 162 of 164