Server Manager
Copyright
© 2009 Open Text Corporation. All rights reserved. Documentation 01/2009 - Management Server 10.0
This documentation contains information protected by copyright. Without prior written permission, any part of this documentation may only be reproduced, translated, stored or analyzed in dp-systems by Open Text Corporation. The information in this documentation is subject to change without notice.
Open Text Corporation shall not be responsible for technical or editorial errors or omissions contained in this documentation. Open Text Corporation will not be liable for incidental or consequential damages resulting from the furnishing, performance or use of this documentation.
Trademarks
RedDot is a trademark of Open Text Corporation. All other product and service names are trademarks or registered trademarks of their respective owner.
0 S erver Manager 05/200 9
Contents 3
About This Documentation ... 8
Handbooks, Online Documentation, and Help ... 8
Breakdown of Topics ... 9
Conventions ... 9
Activity Flow Chart ... 9
Symbols ... 11
Syntax ... 11
About the Server Manager ... 12
Accessing the Server Manager ... 12
User Interface ... 13
Tree ... 13
Action Menu ... 14
Clipboard ... 14
Editing Clipboard Content ... 15
Administering Application Servers ... 16
Application Servers ... 16
Administering Asynchronous Processes ... 17
Administering Publication and Scheduled Processes ... 20
Process Properties ... 23
Backing Up Administration ... 26
Restoring Administration ... 26
Showing Licenses in Use ... 27
Creating Support Information ... 27
Editing Connections ... 28
Editing Connections ... 28
Editing Settings ... 29
Clearing the Language Resource Cache ... 37
Deactivating Servers ... 37
Activating Servers ... 37
Projects ... 38
Contents 0 S erver Manager 05/200 9 Classes ... 41 List of Classes ... 41 Log Files ... 42
Clearing Log Directories ... 42
Viewing Log Files ... 43
Deleting Log Files ... 44
Downloading Log Files ... 44
Viewing Log Files (Accountsystem) ... 44
Viewing Log Files (ApplicationImport) ... 45
Viewing Log Files (AsyncQueue) ... 45
Viewing Log Files (ChangeLicense) ... 46
Viewing Log Files (Common) ... 46
Viewing Log Files (Converter) ... 46
Viewing Log Files (ConvertFolder) ... 47
Viewing Log Files (CopyProject) ... 47
Viewing Log Files (Export) ... 47
Viewing Log Files (Import) ... 48
Viewing Log Files (Install) ... 48
Viewing Log Files (Login) ... 49
Viewing Log Files (Publishing) ... 49
Viewing Log Files (Report) ... 50
Viewing Log Files (Serverjobs) ... 50
Viewing Log Files (Shared) ... 51
Viewing Log Files (TreeExport) ... 51
Viewing Log Files (TreeImport) ... 51
Viewing Log Files (UpdateDatabase) ... 52
Viewing Log Files (User) ... 52
Viewing Log Files (WebCompliance) ... 52
Administering Users and Groups ... 54
Directory Services ... 54
Adding/Editing Directory Services ... 55
Users ... 58
Configuration File for LDAP Directory Services ... 58
Deleting Directory Services ... 65
Contents 0 S erver Manager 05/200 9 Selecting Projects ... 67 Selecting Groups ... 67
Deleting Imported Users ... 68
Users/Groups by Projects ... 68
Creating Groups ... 68
Connecting to Groups in Clipboard ... 70
Editing Groups ... 70
Creating Shortcuts in Clipboard ... 71
Deleting Groups ... 71
Disconnecting Groups from Projects ... 72
Connecting to Users in Clipboard ... 72
Sending E-mails to All Active Users of a Group ... 73
Sending E-mails to All Users of a Group ... 73
Users ... 74
Creating and Editing User Data ... 74
Finding Users ... 77
Sending E-mails to All Active Users ... 79
Showing Active Users ... 79
Showing All Users ... 80
Editing Module Assignments ... 81
Editing Project Assignments ... 84
Deleting Users ... 86
Editing Group Assignments ... 87
Creating Shortcuts in Clipboard ... 88
Groups ... 89
Showing All Groups ... 90
Administering Projects ... 91
Editing Projects ... 91
Creating Projects ... 91
Importing Projects ... 94
Checking Database Servers ... 96
Selecting Directories ... 96
Renaming Projects ... 97
Showing Project Information ... 98
Contents 0 S erver Manager 05/200 9 Copying Projects ... 101 Exporting Projects ... 103
Extended Information Concerning XML Project Exports ... 105
Updating Project Databases ... 106
Activating Versioning ... 107
Deactivating Versioning ... 107
Shrinking the Versioning Database ... 108
Activating Archiving ... 108
Deactivating Archiving ... 108
Displaying Active Users in Project ... 109
Editing Project Locks ... 109
Assigning Publishing Servers ... 111
Assigning Database Servers ... 111
Administering Database Servers ... 113
Administering Server Connections ... 113
Creating Server Connections ... 114
Showing Usage ... 114
Editing Server Connections ... 115
Testing Database Connections ... 118
Deleting Server Connections ... 118
Administering Database Access Modes ... 119
Creating/Editing Access Modes ... 119
Creating Provider Templates ... 120
Deleting Access Modes ... 121
Administering User-defined Jobs ... 122
Editing User-defined Jobs ... 122
Creating/Editing User-defined Jobs ... 122
Editing Scheduling ... 123
Editing Pending Actions ... 124
Editing E-mail Notifications ... 129
Showing Job References ... 129
Starting Jobs ... 130
Deleting Jobs ... 130
Contents 0 S erver Manager 05/200 9 Plug-ins ... 131 Importing Plug-ins ... 131
Plug-in Import Report ... 132
Creating/Editing Plug-ins ... 132
Editing Project Assignments ... 134
Deleting Plug-ins ... 135
Administering Delivery Server ... 136
Delivery Server ... 136
Creating/Editing Delivery Server Connections ... 136
Deleting Delivery Server Connections ... 137
Widget Configurations ... 138
Creating/Editing Widget Configurations ... 138
Deleting Widget Configurations ... 140
0
S
erver Manager
05/200
9
About This Documentation
This section provides an overview of the content and layout of the documentation. The handbooks and Help have been created and designed in a uniform way. The structure of the content is based on the structure of the software.
Topics covered in this chapter include:
Handbooks, Online Documentation, and Help (Page 8) Breakdown of Topics (Page 9)
Conventions (Page 9)
Handbooks, Online Documentation, and Help
The Management Server documentation consists of the following sections:
Installation
Open Text Web Solutions Server Manager SmartTree Content Classes SmartEdit Asset Manager Online Documentation Context-sensitive Help
The handbooks contain the following information:
The Installation handbook informs the reader how to install, update, and uninstall
Management Server. It also describes how to install and update the application servers in a cluster.
The Open Text Web Solutions handbook explains the Web Solutions user interface. It
also describes the functions of the Homepage, Tasks, and Search modules.
The SmartTree handbook contains reference documentation for SmartTree. The Server Manager handbook contains reference documentation for the Server
Manager.
The Content Classes handbook contains an overview of content classes, elements, and
templates. It also has a reference section that describes the individual functions available for working with content classes.
The SmartEdit handbook describes all functions available for working with SmartEdit. The Asset Manager handbook describes all functions available for working with Asset
About This Documentation Breakdown of Topics 0 S erver Manager 05/200 9
You can access the online documentation from any component via the Help menu item in the global menu. Its content reflects the sections in the following handbooks: Open Text Web
Solutions, Server Manager, SmartTree, Content Classes, SmartEdit, and Asset Manager.
The context-sensitive Help is available in every dialog window. Click the Help button in the bottom left corner of a dialog window. This opens the Help, which provides information about the current dialog.
Breakdown of Topics
The documentation consists of three levels of headings: chapter, topic, and section. At chapter and topic level, the user obtains an overview of the contents of the chapters and topics. For SmartTree and Server Manager, the level headings correspond to the tree items described.
The dialog windows are described on the section level. A section consists of heading, activity flow chart, introduction, and operating procedure. In certain sections, a list of related topics will be included at the bottom of the page. The heading corresponds to the respective menu item. The activity flow charts and descriptions of the dialog windows follow a specific documentation syntax.
See also:
Activity Flow Chart (Page 9) Symbols (Page 11) Syntax (Page 11)
Conventions
The better your orientation within the documentation, the quicker you will be able to obtain the knowledge/information you need to carry out your work with Management Server. For this reason, the following conventions have been set up for this documentation:
Defined symbols Defined syntax
At the beginning of every section, an activity flow chart depicts how to navigate to the individual dialog windows in Management Server.
Activity Flow Chart
Navigation in Management Server is explained at the beginning of each section within a gray box (activity flow chart). The dialog windows can be opened in various ways. Many dialog windows have multiple activity flow charts defined for them.
About This Documentation Conventions 0 S erver Manager 05/200 9
The activity flow chart is not initially displayed in the online documentation. A page that has an activity flow chart has a symbol. Click the symbol to display or hide the activity flow chart.
In the following examples, the actual names have been replaced by generic terms.
Module Menu item/Tree item Select tree item Menu item in Action Menu Title of dialog window
Module might refer to SmartTree, for example, the program component (module) from which
further navigation steps are taken. In some cases, alternative paths are possible. The alternative paths are preceded by the word or in italics.
The symbols used have the following meanings: Symbol Meaning
The arrow symbol appears in combination with a menu item or tree item. It represents the beginning of the next navigation step or navigation event. A dialog window opening is one example of a navigation event.
The pointer symbol appears in combination with a user-specific item in a tree view. Meaning: Select the desired item in the tree view.
This pointer symbol is used for right-clicks. Right-clicking lets you open a shortcut menu that offers you different actions.
This is the symbol for the Action Menu. The Action menu lists all menu items available for a tree item you have selected. Meaning: Click the Action Menu item described after the symbol. This symbol is used for Server Manager, SmartTree, and Workflow Designer.
This is the symbol for the global menu. It is located in the area on the upper right of the Web Solutions user interface.
This symbol represents the Clipboard. Next to the symbol is the name of the objects that are in the Clipboard and that you have to select. This symbol is used for the Server Manager and SmartTree activity flow charts.
This is the symbol for an open dialog window. The name of the open dialog window is given after the symbol.
This symbol represents the work area in SmartEdit.
About This Documentation Conventions 0 S erver Manager 05/200 9
Symbols
The following symbols will be used in the documentation text.
Example
This symbol alerts you to examples of the described functions.
Tip
This symbol indicates tips on how to make better use of certain functions.
Information
This symbol indicates useful background information.
Warning
This symbol indicates a warning that must be taken note of.
Syntax
The documentation uses the following syntax:
Steps are numbered.
Software elements are identified in process steps by bold formatting (for example,
buttons or drop-down lists).
Dialog window titles are formatted in italics.
Program code and source code (for example, XML, XSL, and HTML) are printed in Courier
to differentiate them from the rest of the text.
0
S
erver Manager
05/200
9
About the Server Manager
In the Server Manager, you administer and edit settings for all projects, servers, and users. The following tree items are available for use with the individual settings:
Administer Application Servers - Here, you administer the connections to one or more
application servers. You can combine several application servers in a cluster.
Administer Users and Groups - This is where you administer the general project settings
for users and groups. You can also import users from other directory services.
Administer Projects - Here, you administer projects on this and other application
servers.
Administer Database Servers - Here, you administer the various databases of your
projects.
Administer User-defined Jobs - This is where you create and edit user-defined jobs.
User-defined jobs make it possible to execute periodic Administrator or Management Server tasks.
Administer Plug-ins - Create and administer any external scripts with the help of the
plug-in interface.
Administer Delivery Server - Create and administer the connection to a Delivery Server.
Management Server is installed on one server. Throughout the following documentation this server will be referred to as the application server.
You can only work in the Server Manager when you have been assigned the Server Manager module.
Topics covered in this chapter include: Accessing the Server Manager (Page 12) User Interface (Page 13)
Accessing the Server Manager
To be able to work with the Server Manager, the module Server Manager must be assigned to you. The user set up during the installation automatically has access to the Server Manager module. All other users are created in the user administration of the Server Manager. All of the user settings for, for example, modules, roles, project assignments, etc., can be modified at any time.
See also:
Users/Groups by Projects (Page 68) Users (Page 74)
About the Server Manager User Interface 0 S erver Manager 05/200 9
User Interface
The Server Manager user interface is divided into the following sections:
The Tree View lets you administer the project structure using the Action Menu. The Action Menu provides specific options for editing the individual tree items. Tree items can be connected via the Clipboard.
See also: Tree (Page 13)
Action Menu (Page 14) Clipboard (Page 14)
Editing Clipboard Content (Page 15)
For information about the Web Solutions user interface, see the Open Text Web Solutions documentation.
Tree
Server Manager
The tree displays the essential editing area in Server Manager. The first item in the tree is called Start. The Server Manager tree lets you edit all administrative components of your projects.
Start
Administer Application Servers Administer Users and Groups Administer Projects Administer Database Servers Administer User-defined Jobs Administer Plug-ins Administer Delivery Server How to work with the tree items:
Opening tree items - To open tree items, click the in front of the corresponding tree
item.
About the Server Manager User Interface 0 S erver Manager 05/200 9
Action Menu
Server ManagerThe Action Menu of the Server Manager is located at the top right-hand side. In the Action Menu, all editing options for the selected tree item will be displayed.
Action Menu
In the screen shot below, the Projects tree item has been selected. In the Action Menu, you can see all the menu items that are available for the Projects tree item:
The Action Menu items, Create Project, Import Project, and Check Database Server, are available for the Projects tree item.
If you click the icon in the Action Menu, you will get support-relevant information about the tree item selected in the Element Info window.
Clipboard
Server ManagerThe Clipboard is located at the right bottom of the Server Manager. You can create shortcuts for tree items in the Clipboard by double-clicking the corresponding tree item. The Create Shortcut in Clipboard menu item in the Action Menu is available with some tree items. Tree items in the Clipboard can be connected to other tree items.
About the Server Manager User Interface 0 S erver Manager 05/200 9
Creating Shortcuts in Clipboard
A user is to be added to a different group. Create a shortcut in Clipboard for the user and connect him or her to the corresponding group in the tree via Clipboard.
See also:
Creating Shortcuts in Clipboard (Page 88) Connecting to Users in Clipboard (Page 72) Creating Shortcuts in Clipboard (Page 71) Connecting to Groups in Clipboard (Page 70)
Editing Clipboard Content
Server Manager
Tree items that you have noted in the Clipboard can be edited. For this, use the Clipboard functions.
How to use the Clipboard functions:
Refresh Clipboard - Update the contents of the Clipboard with this function. Select All - With this function you can mark all of the elements in the Clipboard. Undo Selection - This function removes all marks in front of the elements in the
Clipboard.
Remove Selected Entries - This function removes all marked elements from the
Clipboard.
Display Element in Tree - Click on this arrow icon to display the position of the
0
S
erver Manager
05/200
9
Administering Application Servers
The application server is the server on which the Management Server software is installed. All data and objects are stored on the application server. This means that all project user data, files, content classes, for example, are stored and administered here.
You can operate several application servers in a cluster. Topics covered in this chapter include:
Application Servers (Page 16) Editing Connections (Page 28) Projects (Page 38)
Classes (Page 41) Log Files (Page 42)
Application Servers
For each application server, you can view and edit the asynchronous processes and back up and restore the Administrative Notes of the administration database.
Administration data comprises all the data administered using the Server Manager, for example, users and groups, projects, or global releases.
You can view and edit asynchronous processes located on application servers. You need both of the following dialog windows if you intend to administer multiple application servers in a cluster.
A cluster consists of multiple application servers that access the same administration database (ioadministration) of a database server.
Not all asynchronous processes can be managed in clusters. You can use and administer the following processes in the cluster:
Automatic and manual publishing jobs Escalation routines for the workflow
For more information on installing clusters, see the Installation documentation.
Administering Application Servers Application Servers 0 S erver Manager 05/200 9 Asynchronous Processes
Management Server is a Web-based application. Whereas other client applications can wait for a server response, this is hardly possible for a browser-based client. For this reason, time-consuming program functions, like page publication, are initiated without requiring the client to wait for execution. The client merely receives confirmation that a function has been started. These special independent program functions, known as asynchronous processes, can be executed concurrently on a server. When an asynchronous process is complete, this is logged in a log file. If e-mail notification has been preset, the user is notified via e-mail that the process is complete.
Administering Asynchronous Processes
Server Manager Start Administer Application Servers Application Servers Administer Asynchronous Processes Administer Asynchronous Processes
Time-consuming functions are executed asynchronously in Management Server so that users can continue working optimally, even during complex processes. These program components are identified as asynchronous processes. These include more complex program
components, for example, publications and project imports/exports, as well as less complex components such as sending e-mail or deleting pages. In total, around 60 different types of asynchronous processes occur in Management Server. Because users usually trigger these asynchronous processes unknowingly, it can lead to performance problems if multiple processes are triggered simultaneously.
The Process Manager component controls these asynchronous processes. Process Manager ensures that not too many processes are started at once. The asynchronous processes form a queue before they are processed. This avoids a system overload.
Process Manager is configured with useful default values after installation or updates so that you do not have to modify the configuration. Modifications to the configuration are
sometimes useful when the server is not very busy and there are too many processes waiting. This is also the case when the server is overloaded because too many processes have been started. Only in cases such as these should you consider modifying the configuration. To do this, contact Support or Professional Services for guidance.
The Administer Asynchronous Processes dialog window gives you an overview of the processes that run in a cluster on all application servers or that are waiting to be executed. You can stop, end, or change the priority of processes.
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
The shortcut menu that opens when you right-click provides different actions for the individual items:
Application Server Actions
Shut Down Process Manager - Process Manager is shut down on this application server;
asynchronous processes are no longer executed on this application server. Here you can select:
End Processes - All running processes are ended and Process Manager is shut down. Wait Until Processes Are Completed - All running processes are completed before
Process Manager is shut down.
Refresh - Refreshes the dialog window display.
Queue Actions
Pause - No new processes are started in this queue. All active processes continue
running. You can restart a queue that has been paused by clicking Resume in the shortcut menu.
Refresh - Refreshes the dialog window display.
Active Process Actions
Stop - The process is given the signal to stop. This function is not supported by all
processes.
End - The process is ended.
Set Priority - The priority is changed to the selected setting.
Actions for Executing Pending Processes
Remove - The process is removed from the queue.
Position - The process is moved to the queue according to the selected setting.
Dialog Window Keyboard Shortcuts
You can use the following keyboard shortcuts in the Administer Asynchronous Processes dialog window:
R - Refreshes the selected item in the left of the dialog window. F8 - Refreshes the entire dialog window.
Operating System Processes for Asynchronous Processes
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
Windows service with the name RedDot.CMS.ProcessServer.Service. Process Manager runs within this service. In the Task Manager, the process is called
RedDot.CMS.ProcessServer.Service.exe. All asynchronous processes are executed
in threads within this operating system process.
Assigning Processes to Queues
There are six queues in Process Manager with the following assignment of functions: Default Manager
All asynchronous functions that are not triggered by the following
Instant Manager
Clear page cache
Refresh page caches in the cluster Refresh image caches in the cluster
Save version information for a page if it has been changed
Asynchronous Queue
Update Asset Manager Export assets to a directory Import files into Asset Manager Move assets
Delete assets
Shrink the versioning database Send e-mail
Publication
Workflow reaction: Publish Page Export instances of content classes
Notification when the application server cannot be accessed in the cluster Check all external URLs in a project
Check all references in other projects
Workflow reaction: Automatic Expiration and Resubmission of Pages Inherit publication package to following levels
Disconnect publication package from structural element and following levels Create project reports
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
Check spelling in page(s) using Web Compliance Manager Find and replace
Start applications before/after publication Check database servers
Publishing Supporter
FTP transfer, transfer to Delivery Server, delete files from the live server Delete files from the live server
Live Server Cleaning
Clean up live server
WebCompliance
Check pages for Web compliance
Administering Publication and Scheduled Processes
Server Manager Start Administer Application Servers Application Servers Administer Publication and Scheduled Processes Administer Publication and Scheduled Processes
or
SmartTree Start Administer Project Structure Project Administer Publication and Scheduled Processes Administer Publication and Scheduled Processes
You can view the properties of all publications and scheduled processes that run on the application server. You can start, deactivate, activate, and delete processes. When you open this dialog window in SmartTree, only the processes of the current project are displayed.
Using the Process List
Use the process list to do the following:
Which processes and how many are currently running or waiting to be run on the
selected application server
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
The process list is ordered according to when a process is scheduled to begin on a specific application server. The active process is listed first, followed by the next scheduled process, while the lowest priority processes and those scheduled to run last are listed at the bottom. If you open the process list in SmartTree, only the processes corresponding to the current project will be displayed.
The process list contains the following information for each process: Status
The first column informs you about the process status. The process status is indicated by symbols. Black symbols indicate active processes and grey symbols indicate deactivated processes. The actions determine the display of a status.
Priority
This column indicates the priority with which a process is handled. There are three levels of priority for a process. These are: low, normal, and high. All processes have the normal priority by default, except for publishing processes, which can have a different priority. A publishing job can have a different priority. You can set this priority already in the publishing job. To create a publishing job, go to the Administer Publication tree item in SmartTree. The following symbols are used:
Symbol Meaning
The process is currently being executed. The process has been stopped.
The process is waiting to be executed.
The process is still being executed and will be deleted afterwards. The process is still being executed and will be stopped afterwards. The process has been stopped and will be deleted immediately. The process has been stopped and will be started immediately. The process is waiting to be executed and will be deleted immediately. The process is waiting to be executed and will be started immediately. The process is waiting to be executed and will be stopped immediately.
Symbol Meaning
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
Processes with normal priority do not have symbols. You can set the priority of a process in the process properties area. Click the process name to change the priority of a process in the
Process Properties dialog window.
Process name
The Process name informs you about the process. To get more information, click the process name to display its properties. For more information, see the Process Properties section. Category
The Category tells you what type of process is performed. Possible categories include, for example, publication and escalation procedure.
Next execution
With processes that are waiting to be executed, the Next execution field displays the date scheduled for its next execution. With processes that are currently being executed, it displays when the process actually started.
Application server
Application server displays the application server assigned for this process (processes waiting to be executed). If the process has not started yet, you can use the process properties to change the assigned application server manually. If a process is currently being executed, the active application server is displayed here.
Actions
You can use Actions to make changes to the processes. The following actions are available: Stop process
Use this function to stop an active process ( ) or one waiting to be executed ( ). This function does not immediately stop an active process but waits until the current steps in the publication process have been completed. The process remains stopped until it is deleted or restarted. If a process has been deactivated, nothing happens until the process has been reactivated.
Start process
Use this function to restart a process that had been stopped ( ). You can also use it to jump the queue and immediately start a process that is waiting to be executed ( ). This only takes place if no other process is waiting on the application server with a higher priority. If this is not the case, the process waits to be executed and the following symbol is displayed: . In general, you can never start a deactivated process using this symbol.
If a process with an automatic - that is, periodic - publishing job is completed, the new execution date is displayed and the process receives the Wait status ( ). The same applies for escalation procedures. The name of a manual publishing job is removed from the list upon completion.
Delete/cancel process
You can cancel any recurring process (automatic publishing jobs, escalation procedures) that is currently active. If it is canceled, the next execution date is entered automatically. If this is an automatic publishing job, the new publication date is entered. To prevent the execution of a recurring process, you need to deactivate it. The appropriate symbol is then displayed in the process list.
Administering Application Servers Application Servers 0 S erver Manager 05/200 9 Deactivate process
To cancel not only the current process but also any future execution of an automatically running process, you have to deactivate the process. A process that has been deactivated is displayed with light gray status symbols in the first column.
You can only undo the Deactivate action by executing the Activate action. For example, if you want to start a deactivated process, you first need to activate it.
Activate process
A deactivated process can be executed again using the Activate action.
If the next execution date has already passed in the deactivated period, the process will be executed as soon as possible. In the case of recurring processes (automatic publishing jobs, escalation procedures), these are only executed once rather than in the scheduled frequency. Afterwards, a new execution time is determined.
See also:
Process Properties (Page 23)
Process Properties
Server Manager Start Administer Application Servers Application Servers Administer Publication and Scheduled Processes Administer Publication and Scheduled Processes Select process name Process Properties
or
Server Manager Start Administer Application Servers Application Servers Administer Publication and Scheduled Processes Administer Publication and Scheduled Processes Select process name Process Properties
You can view process properties and edit processes. The Process Properties dialog window contains all important process information. You can specify the application server where you want the process to be executed and define the priority.
Process Properties
You can only alter process properties as long as the process has not been started.
A process contains the following information: Process name
Administering Application Servers Application Servers 0 S erver Manager 05/200 9 Status
This column informs you about the process status. The process status is indicated by symbols. Black symbols indicate active processes and grey symbols indicate deactivated processes. The actions determine the display of a status.
Executing application server
If the process has been started, this drop-down list is deactivated. It contains a note about the application server where this process is being performed. If the drop-down list is available, you can determine the executing application server. An individual alteration is only applied for the current process execution. If it is a repeated process, the preset application server is used for each repetition. You can select the preset application server below the Application server entry (at the bottom of the dialog window).
Category
Informs you about the running process job, for example, publication or escalation. Application server
Specifies which server is responsible for the process. If the process has not been started yet, this entry can be overwritten by the Executing application server entry (at top of the dialog window).
Project
Specifies the project for which the process is being executed. You can select a different priority from the drop-down list. You have the following options: low, normal, and high. Last execution
Specifies the time (date and time) of the last execution of the recurring process. Last execution by
Specifies the name of the user who initiated the last execution of the current process. If (SYSTEM) is shown instead of a user name, the process was automatically started by the system.
Symbol Meaning
The process is currently being executed. The process has been stopped.
The process is waiting to be executed.
Administering Application Servers Application Servers 0 S erver Manager 05/200 9 Next execution
Specifies the time (date and time) of the next planned process execution. Next execution by
Specifies the name of the user who initiated the current process for the next execution. There may be a certain amount of time between the initiation and the actual execution of a process. If (SYSTEM) is entered instead of a user name, the process will be started by the system for the next execution.
Priority
Specifies the priority with which the process is executed. This entry can be changed if the process has not started yet.
Created on
Specifies the time (date and time) when this process was created.
Created by - Specifies the name of the user who created the process. If (SYSTEM) is shown instead of a user name, then the process was created automatically by the system.
Process ID
Specifies the process GUID. Actions
You can use Actions to make changes to the processes. The following actions are available: Start process
Use this function to restart a process that had been stopped ( ). You can also use it to jump the queue and immediately start a process that is waiting to be executed ( ). This only takes place if no other process is waiting on the application server with a higher priority. If this is not the case, the process waits to be executed and the following symbol is displayed: . In general, you can never start a deactivated process using this symbol.
If a process with an automatic - that is, periodic - publishing job is completed, the new execution date will be displayed and the process receives the Wait status ( ). The same applies for escalation procedures. The name of a manual publishing job is removed from the list upon completion.
Delete/cancel process
You can cancel any recurring process (automatic publishing jobs, escalation procedures) that is currently active. If it is canceled, the next execution date is entered automatically. If this is an automatic publishing job, the new publication date is entered. To prevent the execution of a recurring process, you need to deactivate it. The appropriate symbol is then displayed in the process list.
Other processes currently being executed can be canceled and deleted at the same time. The process will then no longer appear in the process list.
Deactivate process
To cancel not only the current process but also any future execution of an automatically running process, you have to deactivate the process. A process that has been deactivated is displayed with light gray status symbols in the first column.
You can only undo the Deactivate action by executing the Activate action. For example, if you want to start a deactivated process, you first need to activate it.
Activate process
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
If the next execution date has already passed in the deactivated period, the process will be executed as soon as possible. In the case of recurring processes (automatic publishing jobs, escalation procedures), they are executed only once rather than in the scheduled frequency. Afterwards, a new execution time is determined.
See also:
Administering Publication and Scheduled Processes (Page 20)
Backing Up Administration
Server Manager Start Administer Application Servers Application Servers Back Up Administration Back Up Administration
When you back up the ioAdministration administration database, the information is saved to a file in XML format.
Administration data comprises all the data administered using the Server Manager, for example, users and groups, projects, or global releases.
1. Make the following backup settings:
Path - In the Path box, enter the path and administration database directory whose
administration data should be saved, or click Search to select a directory. You can use the Check link to see if the information you entered for the path is correct.
File name - Enter a file name of the administration database.
E-mail confirmation - You can be informed of the completion of the backup process
via e-mail.
2. Confirm with OK and a backup of the administration database will be made.
Restoring Administration
Server Manager Start Administer Application Servers Application Servers Restore Administration Restore Administration
The settings of the Administration database are saved in a file in XML format. When you restore these settings, they are imported to the existing Administration database of the application server. The settings in the existing Administration database are overwritten. 1. Edit the following settings:
File name - Enter the file name of the administration database you want to restore. E-mail confirmation - Enter an e-mail address to be notified when restoration is
complete. 2. Click OK to confirm.
Administering Application Servers Application Servers 0 S erver Manager 05/200 9
Showing Licenses in Use
Server Manager Start Administer Application Servers Application Servers Show Licenses in Use Management Server
You can display the licenses used for the individual modules. 1. This dialog window provides the following information:
It shows the number of available licenses for the SmartTree and SmartEdit modules,
and the number of licenses in use. For all other modules, you can see whether a license is available. You cannot edit this dialog window. For more information, contact your sales representative.
2. Click Close to close the dialog window.
Creating Support Information
Server Manager Start Administer Application Servers Application Servers Create Support Information Create Support Information
Support information includes all technically relevant information for your system, which is sent as e-mail to a specific recipient. This data makes all information about your support queries quickly and readily available, thereby supporting your work. The e-mail contains a ZIP file attachment, which itself contains a server report as well as configuration and log files. You can open and view all files in a text editor.
1. You have the following options:
Level - Select a level from the drop-down list to apply to the support information. The
levels differ in the amount of detail that is provided in the server report. The report for the Standard level contains all information relevant to the system and the servers used. The report for the Extended level contains additional information on content classes for all projects.
E-mail recipient - Enter the e-mail address where you want to send the support
information.
Subject - Enter text for the subject of the e-mail. Message - Enter text for the e-mail message.
2. Click OK to confirm.
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
Editing Connections
Via the central application server, it is possible to co-administer connections to other application servers and also have direct access to their projects.
Editing Connections
Server Manager Start Administer Application Servers Application Servers Select Application Server Edit Connection Edit Connection
You can edit the connection to an application server. 1. Edit the connection.
Connection name - Enter a unique and meaningful name for the connection in the
box. The connection will be displayed in the tree under this name.
IP address - Enter the IP address or host name of the application server that you want
to connect (for example, 110.2.1.2).
Host header - Enter the name of the host header (for example, https://<Server
name>/cms) that addresses the virtual Web site and under which Management
Server has been installed. The host header name is used for internal IIS calls with RDExecute and PreExecute constructions. You enter it, for example, if you want to use a Web site other than the default Web site as the virtual Web site, or if a different server name has to be used for internal calls due to the network configuration. You can usually leave this box blank.
DNS name (cluster) - Enter the name of the DNS cluster in this box. This name is used
for the e-mail in which a link is provided to the page preview. In this way, the preview link calls the page via the official cluster URL and not via the application server from which the e-mail was sent.
Note:
If you want to make use of the HTTPS protocol for the preview links, you need to enter the server name with the protocol (for example, https://<Server name>/<Web
directory>) in this box.
2. Click OK to confirm.
Modifying the Server Connection
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
Editing Settings
Server Manager Start Administer Application Servers Application Servers Select Application Server Edit Settings Edit Application Server Settings
In the Edit Application Server Settings dialog window, you define essential settings for log files, e-mail notification processing, and asynchronous processes, such as SSL encryption, HTTP port, escalation procedure, and session time-out.
If you received a new license key, it can be entered here. You can also obtain additional information about the number of licenses.
If your Internet connection is set up through a proxy, the proxy server area allows you to enter the required settings. This allows you to check the URLs defined in the project that refer to external links.
1. Edit the settings.
E-mail notification
Use default virtual SMTP server - Select this check box if you want to use the
default server.
Name/IP of mail server - Enter the IP address or host name of the mail server that
you want to use for the e-mail notification.
From - In this box, enter your name as it should appear with outgoing messages. It
can take the form of an e-mail address or server name. For example:
[email protected] or company.com.
User name, Password - Enter the account name and the password that your
Internet service provider has given to you for accessing the SMTP.
Port - Enter the port of your mail server.
License
License key - This shows the license key that was entered during installation. If
you have a new license key, follow the steps below: 1. Enter your License key.
2. Click OK to confirm.
Check - Click this link to open a dialog window that will inform you about
available licenses and their validity. If the current application server is part of a cluster, this link is available for one application server only.
Asynchronous processes
Query interval - Here you can enter the interval (in seconds) of how often the
application server should search the database server for new asynchronous processes waiting to be completed. The default setting is 60 seconds.
Number of simultaneous processes - Here you can define how many
simultaneous asynchronous processes this application server should accept. Select one of the following settings:
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
0 = The application server is not allowed to start any processes.
1 - 500 = Insert the number of processes (max. 500) that may be performed
simultaneously on the application server.
Log file settings - Decide here which events should be logged and where the log files
are to be saved.
Home directory - Enter the path for the home directory of the log files. In this
home directory, subfolders are automatically created for the individual log files when the first log file is written. You can enter a path on the application server or the UNC path of another accessible computer. If you do not enter a path, the log files are written to the default log directory, <Installation directory>\Open
Text\WS\MS\ASP\LOG. Changes to the directory path become effective as soon
as you close the dialog window. Note:
In a cluster installation, different physical directories must be entered for each server. Because the installation log files are created before Management Server is started, they are always found in the default log directory. The same applies to the
dberror.log log file in the Common subdirectory.
User name - Enter the user name that you use to log on to the server where the log
files are to be saved.
Password - Enter the password for the user name.
No logging - Select this option if you do not want any events to be logged. Full logging - Select this option if you want to log all events.
Other settings
Permit ActiveX controls - Select this check box to allow ActiveX controls. You also
need to enable ActiveX controls in Internet Explorer under Tools -> Internet
Options -> Security. ActiveX controls are used for the following functions:
The drag-and-drop operation in the text editor
For more information, see the Text Editor section in the SmartTree documentation or Help.
The drag-and-drop operation in SmartEdit
For more information, see the Editing Content Elements chapter in the
SmartEdit documentation.
Using Microsoft Word as the text editor
For more information, see the Editing Content Elements chapter in the
SmartEdit documentation.
Refresh task alert - Use the drop-down list to define whether the task alert
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
Do not allow profile changes - Select this check box to prohibit users from
changing their profiles during the logon procedure. If selected, the logon menu will not display the Edit profile after logon check box. For application servers in a cluster, this setting only applies to the current application server. This allows you to selectively activate this function for specific application servers in a cluster.
Only permit logon using SSL encryption - Select this option to specify that logon
to the application server must use SSL encryption.
Stop SSL encoding after logon - The virtual directory can be secured completely
or partially by the SSL (Secure Sockets Layer). SSL is not provided with
Management Server. It can be purchased from an appropriate supplier. Determine whether or not SSL encoding is applied only during logon to the application server.
HTTP port - Management Server requires this port specification in order to find
the correct port when changing from HTTPS to HTTP. The default port is 80. If this port cannot be accessed, you will not be able to change to HTTPS.
HTTPS port - HTTPS is a secure version of the generally applied HTTP. The default
port is 443.
Checking interval for asynchronous workflow reactions - Here you can define
the interval for checking workflow reactions such as the escalation interval or automatic page expiration. The default setting is 30 minutes.
Session-Timeout - Enter the number of minutes that should elapse before a
session times out. The default setting is 70 minutes. If several application servers are organized into a cluster, this value applies to the entire cluster.
RDExecute-Timeout - Enter an interval in seconds. The timeout takes effect in the
execution of server-side script code. The default setting is 10 seconds. If you enter a value lower than 10 seconds, the value of 10 is saved automatically.
PreExecute-Timeout - Enter an interval in seconds. The timeout takes effect in the
execution of active templates. The default setting is 10 seconds. If you enter a value lower than 10 seconds, the value of 10 is saved automatically.
Private digest element - Enter the private section of a digest which was created
with the MD5 algorithm. This is only necessary if, for example, you want to enable authentication for a portal integration using a digest. For more information, see the information box below.
Validity of digests - Enter a validity for the digest in minutes. For more
information, see the information box below.
HTTP Proxy server - Select this check box if you intend to use a proxy server. Proxy server - Enter the name of the proxy server you intend to use. Proxy server port - Enter the designated port of the proxy server.
Use external PDF converter - Select this check box if you intend to use an external
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
converted by the external converter. Once the converted file lands in the Conversion directory, the PDF file is adopted in Management Server. Depending on your settings, the source file is deleted from the preconversion directory and the converted file is deleted from the conversion directory.
Conversion input directory - Enter the path to the preconversion folder. Conversion output directory - Enter the path to the conversion folder.
After converting file delete it from preconversion folder - Select this check
box if you want to delete the files contained in this directory after they have been converted.
After converting file delete it from conversion folder - Select this check box
if you want to delete the files contained in this directory after they have been converted.
Automatic user log on.
IIS authentication - Select this option to allow user logon with IIS authentication.
For more information, see the information box below.
Activate logon via a saved cookie - You can control user logon by using saved
cookies.
Length of validity of cookies in hours - Enter the length of time that a cookie
should be valid (in hours).
Cookie name - Enter the name of the cookie.
2. Click OK to confirm.
Notes on IIS Authentication
Management Server can also make use of the logon information provided for a Windows user, which means that no additional logon is required.
Setting Up IIS Authentication Configure the following settings:
1. Open Internet Information Services on your application server. 2. Open the CMS folder under Default Web Site.
3. Open the shortcut menu for the WinAuth subfolder and select Properties. 4. Select the Directory Security tab and click Edit in the Control anonymous
access and authentication area.
5. Clear the Anonymous logon check box and, depending on the situation in your network, select one of the check boxes for Authenticated Access.
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
Access Violations on RDCMS_XMLServer COM+ Component Access violations may occur when accessing the COM+ component
RDCMS_XMLServer because once authentication via IIS is complete, all ASP pages are authenticated using the authenticated user's identity. You have the following options to correct this situation:
Deactivate Windows authentication in IIS for the CMS directory
You can clear all of the check boxes for the virtual IIS directory CMS in the Authenticated Access area and just allow anonymous access. This means that the user (after authentication against IIS) makes use of the anonymous user identity.
If default settings are valid for this directory during installation, the modification is executed by the installation routine.
Extend access authorizations
Add users or groups to the RedDotRole for the components. Add the users/ groups that are able to log on using IIS authentication.
Deactivate the access test for this COM+ component
To deactivate the access test for this component, call up the component properties, select the Security tab, and clear the Enforce access check for this application check box in the Authorization area.
Notes on Configuration in Management Server
Select IIS authentication in the application server settings in Server Manager. Authentication also works for users from the internal account system.
When importing users from other directory services, you can determine whether
you want to allow IIS authentication for them. IIS authentication is permitted by default.
Circumventing IIS Authentication
IIS authentication can be deactivated by adding the DisableAutologin=1 parameter to the URL. The logon dialog URL would then look like this: http://servername/cms/
ioRD.asp?Action=ShowLoginMask&DisableAutologin=1
Notes on Integrations
Because this method of authentication does not use passwords, it is not
recommended. Otherwise, care must be taken when integrations, for example, require user name and password authentication.
Identical Users in Different Domains
Management Server cannot differentiate between users with the same names in different domains. This means, for example, that two users could log on to
Management Server with the same user name. In such a case, you need to deactivate the logon authentication via IIS for both users.
Using IIS Authentication from Outside the Domain
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
perceived as a security risk, IIS authentication logon from outside the domain should not be used. In this case, the simpler direct Management Server logon should be used instead.
User Authentication Using a Digest
It is possible to identify and authenticate a user in Management Server using a digest that was created with the MD5 algorithm. This authentication method can be used for portal integrations. Authentication requires three steps:
The portal integration sends a digest to Management Server as part of a URL. Management Server checks the authenticity of the digest.
If the digest is correct and valid, the user is logged on to Management Server.
Step 1: The portal integration sends a digest to Management Server as part of a URL
The portal has to include the digest in the URL that opens the required page in Management Server. In the following example of a URL for editing a page in SmartEdit, the Digest parameter is required for authentication:
http://<application server>/cms/ioRD.asp?Action=ShowLoginMask&LngId=EN& LanguageVariantGuid=B54519BEE72247AF923E93B0C4FB34B7& ProjectGuid=673C95D9F64B4620AA1A7356C31A107F& PageGuid=CF8EF604980A4090A0C6B5C0146AF737& LinkFromGuid=BDB85B530F204137A8DA58E0509CBB9A& Digest=username%7C4F1B7D2C6ADE48F3B5CE681397783B7C%7C200507121 70242%7C%2B02%3A00%7C7F87E067072DE6355A81B976CE9AC32A
Structure of the body of the digest
The digest body comprises several elements, which have to be separated by pipe (|) characters. The body of the digest contains the digest created by the portal
integration, as well as three significant elements. These are the user name
(Loginname), the time stamp (Timestamp), and the GMT time bias (TimeBias). There may be any number of elements between the logon name and the time stamp, to increase the variance of the digest. The digest does not transmit any passwords. Because the pipe character is used as a separator for the various digest elements, the digest elements must not contain this character.
An overview of the body of the digest: Loginname|...|Timestamp|TimeBias|Digest
Loginname
No particular formatting rules apply to the logon name. The only rule is that the pipe character (|) is not allowed.
Timestamp
Format: yyyymmddHHnnss (YearMonthDayHourMinuteSecond).
The year must be entered as a four-digit number, all other values as two-digit numbers. The time must be entered in 24 hour format.
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9 TimeBias Format:[+/-]HH:nn (SignHour:Minute).
The plus or minus sign must be entered. All numeric values must have two digits. The time must be entered in 24 hour format.
Example: +13:00
Digest
The digest must be entered as a hexadecimal number. All letters must be upper case, and all numeric values must have two digits.
Example: 7C072DE6355A81B976CE9AC32A
Step 2: Management Server checks the authenticity of the digest
To check the authenticity of the digest, Management Server creates another digest. It uses all characters in the digest body transmitted, except for the digest from the portal and the pipe that precedes it. Management Server adds the pipe character and the private section of the digest to determine the digest. You enter the private section of the digest in the application server settings, in the Private digest element box. If the digest determined matches the digest from the portal, the time stamp is used to check the age of the digest. The digest is valid if the age is less than the value specified in the Validity of digests box.
Step 3: If the digest is correct and valid, the user is logged on to Management Server
If a valid digest and a valid Management Server logon name are transmitted, the user is logged on and directed to the page specified. No further authentication in Management Server is required (logon dialog, cookie authentication etc.). If there is no free user session, the user session that has been inactive for the longest time is used.
Changing the License Key
When you change the Management Server license key, all the modules and roles assigned to users are checked and updated. If the number of licenses has been reduced for a specific module, the module assignment is adapted accordingly. Example: Ten users have been assigned the SmartTree module. The new license key contains only four SmartTree licenses. Thus, six of the ten users will no longer be able to use the SmartTree module. Their project roles will be adjusted accordingly. Management Server checks each user ID to determine whether a user is allowed to keep his or her module, starting with the user who has the lowest level user ID.
Administrators with the Server Manager option can change this automatic
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9 Escalation Requirements
To ensure that the escalation will work properly, the following requirements must be met:
An e-mail (one or more) must be set up as the escalation reaction to the release
level in the workflow.
A time must be set in the workflow reaction of the respective release level that
applies to the escalation reaction.
In the Task Manager, check whether the GenDispatcher has started.
If you now create or edit a page and submit it to the workflow, the page will be submitted for release according to the usual workflow. If the page is not released within the set time limit (escalation time in hours), the escalation reaction is triggered and e-mail is sent out. The procedure is repeated in accordance with the specified escalation interval.
The escalation procedure depends on the value that was configured in Server Manager under Checking interval for asynchronous workflow reactions. When the escalation procedure is set to one hour for the workflow reaction and the checking interval for the server is 120 minutes, it results in a query as to whether the escalation procedure should be set to 120 minutes. If necessary, change the server settings according to the desired escalation procedure.
Configuring ActiveX Controls in the Internet Explorer
To configure ActiveX Controls in the Internet Explorer, select Extras -> Internet Options
-> Security -> Custom Level for the Local intranet.
1. Edit the following settings for ActiveX controls and plug-ins:
1. Enable the option Script ActiveX controls marked safe for scripting. 2. Enable the option Initialize and script ActiveX controls not marked as safe. 3. Enable the option Run ActiveX controls and plug-ins.
4. Enable the option Download signed ActiveX controls. 5. Enable the option Download unsigned ActiveX controls. 2. Click OK to confirm.
Administering Application Servers Editing Connections 0 S erver Manager 05/200 9
Clearing the Language Resource Cache
Server Manager Start Administer Application Servers Application Servers Select Application Server Clear Language Resource Cache Management Server The language resource cache is used for displaying the user interface. Clear the cache if this is recommended, for example, by support.
1. Click OK to confirm.
The language resource cache is cleared.
Deactivating Servers
Server Manager Start Administer Application Servers Application Servers Select Application Server Deactivate Server Management Server
Use this Action Menu item when you have server clustering. 1. Confirm with Yes.
The server is deactivated and the Activate Server menu item appears in the Action Menu.
Activating Servers
Server Manager Start Administer Application Servers Application Servers Select Application Server Activate Server Management Server
This menu item is only displayed for application servers that have been deactivated. 1. Confirm with Yes.
Administering Application Servers Projects 0 S erver Manager 05/200 9
Projects
Using this tree item, you can administer projects that are available on the individual application servers and you can create new projects.
Creating Projects
Server Manager Start Administer Projects Projects Create Project Create Project
or
Server Manager Start Administer Database Servers Server Connections Select Server Connection Projects Create Project Create Project You can create new projects in Server Manager.
Management Server differentiates between live and test projects. When a project is created, it is created as a test project in accordance with the default settings. Live projects are projects with all of the functions and opportunities for export, backup, import, and publication. The number of live projects that may be created is limited by the license. If the number of live projects has been exceeded, the next project will be created automatically as a test project. Once a project has been designated as a live project, it cannot be changed. Test projects cannot be published. The number of simultaneous users is limited to 5. A test project can be transformed into a live project only once-if there is a project license available.
Naming Conventions for Projects
Do not use special characters or umlauts when creating new projects or changing the names of existing projects. Here is an example of a project name that would cause errors because of the hyphen: Project HAMPDEN-SYDNEY.
When you rename a project, you are actually creating a new name. The original database name remains intact. If you try to create a project with a database name that already exists, an error message will appear. In this case give the database of the new project a different name.
1. Configure the following Project registration settings:
1. Test project - Clear this check box to create the project as a live project.
2. Project name - Enter a unique and meaningful name for the project. The project will be displayed in the tree under this name.
Activate versioning - Select this check box to version project content.
Activate archiving - Select this check box to allow the archiving of pages in your
Administering Application Servers Projects 0 S erver Manager 05/200 9
3. Select the application server on which you want to administer the project from the Application server drop-down list.
4. Use the Database server drop-down list to select the database in which you want to store the project data.
If you select an Oracle database, the following boxes appear:
Schema - Enter the schema for the project. For more information, contact your
administrator or see the corresponding chapter in the Installation documentation.
Password - Enter the password for the project schema. For more information,
contact your administrator or see the corresponding chapter in the
Installation documentation.
If you select a server connection that you do not have authorization for, the following warning appears:
Note: The project database must be prepared and set up for the creation of a project. For more information, see the Installation handbook.
If you select an SQL database, the following box appears:
Database name - Initially, the name you specified in the Project name box is
automatically displayed in this box. You can change this name. 2. Configure the following in the Project settings area:
1. Language variant - Use the drop-down list to select the language variant in which the project will be created. The language variant you choose will be defined as the project's main language. You can change this setting again later. You can define additional language variants for the project.
2. Select the check boxes for the folders you want to create along with the project. The default names can be changed directly in the boxes. The following folders are available:
Content Classes - Folder for saving the content classes of your project. Images - Folder for saving the images of your project
Files - Folder for saving other files of your project
ftp://localhost - Publishing target for your project (modify this setting in
accordance with your FTP server). 3. Click OK to confirm.
The project is created.
Creating Full-text Indexes for the Page Search (MS SQL Server)
