Upgrading your Content Server on Windows Server OS
The current version of xCelerated Composition Platform (xCP) is version 1.5 (6.6 release). It is not possible to update the entire software platfrom 1.5 to 1.6 (6.7 release).
Note: Due to changes in the licensing of some 3rd party components that are used in the xCP Developer Edition, the 1.6 release has been delayed. Please watch this page for an announcement of its availability.
The first step is to upgrade the Content Server from the released version 6.6 to the current version 6.7 SP1. Here is the upgrade checklist with additional screenshots and comments.
checklist
Back up the repository.
Back up customized formats(dm_format objects)
Content Server 6.7 SP1 start installation
Run the consistency checker job or dmbasic syntax (optional, if you are not upgrading an new xCP installation)
Disable all jobs in the Documentum Administrator
Shut down the repository and the connection broker (docbroker) in the Server Manager
Shut down the Documentum Java Method Server services. Switch the start up method from automatic to manual to ensure that the services does not start automatically after a host restart.
Start the installation
install xPlore or FAST search engine (FAST is not supported)
Content Server 6.7 SP1 select search engine
select upgraderepository and docbrocker
Content Server 6.7 SP1 upgrade repository
don’t select create additional repository or docbrocker and finish the section
Content Server 6.7 summary information
finish installation, check install logfile in the source folder
restart the environment (check Java memory size in Windows Task Manager, check the Documentum Services in the Windows Services, check the log files in the new JBoss 5.1 folder)
stop the Application Server Service
deploy JBoss war files for Taskspace, Administrator etc. in the deploy folder
restart Application Server Service
install DAR applications (Taskspace, Administrator etc.) using Composer 6.7 DARInstaller
No Microsoft SQL Server or SQL Server Express installed No other Documentum software installed
Microsoft .NET 2.0 or higher (included in Windows Server 2008) Web Browser with Sun JRE 5.0 Update 22 or higher
RAM: A minimum of 4 GB
Free disk space: 5 GB Operating system:
Microsoft Windows XP SP3
Windows Vista SP2 (32 bit)
Windows Server 2003 SP2 Windows Server 2008 SP2 (32 bit /64 bit)
only english server version functional
install all available windows updates (Internet Exporer 9 not necessary) ~ 100 updates and patches June 2012
You must be logged in as a member of the Windows Administrators group, but notcnecessarily as Administrator
You can set default values for every standard or custom type. The possible values can be predefined or the result of a DQL query.
Every entry in the drop down list is a single custom object child of the custom type lov_entry. So you set or change the properties for each entry: e.g. valid or visible or change the display label individually. It is easy to administrate the values via DFS, because the entries will be maintained by the departments not by the administrators.
Lov_entry is a custom object based on dm_document. All dm_documents attributes are inherited. Additional attributes depend on your individual requirements. In this example we have lov_type, lov_code and lov_label etc. This is the parent object of all lov_entry value. You can mark the property Attribute cannot be blank, so the user must set a value for the attribute.
So,second create the lov_entry objects using DQL:
create "lov_entry" OBJECT set "object_name" = 'Department sector seven blue' set "lov_type" ='department' set "lov_code" = '7 blue' set "lov_label" ='Sektor Sieben Blau' set "lov_depend"= '0' set "is_valid" = 1 set "lov_lang" = 'de'
is_valid: 0 (FALSE)
is_valid:1 (TRUE)
Check all your entries in the DQL Tester:
select * from lov_entry WHERE lov_type ='department'
Value mapping
The type lable is the name of the custom object displaying in the dropdown list. If you create a dm_document related object this is will be shown on the document type list.
Use the Conditional Assistance and inset a tested DQL query like
select lov_label from lov_entry WHERE lov_type ='department' AND is_valid = 1 ORDER BY lov_label ASC
Check your DQL carefully! The install process will stop with an error message, if the query result is not valid.
Display Configuration
Configure the visible display values
Configure the visible object attributes. It is possible to create a custom properties label. Add all custom attributes from the left to the right. You can reorder the attributes if you move the selected value up or down.
Select only the custom attributes
Installing
Finally install the custom type and the value mapping into your environment.
If the changes are not visible after installing run the Data Dictionary Publisher job manually.
additional information on the properties tab for the custom object
xCP 1.x compatible
