Documentation Center

Upgrading Contenta Client

The upgrade program may prompt you to replace files on your system.

About this task

AnswerFor:
YesSDL software product files—that is, XPP software files or, if applicable, previously installed Contenta files.
NoThird-party software files.
On Windows clients only, you can opt to do the installation on a single client and create a response file that can be used to do a silent upgrade installation of the remaining systems. See the Performing a Silent Upgrade topic.

Procedure

  1. Log in to the client workstation as a user with administrator privileges.
  2. Perform the tasks as indicated in the Before You Upgrade topic.
  3. Windows only: to prevent the installer from complaining that another install is in progress, before beginning the installation, stop the Windows Installer service, reboot, and restart this service as follows:
    1. Display services from the Control Panel.
    2. Right-click on the Windows Installer service, and then click Properties.
    3. Click Manual in the Startup type field, and then click Stop.
    4. Click OK in the services window, and then reboot the system.
    5. After rebooting, log in as a user with administrator privileges and display the services from the Control Panel again.
    6. Right-click on the Windows Installer service, and then click Properties.
    7. Select Automatic in the Startup type field, and then click Start.
  4. Mount the installation ISO file on the Web Server system using one of the methods described in the following table.
    OSMethod for mounting the installation ISO file
    WindowsUse Windows to extract the ISO to the file system or use a third party tool to mount the ISO as a disk.
    Linux
    1. From a command prompt, type: mkdir /mount-point (where mount-point is the name of the directory where you will mount the ISO).
    2. Type mount -t iso9660 -o loop cdrom.iso /mount-point (Where cdrom.iso is the name of the ISO file and mount-point is the directory you just created.
  5. Launch the installer executable file (setup.exe on Windows, or install.bin on Linux).
    The installation program begins, displaying a page with general information about the installation. If you are upgrading from a previous version of Contenta, the system displays a message indicating the currently installed version and prompting you to confirm you want to continue.
  6. In the Welcome window, click Next.
  7. Contenta 3.2 upgrade or if Perl is not installed: in the Perl Destination window, click Next to install Perl in the default location or click Browse to choose an alternative location.
  8. Select the database you are using with Contenta, and then click Next.
  9. In the Contenta Server Settings window, click Next if the server or socket number has not changed. If changed, enter the new data.
    The default values are from the registry entries and should match the current configuration.
    FieldEnter:
    Server NodeThe Contenta Server name or IP address.
    SocketPcmPortal number running on the Server Node.
  10. Click Next.
  11. Oracle only: in the Oracle Home Directory window, verify or correct the path name to the version of Oracle to use with SDL Contenta, and then click OK.
  12. In the Contenta Database Information window, confirm the following database information:
    FieldEnter:
    Database Name Default Contenta database name.
    ODBC DSNContenta Administration clients only

    The ODBC DSN name.

    See the Before You Upgrade topic.

    Oracle SIDContenta Administration clients only

    Oracle only: The SID as specified in the tnsnames.ora file.

    Contenta Administration clients refers to client workstations that were installed with the Custom option for Contenta administrator users.

    The values entered in the Database Information window are written to the registry and assumed to be the default if not required or specified when executing some Contenta programs. See the SDL Contenta Explorer User Guide publication to specify an alternate database name or service name as an option in the Contenta Explorer application.

  13. 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 or unixuser.dat file and read by WS applications and Perl wrappers.
  14. Click Next.
  15. If upgrading a user workstation (non-administration client), skip to Step 17.

    If upgrading a Contenta Administration client, in the Setup License Server window, enter:

    FieldEnter:
    Server NameServer name or IP address

    This is the server where the license file resides.

    Server SocketPort number

    The default port number is 5053.

    Note: this is not the PcmPortal number.

    If not using the default socket number, after installing see the Alternate Reprise License Socket Number topic.

    Click Next.

  16. When the installation is complete, if you are prompted to reboot your system click Yes, I want to restart my computer now.
    SDL recommends that you reboot your system after upgrading the software.
  17. Post-installation notes:
    • Windows 7, 8: If you installed a Windows 7 or Windows 8 client, follow the Required Post‐Installation Steps for Windows 7 or Windows 8 topic.
    • Using OCI or ODBC versions of verilk: See the Hiding the default user name in Contenta login screens topic.
    • If Contenta Server and Contenta Client are installed on the same machine, update the registry before you continue. See the Configuring Contenta Client topic.
    • GlobalEd and Arbortext Editor: If you are using Globaled, and PTC Arbortext Editor was installed before you installed/upgraded Contenta, open the _main.acl file with a text editor and remove the lines appended by the Contenta install/ upgrade as noted.

      These lines source ACL files that are used exclusively by the Contenta Arbortext tool. The code in these sourced ACL files conflict with ACL used by Globaled.

      To configure Arbortext properly for use with GlobalEd in Contenta, open the file:

      C:\Program Files (x86)\Arbortext<version>\packages\_main.acl.

      Remove all lines (that source the EpicEdit*.cmd files) between and including the comments shown below.
      #XyEnterprise EpicEdit Client Entries.
      <if....source ...cmd...>
      #XyEnterprise EpicEdit Client Entries.

      If you are using the Arbortext tool you cannot have allowTouchup set to no in the .dcf file of any document type that you plan to edit with the Contenta Arbortext tool.

      Because allowTouchup is set to no in the .dcf file for this doctype, this document is "read only". In order to edit documents of this doctype you must edit the .dcf file setting allowTouchup and change it to yes.

    • After upgrading a Contenta Administration Client workstation, upgrade your Contenta database to the current software revision. See the Upgrading the Contenta Database topic.
    • Complete the Contenta Client configuration tasks, then verify the installation using procedures in the Configuring Contenta Client topic.