If you do not have an Installation CD you may download the latest version from the Cobwebb website. Note: The same installation CD is used for both installing the Cobwebb Document Management Server software for the first time and for upgrading an existing version. The downloaded file will be called CPPDnnnn.iso.zip file where nnnn is the version number. The .zip file contains the file CPPDnnnn.iso which may either be burnt as an image to a CD and then installed on the Server or installed directly from the IFS using a Virtual Optical device.

For the cumulative Release Notes please download the What's New in Cobwebb Document Management pdf from the Cobwebb website.

Pre-Requisites

•Minimum IBM i Version: V6R1M0 (Please see CPPD & IBM i Compatibility for further details.)

•Available Disk Space: 1GB HDD

•Server Authority:

oServer sign on as QSECOFR or with a User Profile that has the following authorities:

▪*ALLOBJ  

▪*SECADM

▪*JOBCTL  

▪*SPLCTL

▪*IOSYSCFG - required if you are going to be installing Cobwebb Document Management from a Virtual Optical Device.

oThis User Profile must also be enrolled in the System Directory as the Cobwebb Server installation restores a folder to QDLS. For details on how to enroll a user in the System Directory please see Installing / Upgrading the Cobwebb Server Software below.

Steps to perform BEFORE Upgrading the Cobwebb Server Software

If you are upgrading your version of Cobwebb Document Management then you will need to perform the following tasks BEFORE following the instructions for Installing / Upgrading the Cobwebb Server Software.
The upgrade works by renaming the existing CPPD library to CPPDOLD. The new CPPD library is restored and all of the data from CPPDOLD is copied to the new CPPD library. All of your existing configurations will also be carried through to the new CPPD library.

1.If you are a Cobwebb Email or Cobwebb Fax customer, make sure that you have run the Cobwebb Housekeeping to reduce the size of the Cobwebb Queue.

2.Agree time with end users of Cobwebb PPD and the Cobwebb Web Server (CHTTPD) for the upgrade as they will not be able to use these during the upgrade process. The Cobwebb Web Server may include Docstore / Portal external usage, Imports to Docstore e.g. Tungsten Capture and Folder Monitoring, Mobile POD, or whatever else uses the CHTTPD job.

3.Check the Available Disk Space on the Server is greater than that of the size of your current CPPD library.
 
WRKSYSSTS - (Will show you the Available Disk Space)
 
DSPLIB LIB(CPPD) OUTPUT(*PRINT) - (Will show you the Total size of library CPPD at the bottom of the print)

4.Check for a CPPDOLD library (this will only exist if you have run a previous upgrade of CPPD as it copies the current CPPD to CPPDOLD in case a rollback is required.) If a CPPDOLD library exists then either RENAME this or DELETE it.
 
DSPLIB CPPDOLD - (Will show you the contents of library CPPDOLD if it exists)
 
Note: If an upgrade has just failed, the CPPDOLD library may contain the only 'live' good version of CPPD so Renaming would be better than Deleting in this case. Also if you are going to Delete the library you will need to first clear the QPRINT Output Queue in the CPPDOLD library otherwise the library will not be deleted use CLROUTQ OUTQ(CPPDOLD/QPRINT)

5.End the CPPD subsystem.
 
ENDSBS CPPD

6.End any other systems that might automatically lock any of the Cobwebb libraries or DLOs, such as MIMIX.

7.Check that there is nothing/no one using the CPPD library
 
WRKOBJLCK OBJ(CPPD) OBJTYPE(*LIB)
 
You should see the following message:
(There are no locks for the specified object)

8.If there are locks displayed then end the relevant jobs and keep running Step 7 until there are no locks existing on the CPPD library.

9.Install the Cobwebb Server Software - see below Installing / Upgrading the Cobwebb Server Software for details.

Notes: As a general rule the library CPPD should NOT hold any Bespoke objects for a customer.

•Bespoke Exit Programs will normally reside in a library called COBEXIT, if they have been put in library CPPD the upgrade will try to move them (from CPPDOLD to the new CPPD) but this cannot be guaranteed.

•Any none system Job Descriptions in library CPPD will be copied across along with existing CPPD Job Descriptions in case you have changed library lists etc.

•If you have any bespoke Output Queues or Data Queues that are configured in the Work with Spooled File Monitor, and exist in library CPPD, the upgrade process will give you the chance to move these to somewhere more suitable e.g. QUSRSYS. This means that no data waiting to be processed by Cobwebb PPD will be lost in the upgrade process.

Installing / Upgrading the Cobwebb Server Software

1.Sign on as QSECOFR or with a User Profile that meets the Prerequisites outlined above.

This User Profile must also be enrolled in the System Directory as the Cobwebb Server installation restores a folder to QDLS. To add a Directory Entry you can use the following command replacing the words in red with your own entries:

ADDDIRE USRID('User ID' 'Address') USRD('User Description') USER(User_Profile) SYSNAME(*LCL)

User ID - is usually the same as the User i.e. the User Profile

Address - is usually either the System Name or the same as the User Id

User_Profile - must match the User Profile that you are going to use for the installation.

2.Install Cobwebb Server software:

•Installing the Cobwebb Server software from a CD#1

oPlace the Installation CD in the IBM i Optical Disc drive and type

LODRUN DEV(*OPT)

Please refer to the topic on the System Installation Wizard for details.

•Installing the Cobwebb Server software from a Virtual Optical Device

Note: From version 6.2.60 the joblog from the Cobwebb Server software installation will be automatically written to the AINSLOG file in library CPPD creating a new member each time.

What is installed?