Trademarks 1 Prerequisites 2 COMOS Platform MS SQL Server 2005/2008 3 Oracle 4 Operating Manual 09/2011 A5E03638301-01
Legal information Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. Trademarks All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY A5E03638301-01 P 09/2011 Copyright Siemens AG 2011. Technical data subject to change
Table of contents 1 Trademarks... 5 2 Prerequisites... 7 2.1 Hardware...7 2.2 Version...7 2.3 Rights Management in the Network...8 2.3.1 The three logins...8 2.3.2 Access to the database server...9 3 MS SQL Server 2005/2008... 11 3.1 Setup of the SQL Server...11 3.1.1 Calling the SQL Server...11 3.1.2 Server properties...11 3.1.3 Creating a new database...11 3.1.4 Security...12 3.1.5 Test versions of the SQL Server 2008...13 3.2 Workstation setup (COMOS workstation)...13 3.2.1 Configuring the ODBC data source for the SQL connection...13 3.2.2 Creating additional instances for the SQL client...15 3.2.3 First COMOS login/creating a dat file...16 3.2.4 Changing the ODBC connection...16 3.3 Creating a COMOS database...16 3.4 Comprehensive domain networks...17 4 Oracle... 19 4.1 Workstation setup (COMOS workstation)...19 4.1.1 Installing the Oracle client...19 4.1.2 Installing the Oracle 11 Client...20 4.1.3 Net Service Name setup...21 4.1.4 Creating an ODBC data source for an Oracle client...22 4.1.5 Creating additional instances for the Oracle client...23 4.1.6 First COMOS login/creating a dat file...24 4.1.7 Changing the ODBC connection...24 4.2 Setting up the Oracle Server...25 4.2.1 Unicode-capable instance...25 4.2.2 Creating a new user...26 Operating Manual, 09/2011, A5E03638301-01 3
Table of contents 4 Operating Manual, 09/2011, A5E03638301-01
Trademarks 1 Trademarks Registered trademark: COMOS Operating Manual, 09/2011, A5E03638301-01 5
Trademarks 6 Operating Manual, 09/2011, A5E03638301-01
Prerequisites 2 2.1 Hardware To avoid performance losses, configure the database file system in accordance with Microsoft Support document 929491. This applies to the Microsoft SQL Server and to Oracle. You can find additional information on this topic in the "Infrastructure Planning" manual. 2.2 Version Suitable database servers Microsoft SQL Server 2000 Microsoft SQL Server 2005 Tested on Windows Server 2003 Service Pack 1 (64-bit) Microsoft SQL Server 2008 Tested on Windows Server 2008 Service Pack 1 (64-bit) Oracle, Release 10.g Tested on Windows Server 2003 Service Pack 1 (64-bit). An Oracle 10 client on Windows XP (32-bit) was used on the counter side. Oracle Release 11G R1 Tested on Windows Server 2008 SP1 64-bit. A client on XP SP3 (32-bit) was used on the opposite side. Operating Manual, 09/2011, A5E03638301-01 7
Prerequisites 2.3 Rights Management in the Network 2.3 Rights Management in the Network 2.3.1 The three logins Client/server structure If you are working with an Access DB and the database is a local one, then you have nothing to do with the management of network rights. However, the normal case is a different one: The individual users have installed the COMOS software on their PCs ("workstations"). The user is not an administrator, neither on the PC nor in the network. The data is managed centrally in the network. Thus, the PCs of users are "clients" and access a common "server". Here, you can further differentiate between two kinds of information: Everything that is referred to as an "object" in COMOS originates from the actual database. The server on which the COMOS database is located is called the "database server". Everything that is indicated as a "Document" or "File" in COMOS is stored independently as a physical file and saved in the "Document folder". This document folder may be located on the database server. However, the document folder can also be located on a separate server, which is then called "Document Server" or "File Server". Login types In the above case (clients with access to a database server and access to a file server), there is not just one login, but rather three, during the COMOS start which is often unnoticed by users: 1. Login to the client on database server To do this a kind of "network user" (a so-called "System DSN") must be set up on the client in the "ODBC data sources administrator". (Exact description in the following sections). The counterpart to this occurs in the user management of the database server: there, a user is set up with exactly the same name as the login ID of the "System DSN" on the client. This user then gets the required rights to the database server. 2. Login to the file server Usually the user of the workstation gets the necessary rights on the file server. 3. Login to COMOS (the "Comos login") Only at this point does the COMOS rights administration take effect. 8 Operating Manual, 09/2011, A5E03638301-01
Prerequisites 2.3 Rights Management in the Network 2.3.2 Access to the database server Saving the password COMOS uses a System DSN to find a data source. But login ID and password are normally not taken from the System DSN and are mostly ignored in the other settings of the System DSN as well. The password is taken from an encoded dat-file. Advantages It is sufficient if one administrator knows the password. The administrator generates this file once and then distributes it to all clients. The password can be easily changed later for all clients, since only the dat file has to be replaced. The ODBC administrator on the clients does not need to be started. Procedure A typical procedure for this would be as follows: The administrator installs the database server and the clients. The administrator creates a System DSN on a client, as described below. The administrator logs into COMOS on the same PC and now searches for the System DSN and then for a suitable dat-file. At this point, there is still no dat-file, therefore the login window for the login to the database server appears in Comos. The administrator enters the login ID and password here. If COMOS can log into the database server with this information, it automatically generates an encoded dat-file as described below. This dat-file is station-independent and can be distributed by the administrator. On all other clients, the users (or administrator) still needs to generate the System DSN. Directly after that, the administrator can distribute the dat-file generated in the above step. Consequently, no login window appears in COMOS and the users do not need a password. You can find additional information on this topic in the "Network security" manual. Operating Manual, 09/2011, A5E03638301-01 9
Prerequisites 2.3 Rights Management in the Network 10 Operating Manual, 09/2011, A5E03638301-01
MS SQL Server 2005/2008 3 3.1 Setup of the SQL Server 3.1.1 Calling the SQL Server 1. Select the "SQL Server Management Studio" option in the Windows Start menu. 2. Connect to the SQL server. 3.1.2 Server properties 1. Click the "Properties" command in the context menu. 2. The dialog window opens. Select the "Security" page. 3. In the "Server authentication" area, activate the option "SQL Server and Windows authentication mode". 3.1.3 Creating a new database With the current SQL Server there is a folder called "Databases". 1. Select the "New database..." command in the context menu. 2. The "New database" window opens. "General" page 1. Enter a name in the "Database name" field. This name is automatically transferred to the "Database files" table as a local name. Additionally a log file is generated. Operating Manual, 09/2011, A5E03638301-01 11
MS SQL Server 2005/2008 3.1 Setup of the SQL Server 2. "Database files" table In the "Initial size (MB)" column, set the value to > 2048 MB. Click the "..." button in the "Automatic file growth" column. A new window opens. Activate the following options here: "Activate automatic file growth" "By percent:" Enter a value between 5 and 20 in this field. "Unrestricted file growth" Please ensure that you scale down the transaction log file in good time (either manually or automatically). Generally, it can only be scaled down if the file has previously been saved. "Options" page 1. Select the "Simple" entry from the "Restore model" list. This means that no restore point is set. Advantage: The compilation of the database is concluded faster. 3.1.4 Security 1. Open the "Security" folder. 2. Go to the "Logins" subfolder and select the "New login..." command in the context menu. 3. The "Login - New" window opens. "General" page 1. Enter a name in the "Login name" field. 2. Activate the option "SQL Server authentication". 3. Select the relevant entry from the "ComosDB" list. 4. Select a language from the "Standard language" list. "Server roles" page 1. Activate the option "public". "User assignment" page 1. Activate the desired database. 2. Activate the options: "public" and "db_owner". 12 Operating Manual, 09/2011, A5E03638301-01
MS SQL Server 2005/2008 3.2 Workstation setup (COMOS workstation) 3.1.5 Test versions of the SQL Server 2008 SQL Express SQL Express is a free test version for a database size of up to 4 GB. With its default settings, SQL Express cannot be used with COMOS. The following needs to be checked and changed if necessary: The TCP/IP is disabled as a default and has to be activated. The standard SQL Port 1433 is not used. The corresponding port has to be considered when setting up the client. The "SQL Server Browser" service is deactivated by default and needs to be activated. The above-mentioned items can be evaluated and changed by means of the "SQL Server Configuration Manager". SQL Server developer version This version provides the complete scope of services of the SQL Server for testing and developer purposes. The use for production purposes is not permitted according to the licensing agreement. 3.2 Workstation setup (COMOS workstation) 3.2.1 Configuring the ODBC data source for the SQL connection The ODBC entry is only used as the basis for a number of values that are needed at another point. Data communication no longer takes place via the ODBC connection but instead via ADO. You can enter ODBC connections in either the system DNS or the user DNS. The difference is that with the system DNS the entries you make are valid for all workstation users. By contrast, entries in the user DNS are only valid for the specific user who has created them. COMOS reads the user DNS entries first before moving on to the system DNS entries. This means that if an entry exists in the user DNS, only this entry appears in the database selection. Windows XP 1. Select "Control Panel > Administrative Tools" from the Windows Start menu and start the ODBC Manager. 2. Click the "Add" button on the "System DSN" tab. 3. Select the "SQL Server" driver from the list. 4. Click the "Finish" button. Operating Manual, 09/2011, A5E03638301-01 13
MS SQL Server 2005/2008 3.2 Workstation setup (COMOS workstation) "Microsoft SQL Server DSN configuration" window The "Microsoft SQL Server DSN configuration" window opens. The configuration assistant guides you through the process of creating an ODBC data source. 1. Make the following settings "Name" field: pt_sql_server "Description" field: You can enter optional text here. "Server" list: <Name of the SQL Server in the network> 2. Click "Next >". Authenticating the client The next window is used to authenticate the client. 1. Make the following settings Activate the "With SQL Server authentication based on...": option "User name" field: Freely selectable "Password" field: Will not be evaluated Please note that due to compatibility reasons, the user name "Comos" or "comos" is not available. If you use this login ID, COMOS attempts to log in without a password. A password can be entered, but it has little meaning here. It is only evaluated for the concluding test (see "Testing the data source", p. 2-21). Instead, a login window opens when COMOS starts or the password is taken from a dat file. See section: First COMOS login/creating a dat file (Page 16). "Client configuration" button 1. Click the "Client configuration" button. 2. Activate the TCP/IP options. 3. Click the "OK" button. 4. Click the "Next" button. Changing the ComosDB 1. In the next window, activate the option "Change ComosDB to". 2. Select your ComosDB from the list. 3. Click the "Next" button. Finishing the configuration process 1. Click the "Finish" button in the next window. 14 Operating Manual, 09/2011, A5E03638301-01
MS SQL Server 2005/2008 3.2 Workstation setup (COMOS workstation) "ODBC Microsoft SQL Server Setup" window In the "ODBC Microsoft SQL Server Setup" window, all the data source settings are listed together again. Testing the data source To start testing, click the "Test data source..." button. In the "SQL Server ODBC data source test" window, the following message must be displayed: "TESTS COMPLETED SUCCESSFULLY". 3.2.2 Creating additional instances for the SQL client There is also the option to create instances for SQL servers. This enables you to select the desired server during login to COMOS without having to switch within the ODBC administrator. Select "Control Panel > Administrative Tools" from the Windows Start menu and start the ODBC Manager. Go to the "System DSN" tab. Here you add a data source of the type "SQL Server". Repeat the described procedure with the following values in the "Microsoft SQL Server DSN configuration" window: Instance1 Name: pt_sql_server_1 Description: Any Instance2 Name: pt_sql_server_2 Description: Any Instance3 Name: pt_sql_server_3 Description: Any Instance3 behaves differently. COMOS does not save a password file. See also First COMOS login/creating a dat file (Page 16) Operating Manual, 09/2011, A5E03638301-01 15
MS SQL Server 2005/2008 3.3 Creating a COMOS database 3.2.3 First COMOS login/creating a dat file The information generated above in the system DSN is not sufficient for COMOS. Additionally a search for a dat file is conducted: "<Installation directory>\comos\config\sqlpwd.dat". If instances are used: "sqlpwd_1.dat", "sqlpwd_2.dat" The password for the server login, not the COMOS login is stored in this dat file. If COMOS does not find this dat file, a login window is displayed in which you can enter the login ID and password. If you know the password, COMOS can use this information to log into the database server. COMOS then automatically generates an encrypted dat file. When you start COMOS subsequently, an additional login window for logging into the database server will no longer be displayed. Alternatively, if you have administrator rights, you can generate a dat file and install it on the clients. In this case, no additional login window will be displayed even when COMOS is started for the first time. The instance "pt_sql_server_3" behaves differently. The dat file is not stored permanently. For this instance, the user name and password are requested for every login. 3.2.4 Changing the ODBC connection If the "User DSN"/"System DSN" is changed (and especially if another database is selected to serve as the source), the dat file has to be manually deleted. Afterward, the procedure described above for creating and distributing a dat file must be repeated. 3.3 Creating a COMOS database Before you can create the COMOS database, you first have to create a raw database. See also section Calling the SQL Server (Page 11) and section Workstation setup (COMOS workstation) (Page 13). After you have installed COMOS, start it via the Windows Start menu "Programs > Comos > 92". 1. From the list, select the field "Instance: Instance 1 (ComosTest)". 2. Confirm with "Open". 3. In the next window, confirm your selection by clicking the "Yes" button. Tables / indices are now created. 4. In the next window, you receive the message "The format of the database is now correct". Click the "OK" button to confirm. 5. If you receive the message "Database indices generated" and confirm it with the "OK" button, this also means that the database has been created successfully. 16 Operating Manual, 09/2011, A5E03638301-01
MS SQL Server 2005/2008 3.4 Comprehensive domain networks The following tables are displayed on the database server: However, they are still empty. In order to work with the database, the Access database which is on the CD has to be exported into the empty database as a source. In order to create an engineering project, the system and base project should be exported at the very least. You find additional information on this topic in the "Basic Operation" manual, keyword "Importing and exporting projects". After that a database adjustment should be conducted. You will find additional information on this topic in the "COMOS Administration" manual, keyword "Adjusting the database version". 3.4 Comprehensive domain networks It is possible for COMOS clients to be located in a different domain than the SQL server. Restriction If the server name also exists in its own domain, then only one of the two servers is accessible. Example: If following servers exist: "sqlserv.comos.de" and "sqlserv.example.de" This means that a client, for example "cw66-01.comos.com", can only access either "sqlserv.example.com" or "sqlserv.comos.com". Initial situation Normally the full server name has to be entered in the ODBC settings under "Server". For the above example, with access to an external domain server the name would be "sqlserv.example.de". Database access via ADO does not use dots (.) in names. That is why ADO tries to access "sqlserv". Since the domain is missing for that case, the server only searches its own domain ("comos.de") and the name resolution of the DNS server fails: The correct server is not found, instead an incorrect server is addressed. Operating Manual, 09/2011, A5E03638301-01 17
MS SQL Server 2005/2008 3.4 Comprehensive domain networks Solution An entry in the file: "%systemroot%\system32\drivers\etc\hosts" Example file content: # Copyright (c) 1993-1999 Microsoft Corp. # This is a HOSTS example file, which is used by Microsoft TCP/ IP # for Windows 2000. # # This file contains assignments of IP addresses to host names. # Every entry must be in a separate line. # The IP address should be placed in the first column, followed by the associated# host names. # The IP address and the host name must be separated by at least one # one space character. # # Additional comments (as in this file) can be added in single # lines or after the computer name, but must be separated by # the '#' character. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost To enable COMOS to access "sqlserv.company.com", enter the IP address of "sqlserv.company.com" followed by "sqlserv": "127.0.0.1 - localhost" "156.32.17.2 - sqlserv" Windows now does not query from the DNS server which IP address "sqlserv" has; instead, it looks in this file first and selects the specified IP address directly. 18 Operating Manual, 09/2011, A5E03638301-01
Oracle 4 4.1 Workstation setup (COMOS workstation) 4.1.1 Installing the Oracle client An Oracle database server can only be accessed if an Oracle client has been installed. For the Oracle database server you require the registration data. Contact your local administrator to obtain this information. Starting the Oracle installation process 1. Insert the Oracle CD for Windows into the CD drive. 2. The CD starts automatically. Select the option "Begin installation". 3. The "Oracle Universal Installer: Welcome" window opens. Click the "Next" button. Selecting the installation type As of COMOS 9.0, this recommendation only applies to a limited extent. In COMOS 9.2, the Oracle database is accessed using a new technique. If you select the "Runtime (233MB)" option, then in some cases the "Provider not found" error message is displayed. The precise background of the error message is still being analyzed. It is likely that not all components required by COMOS 9.2 are installed. In particular, the Oracle OLEDB seems to be missing. If the "Runtime (233MB)" option causes the above error message, then there is the following workaround: Install the Oracle client with the "Administrator (551MB)" option. 1. Activate the required option. 2. Click the "Next" button. Presettings First some information for the installation has to be provided: 1. For the storage location, accept the suggested directory and click "Next" to confirm. 2. In the "Available Product Components" window activate the "Oracle Windows Interface" option. Operating Manual, 09/2011, A5E03638301-01 19
Oracle 4.1 Workstation setup (COMOS workstation) 3. Deactivate all options except "Oracle ODBC Driver" and "Oracle Provider for OLE". 4. The "Oracle Data Provider for.net" option is currently not required. 5. Activate the option "Oracle Net". 6. Click the "Next" button. Checking the requirements 1. The "Oracle Universal Installer: Product-specific prerequisite checks" window opens. Click the "Next" button. 2. The "Oracle Universal Installer: Overview" window appears. Click the "Install" button. 3. The installation process is performed in the next window. The way to proceed depends on the configuration of your Oracle server. In this example a Net Service Name is created. Configuration assistant You can use the configuration assistant to configure and start up previously selected components. 1. In the first window, "Oracle net configuration assistant: Welcome", click next. 2. To complete the Oracle Net configuration, click the "Next" button again. 3. In the next window, "Oracle net configuration assistant: Completed", click "Finish". 4. In the next window, "Oracle Universal Installer: End of installation", click "Finish". 5. If you really want to exit the program, click the "Yes" button in the "Exit" window to confirm your selection. 4.1.2 Installing the Oracle 11 Client However, the installation is suitable for COMOS version 9.0 Update 190 or higher. Procedure To install the Oracle 11 Client, proceed as follows: 1. Start the installation. 2. In the "Welcome" window click the "Next" button. 3. Select your desired installation type from the "Installation type" window. 4. Click the "Next" button. 5. In the "Specify details of default directory" window enter your desired installation directory and software directory. You can also simply accept the already displayed directories. 20 Operating Manual, 09/2011, A5E03638301-01
Oracle 4.1 Workstation setup (COMOS workstation) 6. Click the "Next" button. The installation program checks whether the minimum requirements for the installation are met. 7. When the check is complete, click the "Next" button. 8. In the "Available Product Components" window activate the "Oracle Windows Interface" option. 9. Under the "Oracle Windows Interface" option deactivate the following subordinate options: "Transaction server" "Oracle Objects for OLEDB" "Oracle Providers for ASP.NET" "Oracle Data provider for.net" 10. Activate the "Oracle Net 11" option. A second option is automatically activated. 11. Click the "Next" button. The "Overview" window shows an overview of your selected installation settings. 12. Click the "Install" button. A progress bar is displayed, indicating the status of the installation. As soon as the installation is complete, the "Installation complete" window is displayed. 13. Click the "Exit" button. Configuration After a successful installation, configure the connection to the database as usual with the Oracle Net Manager or with the Net Configuration Wizard. Then specify the connection type in the Oracle Net Manager. To do so, select "Dedicated server" item from the "Connection type" list. Save your settings and close the Oracle Net Manager. 4.1.3 Net Service Name setup A Net Service Name allows identification and connection via an Oracle database. After the installation start the Net Configuration Assistant via the Windows Start menu "Programs > Oracle > OraClient10g... > Configuration and Migration Tools >...". Requirements In the course of the configuration process, you need such information as "Service name" or "Host name" from your Oracle administrator. Operating Manual, 09/2011, A5E03638301-01 21
Oracle 4.1 Workstation setup (COMOS workstation) Procedure Use the configuration assistant to set up a net service name. 1. In the first window, which is called "Oracle Net Configuration Assistant: Welcome", activate the option "Local Net Service Name Configuration" and click the "Next" button to confirm. 2. The "Add" option in the next window is pre-selected for you. Click the "Next" button. 3. In the next window, which is called "Oracle Net Configuration Assistant: Net Service Name Configuration, Service Name", enter the name in the "Service Name" field. Example: For CS09. Click the "Next" button. 4. In the next window, click a network protocol. Example: "TCP". Click the "Next" button. 5. In the next window, enter the "Host name" in the list. This is the name of your server on which the Oracle instance is running. Please obtain the information from your Oracle administrator regarding the selection of the port number. Click the "Next" button. 6. To test the functionality of the database connection, activate the option "Yes, perform a test" in the next window. Click the "Next" button. 7. In the next window, click the "Change login" button. Another window opens. Complete the "User name" and "Password" fields. Click the "OK" button. 8. In the next window, the Oracle Net Configuration Assistant tries to connect to the database using the information you have entered. Click the "Next" button. 9. In the next window, enter the "Net Service Name". Example: ORADBCS09. Remember which name you have used. Click the "Next" button. 10. After that you will be asked if you want to configure another Net Service Name. Click the "Yes" or "No" button and follow the instructions. Please ensure that a Net Service Name is set up for each Oracle server. 4.1.4 Creating an ODBC data source for an Oracle client The ODBC entry is only used as the basis for a number of values that are needed at another point. Data communication no longer takes place via the ODBC connection but instead via ADO. An ODBC data source on the basis of a Microsoft ODBC driver for Oracle is required on each client PC for the operation of the database connection. 1. Select "Control Panel > Administrative Tools" from the Windows Start menu and start the ODBC Manager. 2. Click the "Add" button on the "System DSN" tab. 3. Select the required driver from the list. It is very important that you select "Microsoft ODBC driver for Oracle", not the "Oracle ODBC driver". 22 Operating Manual, 09/2011, A5E03638301-01
Oracle 4.1 Workstation setup (COMOS workstation) Configuring the data source No password can be entered in this window. Instead, the "Login" window opens when COMOS is started or the password is taken from a dat file. See also section First COMOS login/creating a dat file (Page 24). 1. Make the following settings: "Data source name" field: "pt_oracle". This entry is mandatory for COMOS. "Description" field: Any. This entry is displayed in COMOS. "User name" field: The Oracle user name on the server Corresponds to the database name "Server" field: <Net Service Name>. This is the name that has been assigned with the Net Configuration Assistant. See also section Net Service Name setup (Page 21). 2. Click the "OK" button to confirm. The system data source is now displayed in the list on the "System DSN" tab. 4.1.5 Creating additional instances for the Oracle client There is also the option to create instances for Oracle servers. These instances enable you to select the desired server during login to COMOS without needing to switch within the ODBC Administrator. 1. Select "Control Panel > Administrative Tools" from the Windows Start menu and start the ODBC Manager. 2. Go to the "System DSN" tab. Here you add a data source of the type "MS ODBC for Oracle". 3. Repeat the described procedure with the following values in the "Microsoft ODBC for Oracle configuration" window: Instance1 Name: pt_oracle_1 Description: Any Instance2 Name: pt_oracle_2 Description: Any Instance3 Name: pt_oracle_3 Description: Any Instance3 behaves differently. COMOS does not save a password file. Operating Manual, 09/2011, A5E03638301-01 23
Oracle 4.1 Workstation setup (COMOS workstation) See also First COMOS login/creating a dat file (Page 24) 4.1.6 First COMOS login/creating a dat file The information generated above in the system DSN is not sufficient for COMOS. Additionally a search for a dat file is conducted: "<Installation directory>\comos\config\orapwd.dat". If instances are used: "orapwd_1.dat", "orapwd_2.dat" The password for the server login, not the COMOS login is stored in this dat file. If COMOS does not find this dat file, a login window is displayed in which you can enter the login ID and password. If you know the password, COMOS can use this information to log into the database server. COMOS then automatically generates an encrypted dat file. When you start COMOS subsequently, an additional login window for logging into the database server will no longer be displayed. Alternatively, if you have administrator rights, you can generate a dat file and install it on the clients. In this case, no additional login window will be displayed even when COMOS is started for the first time. Instance "pt_oracle_3" behaves differently. The dat file is not stored permanently. For this instance, the user name and password are requested for every login. 4.1.7 Changing the ODBC connection See also Changing the ODBC connection (Page 16) 24 Operating Manual, 09/2011, A5E03638301-01
Oracle 4.2 Setting up the Oracle Server 4.2 Setting up the Oracle Server The administration of Oracle databases requires in depth know-how. For this step it is expected that an Oracle administrator conducts these actions. Supported versions: See also section Version (Page 7). 4.2.1 Unicode-capable instance Requirements In order to work with unicode, a unicode-capable instance is needed. This instance has to be created from the beginning as unicode-capable. An already existing instance cannot be converted. Creating a unicode-capable instance Database server: Oracle 11G R1 Purpose: Support on the database side for multiple-language entries in COMOS 9.2 Tested languages: Chinese, Russian Settings for the creation of a database instance: Database character set: "AL32UTF8" Country-specific character set: "AL16UTF16 NLS-specific parameter: "NLS_LENGTH_SEMANTICS = CHAR" set as standard value for the "SPFILE". Operating Manual, 09/2011, A5E03638301-01 25
Oracle 4.2 Setting up the Oracle Server 4.2.2 Creating a new user First a new user has to be created under Oracle. Later, all COMOS clients will have to log on to Oracle with this user name. 1. Start the Oracle Enterprise Manager and switch to the administration. 2. There you open the user administration and start with the first tab, "General". 3. Go to the "Roles" tab. 4. Click the "Edit list" button and add "CONNECT" as well as "DBA" to the list. 5. Go to the "System privileges" tab. 6. Click the "Edit list" button and add "UNLIMITED TABLESPACE" to the list. 7. Click the "OK" button. Update message Afterwards you receive the message that your object was created successfully. 26 Operating Manual, 09/2011, A5E03638301-01