SDL Installing Contenta Server on Windows
SDL Contenta 5.6
January 2018 Legal notice
Copyright and trademark information relating to this product release.
Copyright © 2009–2016 SDL Group.
SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and exclusive rights of SDL Group. All references to SDL or SDL Group shall mean SDL PLC. and its subsidiaries and affiliates details of which can be obtained upon written request.
All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL.
Contenta is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred.
This product may include open source or similar third-party software, details of which can be found by clicking the following link: “Acknowledgments ” on page 27.
Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
To the maximum extent permitted by law, SDL Group shall not be liable in contract, tort (including negligence or breach of statutory duty) or otherwise for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software Documentation even if such losses and/or damages were foreseen, foreseeable or known, for: (a) loss of, damage to or corruption of data, (b) economic loss, (c) loss of actual or anticipated profits, (d) loss of business revenue, (e) loss of anticipated savings, (f) loss of business, (g) loss of opportunity, (h) loss of goodwill, or (i) any indirect, special, incidental or consequential loss or damage howsoever caused.
All Third Party Software is licensed "as is." Licensor makes no warranties, express, implied, statutory or otherwise with respect to the Third Party Software, and expressly disclaims all implied warranties of non-infringement, merchantability and fitness for a particular purpose. In no event will Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct, actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and on any theory of liability. This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties acknowledge that this is a reasonable allocation of risk.
Information in this documentation, including any URL and other Internet Web site references, is subject to change without notice. Without limiting the rights under copyright, no part of this may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of SDL Group.
ii SDL Installing Contenta Server on Windows Contents
1 Installing Contenta Server overview ...... 1
Requesting the Contenta License File ...... 2
Installation information prompts ...... 3
2 SQL Server Settings for SDL Contenta ...... 5
Configuring the Microsoft SQL Server ODBC Data Source ...... 7
3 Configuring the Oracle ODBC Data Source ...... 9
Configuring the Oracle ODBC Data Source 64-bit ...... 10
4 About Contenta Server and third-party components ...... 11
Installing Contenta Server and third-party components ...... 12
Notes and reminders for post installation ...... 15
Alternate Reprise License socket number ...... 16
Oracle Passwords ...... 16
Windows Password Security and Contenta with MSSQL ...... 16 Changing the xyadmin and Database Passwords ...... 17 Turning off Check Policy in the SQL script ...... 18 Modifying the Windows Security Policy ...... 18
Configuring Microsoft SQL Server Databases ...... 19 Configuring Windows database servers ...... 19
Configuring Oracle Tablespaces ...... 21 For Windows Database Servers (Only) ...... 21 Creating the Contenta tablespaces ...... 21
Verifying Oracle character set definitions ...... 23
Installing the license file after installing Contenta ...... 24
Configuring for License Server Failover ...... 24
Post-installation note regarding PcmPortal ...... 25
A Acknowledgments ...... 27
SDL Installing Contenta Server on Windows iii iv SDL Installing Contenta Server on Windows 1
Installing Contenta Server overview 1 Installing Contenta Server overview
Important: The initial release of Contenta 5.6 does not support Microsoft SQL (MSSQL) Server. Please disregard references to MSSQL Server support in the Contenta 5.6 documentation. SDL will add support for MSSQL Server to Contenta 5.6 soon. If you have any questions, please contact Contenta Project Management. Complete the following tasks to install Contenta Server with an MSSQL database. 1. Request the license file. 2. Gather the information required by the installer. 3. Configure ODBC and SQL for SDL Contenta. 4. Install the Contenta Server software and third-party components. 5. If installing on Windows Server. 6. Configure the Contenta data file size in your MSSQL database.
To install Contenta Server with an Oracle database: 1. Request the license file. 2. Gather the information required by the installer. 3. Configure the Oracle ODBC. 4. Install the Contenta Server software and third-party components. 5. Configure the Contenta tablespaces in your Oracle database.
Configuring for use with Citrix workstations
To configure your system for use in a Citrix environment, refer to the three files in the Contenta_home/ distr/citrix directory on your server.
The CitrixX11Startup. pdf is titled“Configuring Citrix server to run XPP/Contenta via a Citrix client using published applications”and it contains instructions about running SDL Contenta using a Citrix client workstation Related information
Ӎ “Requesting the Contenta License File”on page 2
Ӎ “Installation information prompts”on page 3
Ӎ “SQL Server Settings for SDL Contenta”on page 5
Ӎ “Installing Contenta Server and third-party components”on page 12
Ӎ “Windows Password Security and Contenta with MSSQL”on page 16
Ӎ “Configuring Microsoft SQL Server Databases”on page 19
Ӎ “Configuring the Oracle ODBC Data Source”on page 9
Ӎ “Configuring Oracle Tablespaces”on page 21 Requesting the Contenta License File
Each server on which SDL Contenta software is installed requires a license. The Contenta license file can be installed at any time but must be activated before you can use the SDL Contenta application.
2 SDL Installing Contenta Server on Windows Installing Contenta Server overview 1
About this task Follow these steps to obtain the license file:
Procedure 1. Contact SDL Customer Support at www.sdl.com/ support. 2. Provide the following information with your request: • Site code The site code appears as your customer number on SDL invoices. • Host name of the designated Contenta Server Note: If you request the license after installing Contenta, note that the server information about hostid is stored in the file C:\Windows\ hostid.txt.
• Host ID/Ethernet Address for the license server If you are using SDL Contenta on a Windows system that may sometimes be disconnected from the network, use the disk volume serial number instead of the Host ID/Ethernet Address when you request the Contenta license. SDL emails the license file contents to you within 24 hours. The contents of the license file is an attachment to the email.
Installation information prompts
The installation program prompts you for the following information while installing Contenta Server. Obtain this information before you begin. You must have an Oracle system account.
You are prompted to enter: Note the information here to use during the installation:
Type of database—Oracle or Microsoft SQL Server
Server Socket Default is 6050. Unless it is explicitly changed, enter/accept the default. The input value is numeric and in the range 1024 49151. ˉ ODBC DSN (Data Source Name)
Oracle SID Only if using an Oracle database.
License server name (if using a license server, i.e. a different server, for Contenta license)
License server port number (if using a Default is 5053. Unless it is explicitly changed, license server for Contenta license) enter/accept the default. If you do not use the default port number, after installing see Alternate Reprise License Socket Number.
SDL Installing Contenta Server on Windows 3 1 Installing Contenta Server overview
You are prompted to enter: Note the information here to use during the installation: Contenta Web Services Base URL In the Contenta Web Services Base URL window, specify the URL for your Contenta Web server. The value entered here is written to the Windows registry and read by WS applications and Perl wrappers.
The following table lists additional information if you are also installing Contenta Explorer on your server:
You are prompted to enter: Note the information here to use during the installation:
Name of the Contenta Server
Name of the default Contenta database
4 SDL Installing Contenta Server on Windows 2
SQL Server Settings for SDL Contenta 2 SQL Server Settings for SDL Contenta
Follow these steps only if you are using an MSSQL database. If using an Oracle database, see "Configuring the Oracle ODBC Data Source."
About this task Follow the steps below to verify that SQL Server is configured with the required settings for use with SDL Contenta.
Procedure 1. Verify the SQL Server Product Version; from the Start menu on your MSSQL server, click Microsoft SQL Server Management Studio. 2. Connect to the database engine using Windows Authentication—for example: Select a server from the Server name drop down list. • ˉ • Click Connect. 3. Click on New Query icon in the upper left of the Server Management Studio window. 4. Enter the following query in the query pane (example below):
SELECT SERVERPROPERTY (edition) as Edition, SERVERPROPERTY(productversion) as Product Version, SERVERPROPERTY (productlevel) as Patch
5. Press F5 to execute the query. 6. Check that the Login Mode is mixed mode by entering the statement below in the Microsoft SQL Server Management Studio window. You should still be connected to the database in the Microsoft SQL Server Management Studio window. If not, or if executing this step on its own, connect to the database—see step 2 in this topic. xp_loginconfig login mode 7. Press F5 to execute the query. 8. To verify the SQL Server Remote Connection , from the Start menu select:
All Programs > Microsoft SQL Server 20nn > Configuration Tools > SQL Server Surface Area Configuration
The SQL Server 20nn Surface Area Configuration window appears. 9. Click on Surface Area Configuration for Services and connections. A window with SQL Server services appears. 10. Click Remote Connections under Database Engine. Services and connection types appear. 11. Verify that Local and remote connections and Using both TCP/IP and named pipe are selected. If not, click in the radio button next to each. 12. Click OK.
6 SDL Installing Contenta Server on Windows SQL Server Settings for SDL Contenta 2
13. Close the Surface Area Configurationwindow by clicking the X in the upper right corner of the window.
Configuring the Microsoft SQL Server ODBC Data Source
Before installing the Contenta software, you must configure the Microsoft SQL Server ODBC Data Source.
Procedure 1. In the Windows Control Panel, click Administrative Tools > Data Sources. 2. On the System DSN tab, click Add. 3. Click SQL Native Client. 4. Click Finish. 5. In the Create a New Data Source to SQL window, enter a Data Source Name and Description, then select the Server. 6. Click Next. 7. Under How should SQL Server verify the authenticity of the login ID?, click With SQL Server authentication using a login ID and password entered by the user. 8. Click Next. 9. Accept the defaults in the resulting window: • Use ANSI quoted identifiers • Use ANSI nulls, packages and warnings 10. Click Next. 11. Accept the defaults in the resulting window. Ensure that Perform translation for character data is enabled. 12. Click Finish.
SDL Installing Contenta Server on Windows 7 2 SQL Server Settings for SDL Contenta
8 SDL Installing Contenta Server on Windows 3
Configuring the Oracle ODBC Data Source 3 Configuring the Oracle ODBC Data Source
Follow these steps only if you are using an Oracle database. If using an MSSQL database, see "SQL Server Settings for SDL Contenta." Configuring the Oracle ODBC Data Source 64-bit
If installing on a 64 bit Administration client and using an Oracle database for Contenta data, before installing the Contentaˉ software, configure the Oracle ODBC Data Source.
About this task
Note: You must configure the ODBC with 32 bit Odbcad32.exe (Data Source Administrator tool) on a 64 bit machine. ˉ ˉ
Procedure 1. Make sure that the Firewall is turned off or that the Oracle port is open. 2. Create a shortcut to “C:\Windows\ SysWow64\ odbcad32.exe” under Control Panel > Admin- istrative Tools by copying the file odbcad32.exe and doing a paste shortcut under Control Panel > Administrative Tools. 3. Rename the shortcut to“32_Bit_Data_Source (ODBC)”. 4. Add the Contenta SID to the tnsnames.ora file.
Note: On the Contenta Server, ensure that Contenta SID is added to tnsnames.ora file under 32 bit Oracle. ˉ
5. Execute “ODBC Data Source (32 bit)” under Control Panel > Administrative Tools, double click on the entry in theˉ list, which displays the ODBC interface. ˉ 6. Add the Oracle driver and add ContentaDSN data source and point to the CS/DB Server SID. 7. Test the ODBC connection.
10 SDL Installing Contenta Server on Windows 4
About Contenta Server and third-party components 4 About Contenta Server and third-party components
While installing Reprise License Manager, if the file RLM12.dll or a similar file fails to install, make sure that you have downloaded the 32 bit version of this DLL file, not the 64 bit version. ˉ ˉ While installing if you encounter an error about DLL file not registering, it means that the file was in use during installation. The following is an example of this error:
The following files did not self-register or unregister: C:\Windows\SysWOW64\OLEAUT32.DLL Access is denied
If you encounter this error, you can do either of the following: • Click OK on the install screen and continue the installation then register the file when done. To register a dll, in the Start > Run dialog box , enter regsvr32 “file path
If you encounter an error message stating that the ATL71.dll did not register, you can ignore the message. Installing Contenta Server and third-party components
Complete these steps to install Contenta Server and related third-party components.
Procedure 1. Log in as a user with administrative privileges. 2. Back up your system. SDL recommends that you back up your system before installing SDL Contenta or any software. 3. Remove earlier versions of Perl. Refer to the platform requirements document to determine the version of Perl required for the version of Contenta that you are installing.
Note: Contenta 5.5 installs Strawberry Perl in its own install location and does not support Ac- tiveState Perl. Before removing ActiveState Perl, make sure no other Software is dependent on it, for example, SDL XPP.
4. Stop all SDL Services (such as those installed and running for XPP). 5. To prevent the installer from complaining that another install is going on, before beginning the installation, stop the Windows Installer service, reboot, and restart this service as follows: a. Display the services: Control Panel > Administrative Tools > Services. b. Right click on the Windows Installer service then click Properties. Stop.
12 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
c. Click Manual in the Startup type field, and then click d. Click OK in the services window, and then reboot the system. e. After rebooting, login as a user with administrator privileges and display the servicesfrom the Control Panel again. f. Right click on the Windows Installer service, and then click Properties. g. Click Automatic in the Startup type field, and then click Start. 6. Check the directory into which you are installing to be certain that ownership and permissions settings allow you to install into that directory. To check: a. Right click the installation directory, for example, C:\Program Files (x86), then click Propertiesˉ . b. On the Security tab, click Advanced. c. Ensure that your user account has read and execute permission for this directory. d. Ensure that Include inheritable permissions from this objects parent is selected and that the permission applies to this folder, subfolders, and files. e. Click OK to exit the various dialog boxes. 7. Use Windows to mount the ISO installation file or use a third-party tool to mount the ISO as a disk. If prompted to verify that you want to run the file, click Run.
Note: If the installer does not automatically start, right click the setup.exe file from the ISO file and Run as Administrator. ˉ
8. Click Next in the Welcome window to begin the installation. The installation program displays the License Agreement window. 9. Click Yes to accept the license agreement. 10. Click Next to accept the default installation path, and then click Next. To change the default path, click Browse to select a new location.
Note: If you are installing Contenta Server and Contenta Client software on the same machine, install both under the same directory.
If you use the browse button to locate a directory, be certain to add a folder name into which you want to install the software—that is, if you choose C:/Program Files (x86) add Contenta to the path so it reads: C:/Program Files (x86)/Contenta The installer creates the folder if it does not exist. 11. If installing a combined Contenta and License Server, select all the features. This installs the following components. • Strawberry Perl • License Manager • Contenta Server • Search Service
SDL Installing Contenta Server on Windows 13 4 About Contenta Server and third-party components
Important: If you want to spread search services over multiple servers, you can run the Contenta Server installer on each server and enable only the Search Services option.You do not have to install the License Manager. You will also need to specify the Contenta Server Name, Socket, Database Names (comma separated), and SID. ˉ If Contenta Server is configured for ODBC, make sure to enter the correct ODBC DSN when prompted for it. After you have made your selections, click Next to continue. The installation program displays the Contenta Database Settings window. 12. Select the type and version of the database you have installed for use with SDL Contenta. • Oracle 12c • Oracle 11g Release 2 • Microsoft SQL Server After you have selected the database type and version, click Next to continue. The installation program displays the Oracle Home Directory window. 13. In the window, select the directory where Oracle is installed, and then click OK. The installation program displays the Contenta Database Information window. 14. Complete the database setting fields as follows.
Server Socket PcmPortal number running on your Contenta server. The default is 6050. ODBC DSN Data Source Name as specified for Oracle or for Microsoft SQL Server. See the information in the Installation Information Prompts. Oracle SID Applies only to Oracle databases. Name of the Contenta Oracle instance or service (SID).
After you have entered the appropriate information, click Next to continue. The installation program displays the Contenta Solr Settings window. 15. In the window, enter the name of each database that you want indexed (in comma-delimited list) in the Database Names field. 16. Click Next. 17. In the License server window, do one of the following. • If this is not a License Server (License Manager was not installed in step 11), you are prompted for: • Server Name: enter the name or IP address of the server where the license file resides. • Server Socket: Enter the port number. This is not the PcmPortal number.
14 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
The default port number is 5053. Unless it is explicitly changed, enter accept,which is the default. If you do not use the default port number, after installing see Alternate Reprise License Socket Number. • If this is a License Server (License Manager was installed in step 11), you will be prompted for a license file, click Yes or No. If you click No, the installer provides information about obtaining a license file. The license information is saved in the System environment variable sdl_xysoft_LICENSE as
Note: After the Contenta installation is complete, you must restart your system even if the installer does not prompt you to do so.
23. Click Finish.
Notes and reminders for post installation • If you did not have the Contenta license file in place during the installation, you can install the license after the installation is complete by following the instructions in the Installing the License File after Contenta Installation topic.
Note: If you request the license after installing Contenta, note that the server information about hostid is stored in the file C:\Windows\ hostid.txt
• If you did not use the default port number for the License Server. After installing, see Alternate Reprise License Socket Number. • Oracle only: During the Oracle install you are prompted to set the Administrative password. If you choose to set the password using the rules presented during the (Oracle) installation, after installing Contenta, you must change the password to the new password in the XyConfig file. See the SDL Contenta Administration User Guide for information about changing passwords in the XyConfig file.
SDL Installing Contenta Server on Windows 15 4 About Contenta Server and third-party components
• Oracle only: See Oracle Passwords for information about configuring and controlling Contenta password expiration. Alternate Reprise License socket number
If you do not use the default port number for the Reprise license server, you must edit the license file and change the line beginning with HOST.
On the license server, in the C:\Program Files (x86)\XyEnterprise\SDL_License directory, edit the license file and replace 5053 with the server socket number. For example, if the port is 5055 and the server is rosie:
Change from the delivered: HOST rosie 0150668a3476 5053 To: HOST rosie 0150668a3476 5055
Note: Do not change the number after the server name. In the example above it is 0150668a3476. This is an encrypted number associated with your Server ID and, if changed, the license file is invalid.
Oracle Passwords
You can prevent passwords from expiring on you Oracle database server.
Oracle only: Starting with Oracle passwords expire by default. This can result in Contenta system failures due to the expiration of the sys, system and xyadmin passwords. To prevent passwords from expiring on your Oracle database server, as the SYS user enter:
ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED PASSWORD_LIFE_TIME UNLIMITED; NOAUDIT ALL; DELETE FROM SYS.AUD$;
Windows Password Security and Contenta with MSSQL
Information for installing Contenta on a Windows Server system with enforced security.
If installing on a Windows Server system with enforced security, follow the steps in this topic before following the Configuring Microsoft SQL Server Databases topic.
16 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
If not using a Windows Server system with enforced security, skip to the steps for Configuring Microsoft SQL Server Databases topic.
The following describes the default security policies for Windows Server passwords— the password: • cannot contain the user’s account name or parts of the user’s full name that exceed two consecutive characters. • must be at least six characters in length. • must contain characters from three of the following four categories: English uppercase characters (A through Z). English lowercase characters (a through z). Base 10 digits (0 through 9). Non alphabetic characters (for example, !, $, #, %). ˉ Because of these complex security policies, if Contenta is installed on Windows Server, customers who use SQL Server must do one of the following:
Security Option See this topic If you want to maintain the Windows security Changing the xyadmin and Database Passwords policies for passwords If you want to maintain the Windows security Turning off Check Policy in the SQL Script policies for passwords but do not want it to apply to Contenta If you do not want to maintain the Windows Modifying the Windows Security Policy security policies for passwords
Changing the xyadmin and Database Passwords
Follow this procedure if you need to maintain the Windows security policies for passwords.
Procedure 1. Before executing the pcm_setup.sql script to create the xyadmin user, modify the file and replace the manager password with a password that conforms to the criteria noted in the Windows Password Security and Contenta with MSSQL topic.
Note: The manager string appears only once in this file.
2. Use the dbpwdmgr.exe utility to change the default password for xyadmin and the Contenta database(s). To change the password: a. Execute dbpwdmgr.exe from a command prompt b. At the DBPWDMGR prompt, enter: modify c. Enter the user name as defaultsysadmin d. Enter the xyadmin password
SDL Installing Contenta Server on Windows 17 4 About Contenta Server and third-party components
e. Re enter the xyadmin password ˉ 3. To change the Contenta database password: a. Execute dbpwdmgr.exe from a command prompt b. At the DBPWDMGR prompt, enter: modify c. Enter the user name as defaultdb d. Enter the replacement password for pdmuser e. Re enter the replacement password for pdmuser ˉ 4. Copy the XyConfig.bin file located under Contenta_home\bin as required by your configuration. • If the file is configured to be shared on the network, copy the file to the directory defined by the XYV_PDM_XYCONFIG_DIR variable (on Linux) or to the XYV_PDM_XYCONFIG_DIR registry setting (on Windows). • If the file is not configured to be shared, copy it to all Contenta client workstations.
Turning off Check Policy in the SQL script
Follow this procedure if you want to maintain the Windows security policies for passwords but do not want them to apply to Contenta.
Procedure 1. Open the database.pm file, in the Contenta_home > encaps directory for editing. 2. Find and change CHECK_POLICY=ON to CHECK_POLICY= OFF. This is specified in two places in the file. 3. Open the pdm_setup.sql script delivered in the Contenta_home > setup directory for editing. 4. Find and change CHECK_POLICY=ON to CHECK_POLICY= OFF. This is specified in one place in the file.
Note: Always back up the database.pm file after modifying. It is overwritten if Contenta adminis- tration (client) software is installed on the Contenta Server.
Modifying the Windows Security Policy
Follow this procedure if you do not want to maintain the Windows security policies for passwords.
About this task This procedure modifies a Windows security setting. The procedure should be followed by a system administrator who has permissions to change security settings for a domain.
18 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
Procedure 1. Click Control Panel > Administration Tools > Local Security Policy. 2. Open Account Policies, and then click Password Policy. 3. Double click on Password must meet complexity requirements to open it for editing. ˉ 4. Under Local Security Setting, click in the box Disable. 5. Click Apply. 6. Click OK.
Configuring Microsoft SQL Server Databases
Follow these steps only if you are using an MSSQL database. If using an Oracle database, see "Configuring Oracle Tablespaces."
After you have rebooted the system following the SDL Contenta installation, your database administrator (a user with knowledge of Microsoft SQL Server) must follow these steps to configure the Contenta xyadmin user and database.
Configuring Windows database servers
If the database server is a Windows Server system, you must disable the complex password requirement before completing the procedure below to create the tablespaces in the database.
About this task To do this, go to: Control Panel > Administrative Tools > Local Security Policies > Account Policies > Password Policies.
If you cannot, or do not, want to disable the requirements, change the password in the pdm_setup.sql script from manager to a password which can meet complexity requirement of Local Security Policy, and then follow the procedure below to execute the script.
Note: If you change the password, be sure to inform the Contenta Administrator. The password is needed so that they can successfully execute Contenta administration utilities. Use dbpwdmgr to change the password for the Contenta administration utilities—see the Modifying the Database Passwords in the SDL Contenta Administration User Guide for information about using dbpwdmgr.
SDL Installing Contenta Server on Windows 19 4 About Contenta Server and third-party components
Procedure 1. Install SQLCMD, Client Tools, and Client Libraries on the database server. 2. Edit the pdm_setup.sql script installed into the Contenta_home/setup directory on the Contenta Server. You can modify: • Path name for the data file and log file In the example, these are defined as:
C:\Program Files (x86)\Microsoft SQLServer\MSSQL.1\MSSQL\Data\xyadmin.mdf C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ftxyadmin_log.ldf
• Size of the data file and log file and allotted file growth In the example, it is defined as:
SIZE = 2048KB, FILEGROWTH = 1024KB
3. Execute the script as follows: a. At a command prompt on the server, go to the Contenta_home/setup directory. b. At the command prompt, enter the following: sqlcmd -S
Note: Your site and configuration may require more or less space. You should monitor tablespace daily to ensure the operations have sufficient space to complete properly.
Note: Always back up the database.pm file after modification. It is overwritten if Contenta administration (client) software is installed on the Contenta Server.
20 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
Configuring Oracle Tablespaces
Follow these steps only if you are using an Oracle database. If using an MSSQL database, see "Configuring Microsoft SQL Server Databases."
After you have rebooted the system following the SDL Contenta installation, your database administrator must follow the steps below to configure the Contenta tablespaces.
The SDL Contenta Installer delivers a Linux version of pdm_setup.sql into the Contenta_home/setup directory (where Contenta_home is the Contenta install directory). Use this file as the basis for your script or create one based on the example provided in this section. The pdm_setup.sql script configures the Contenta tablespace in the Oracle database.
Note: The pdm_setup.sql script contains the following SQL alter system command to dynamically alter the Oracle database instance: alter system set deferred_segment_creation=false scope=both;
This is necessary to successfully use the dbimport.pl script to create your database instance. It ensures that any empty tables in the .dmp file are imported. If you are reinstalling and already have tablespaces in the database for Contenta in which you plan to import an existing Contenta (database) instance, you must enter the commands above in SQL to ensure no empty tables are dropped. This must be done before exporting a database with the dbexport.pl script.
For Windows Database Servers (Only)
If the database server is a Windows Server system, you must disable the requirement of complex password before completing the procedure below to create the tablespaces in the database.
To do this, go to Control Panel > Administrative Tools > Local Security Policies > Account Policies > Password Policies.
If you cannot or do not want to disable the requirement, change the password in the pdm_setup.sql script from manager to a password which can meet complexity requirement of Local Security Policy then follow the procedure below to execute the script.
Note: If you change the password, be sure to inform the Contenta Administrator. The password is needed to successfully execute Contenta administration utilities. Use dbpwdmgr to change the password for the Contenta administration utilities—see Modifying the Database Passwords in the SDL Contenta Administration User Guide for information about using dbpwdmgr.
Creating the Contenta tablespaces
SDL Installing Contenta Server on Windows 21 4 About Contenta Server and third-party components
Procedure 1. Create one or more directories for Contenta tablespaces. Make sure that the hard drives that contain the tablespaces have sufficient space for your site’s needs—enough space to contain the .dbf files. SDL recommends that you create each tablespace on separate disks to minimize the load. 2. Edit the pdm_setup.sql script installed in the Contenta_home\setup directory on the server. To identify the lines to edit, see the example below. You can modify: • Path name to each of the tablespaces (to the appropriate directory or directories created in Step 1) • Size of each tablespace The samples include recommended sizes but you must define the tablespace size to meet your site needs. For example: datafile 'D:\oracle\pdm_1.dbf' SIZE 2000M 3. Execute the script: a. At a command prompt on the server, go to the Contenta_home\OracleScripts directory. b. At the command prompt enter: sql_pathname\sqlplus where sql_pathname is the directory where the sqlplus.exe file is located. c. Enter the default Oracle user (system) and password (as specified during the Oracle Server installation). d. At the prompt, enter: @pdm_setup.sql where pdm_setup.sql is the SQL script that defines the Contenta tablespaces. SQLplus displays a series of messages either confirming that the tablespaces were created, or providing error information for you to correct the script. The following PdmScript is an example only. It shows how you can define the tablespaces. The data you modify for your site is highlighted in bold. Note that this file specifies the D: drive for storage. Your site and configuration may require more or less space. You should monitor tablespace daily to ensure the operations have sufficient space to complete properly.
-- Run this script as the oracle user (system/"passwd") -- the sizes and paths can be changed as needed based om site req's create tablespace pdm_appl_data datafile 'D:\oracle\pdm_1.dbf' SIZE 2000M default storage ( minextents 1 maxextents unlimited pctincrease 1) online permanent; alter tablespace pdm_appl_data add datafile 'D:\oracle\pdm_2.dbf' SIZE 2000M; create tablespace pdm_indx_data datafile 'D:\oracle\pdmindx_1.dbf' size 1000M default storage ( minextents 1 maxextents unlimited
22 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
pctincrease 1) online permanent; create temporary tablespace pdm_temp tempfile 'D:\oracle\temp_1.dbf' size 500M; create user xyadmin identified by manager default tablespace pdm_appl_data temporary tablespace pdm_temp; alter user xyadmin quota unlimited on pdm_appl_data; alter user xyadmin quota unlimited on pdm_indx_data; grant connect to xyadmin; grant create user to xyadmin; grant alter user to xyadmin; grant drop user to xyadmin; grant grant any privilege to xyadmin; grant select any dictionary to xyadmin; create table xyadmin.pdm_databases ( username char(50), userid integer, index_tablespace char(50) ); connect xyadmin/manager; grant select on xyadmin.pdm_databases to public; Exit
Verifying Oracle character set definitions
To confirm that the Oracle character set definitions are set correctly and consistently, perform the following verification steps for the 32 bit Oracle client installed on the Contenta Server machine (regardless of whether the 64 bit Oracleˉ server is installed on the same machine or on a different machine). ˉ
Procedure 1. Log in as user sysdba. 2. Issue the following SQL command in SQL*Plus:
select name, value$ value from props$ where name like 'NLS_CHARACTERSET' or name like 'NLS_NCHAR_CHARACTERSET';
3. In the results, check the following: • NLS_CHARACTERSET is set to AL32UTF8 • NLS_NCHAR_CHARACTERSET is set to AL16UTF16 4. In the Windows registry, under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KEY_oracle_home_name, check that NLS_LANG is set to AMERICAN_AMERICA. AL32UTF8. This value must be consistent with the value set for NLS_CHARACTERSET.
SDL Installing Contenta Server on Windows 23 4 About Contenta Server and third-party components
Installing the license file after installing Contenta
If you did not have a license file when you installed Contenta, or if you have a new license file to install, copy the license file to the license directory.
By default, this is C:\Program Files (x86)\XyEnterprise\SDL_License. The license file can be named anything, but must have a .lic extension.
If you request the license after installing Contenta, note that the server information about hostid is stored in the C:\Windows\ hostid.txt file.
Note, on the license server, the service is named SDL_LICENSE. If you are replacing a Reprise license, stop and restart the service.
Note: The sdlxysoft_LICENSE system variable specifies the port and server name where the license is installed. If the license server is different than the application server, check the license information in the system environmental variable sdl_xysoft_LICENSE. The format is:
Configuring for License Server Failover
To configure for a license server failover, add the failover license server information to the sdlxysoft_ LICENSE system variable. The second, or failover system, is added to the current, primary system information separated with a semicolon.
For example, assuming sdlsv1 is the primary license server and sdlsv2 is the backup, failover server the value for the sdlxysoft_LICENSE system variable is:
5053@sdlsv1;5053@sdlsv2
Note that it takes approximately two to four minutes for the failover license server to start serving licenses once a failed node goes down.
Note: The system variable is set in Control Panel > System in the Advanced > Environment Variables window.
Reprise license log RLM.log, located in the SDL_LICENSE home directory, contains information about what server or servers are supported by the existing license server and what licenses files have been read by the server.
When a license server encounters a rlm_failover license, it: • Starts a separate thread in the license server to periodically monitor the health of the failed server.
24 SDL Installing Contenta Server on Windows About Contenta Server and third-party components 4
This is done by attempting TCP/IP connection(s) to ports on the failed server in order to determine whether the server is up or down. • If the failed server should go down, enables all licenses in license files for the failed server by performing the equivalent of an rlmreread command. • When the failed server comes back up, disables all licenses in license files for the failed server by performing the equivalent of an rlmremread command. Post-installation note regarding PcmPortal
The Contenta Server installer installs both OCI and ODBC versions of PcmPortal. The OCI version only works with Oracle 12c.
If you selected this database type: This was installed:
Oracle 12c The ODBC portal was installed as PcmPortal_ ODBC.exe
The OCI portal was installed as PcmPortal.exe
Oracle 11g Release 2 The ODBC portal was installed as PcmPortal.exe
The OCI portal was installed as PcmPortal_12c_ OCI.exe
SQL Server The ODBC portal was installed as PcmPortal.exe
The OCI portal was installed as PcmPortal_12c_ OCI.exe
SDL Installing Contenta Server on Windows 25 4 About Contenta Server and third-party components
26 SDL Installing Contenta Server on Windows A
Acknowledgments A Acknowledgments
SDL Contenta and SDL Contenta S1000D include open source or similar third-party software.
ActiveState ActivePerl ActivePerl is the industry-standard, commercial-grade Perl distribution used by millions of developers around the world for easy Perl installation and quality-assured code. Apache Log4j Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture. Apache Tomcat, Tomcat Embed Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. Apache Commons FileUpload The Commons FileUpload package makes it easy to add robust, high-performance, file upload capability to your servlets and web applications. Apache Commons Codec Apache Commons Codec (TM) software provides implementations of common encoders and decoders such as Base64, Hex, Phonetic and URLs. Apache Commons Logging The Logging package is an ultra-thin bridge between different logging implementations. A library that uses the commons-logging API can be used with any logging implementation at runtime. Commons-logging comes with support for a number of popular logging implementations, and writing adapters for others is a reasonably simple task. DWR (Direct Web Remoting) DWR is a Java library that enables Java on the server and JavaScript in a browser to interact and call each other as simply as possible. jacORB The free Java implementation of the OMG's CORBA standard. java2com This is a development tool for bridging the communication gap between Java and COM applications. It enables the integration of both COM and Java based components in one application and allow these components to communicate bi-directionally through Java Native Interface technology. JDOM JDOM's mission: to provide a complete, Java-based solution for accessing, manipulating, and outputting XML data from Java code. jQuery jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. LDAP C SDK The C LDAP Application Program Interface Internet Draft defines a set of API functions that you can use to build LDAP-enabled clients. The functionality implemented in this SDK closely follows the
28 SDL Installing Contenta Server on Windows Acknowledgments A
interfaces outlined in the Internet Draft, which should become an RFC someday. Using the function- ality provided with this SDK, you can enable your clients to connect to LDAPv3-compliant servers and perform standard LDAP functions. MKS Toolkit PTC MKS Toolkit for Developers, the award winning and industry-leading Windows / UNIX interoper- ability solution, dramatically improves the compatibility between Windows and UNIX environments. Omnimark OmniMark allows developers to build efficient content conversion pipelines that support the rapid insertion of multiple content filter elements without loss of processing speed. Reprise License Manager The Reprise License Manager (RLM) is a flexible and easy-to-use license manager with the power to serve enterprise users, and it comes to you from the creators of FLEXlm. SlickGrid A JavaScript grid/spreadsheet. Stingray Studio Stingray Studio provides tools for developing complex GUI applications that are easy to build, maintain, and evolve as new technologies improve the look and feel of user interfaces. Solr Solr is an open source search engine used to locate XML elements and attributes, as well as content. Xalan-C++ Xalan is an XSLT processor for transforming XML documents into HTML, text, or other XML document types.
Xalan-C++ version 1.10 is a robust implementation of the W3C Recommendations for XSL Transfor- mations (XSLT) and the XML Path Language (XPath). It works with a compatible release of the Xerces-C++ XML parser: Xerces-C++ version 2.7.0. Xerces-C++ Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces Java Parser The Xerces Java Parser 1.4.4 supports the XML 1.0 recommendation and contains advanced parser functionality, such as support for the W3C's XML Schema recommendation version 1.0, DOM Level 2 version 1.0, and SAX Version 2, in addition to supporting the industry-standard DOM Level 1 and SAX version 1 APIs.
SDL Installing Contenta Server on Windows 29 A Acknowledgments
30 SDL Installing Contenta Server on Windows