Select at 'Solutions & Patches' the version r11.2

Now we get a page, which gives an overview on the currently available patches.



In our example we're going to install QO88986.
Click on the name.

Title: NT -EMBEDDED CA WORKFLOW VERSION 1.0.019.040
Description :
PRODUCT: Unicenter Service Desk Rxx              RELEASE: 11.2

APAR #:  QO88986                                 DATE:    8 JUN 2007

PROBLEM DESCRIPTION: NT  -EMBEDDED   CA  WORKFLOW   VERSION  1.0.019.040
                     --------------------------------------------- -------

                     This patch contains CA-Workflow version 1.0.019.040

                     This patch  should only  be applied  to an embedded
                     CA-Workflow  installation,  one  that was installed
                     during Service Desk  installation. It has  not been
                     tested for a standalone CA-Workflow installation.

                     This  patch  requires  running  the  Service   Desk
                     Configuration  Wizard.  The  Configuration  will be
                     started automatically  by the  patch. Make  sure it
                     completes successfully.

                     This patch is for server only, not for CAWF  client
                     installations.

                     As of CA  Workflow 1.0.019.029, adopters  and their
                     customers must use the latest MDB patch appropriate
                     to your database and operating system.

                     This  patch  will  include  the  latest MDB patches
                     below:

                     mssql_mdb030_15705345.zip  (for  Sql  in   Windows)
                     mdb030_15786587.zip   (for   Ingres   in   Windows)
                     ora_mdb030_15705345.zip (for Oracle in Windows)

                     This patch fixes the serialization problem below.

                     PROBLEM:  Viewing  the  status  of  instances  on a
                     process  definition  containing  an  XML   external
                     attribute fails with the following error:

                     org.apache.xerces.dom.AttributeMap;   local   class
                     incompatible: stream  classdesc serialVersionUID  =
                     -788....

                     The  failure   happens  due   to  the   version  of
                     xercesImpl.jar   which   persisted   the   instance
                     attribute DOM objects when the instance was started
                     being  different  from  the  version in the current
                     environment  deserializing  the  DOM  objects.  The
                     xercesImpl.jar  versions   will  be   different  in
                     Workflow environments  that have  moved from  build
                     1.0.019.015  or  earlier  to  build  1.0.019.016 or
                     later due to the  later builds being packaged  with
                     xercesimpl.jar version 2.6.2 and the earlier builds
                     being packaged with version 2.5.x.

                     Workflow upgraded xercesimpl.jar  in order to  move
                     to a more recent release of the component eIAM. The
                     new eIAM recommends the  use of Xerces 2.6.2  which
                     988 KB in  size and includes  a manifest file  that
                     identifies  it  by  version  number.  For   general
                     information   on   finding   third-party  component
                     versions in jar files,  see APAR QI85354. The  eIAM
                     release upgrade  was required  to fix  a number  of
                     problems.

                     Please note: Installations that began using  Tomcat
                     4.1.31 may  not be  subject to  this behavior  even
                     after  an  upgrade.  Installations  that began with
                     Tomcat  4.1.29  are  definitely  subject  to   this
                     compatibility problem between different versions of
                     Xerces.

                     This patch also fixes the following problems:

                     Problem: MEMORY LEAK

                     memory leak  in the  use of  the J2FlowParser. this
                     occurs after a long period of doing stress tests.

                     Problem: COMPLETED WORKITEMS ALWAYS RETRIEVED

                     By default, "Show Completed Tasks" in the  Worklist
                     should be set to false. This will help the Worklist
                     perform   better   as   it   won't  load  completed
                     workitems. This is particularly important given the
                     solution of problem WEK 583.

                     Problem: PROCESS INSTANCES HOLD DUPLICATE XML BLOBS

                     Each running WF process instance saves its state as
                     an  xml  blob  to  a  database table. Currently the
                     instance  blob  includes  a  number  of  extra data
                     elements  that  are  not  strictly  relevant to the
                     instance state, e.g. the WF definition is stored in
                     every process instance  blob. Storing this  bloated
                     blob is  a significant  I/O performance  constraint
                     and creates field size problems for some databases.
                     The large process instance data blobs create  major
                     data storage issues.

                     Note: CA Workflow  now normally snapshots  instance
                     BLOB information  to reduce  memory demands  in the
                     Java Runtime. This behavior is controlled by server
                     configuration  parameter  UseSnapshots,  which   is
                     visible  in  the  IDE.  To  restore  the   previous
                     behavior, reset UseSnapshots to false, which is the
                     default behavior.  This is  related to  the problem
                     WEK 598.

                     With this  patch a  change was  made that  will now
                     throw an ActorFault  exception that can  be handled
                     in the definition if  there is no addressee  e-mail
                     for a  SendEmail event.  Previously the  lack of an
                     addressee  e-mail  was   ignored.  If  the   ignore
                     behavior  on  the  node  throwing  the exception is
                     preferred  then  the  "After  exception processing"
                     action  for  the  ActorFault  exception  has  to be
                     changed   from   "Terminate   process"  to  "Remove
                     workitem  and   continue".  Note   that  only   new
                     instances will  pick up  the changes  to ActorFault
                     exception handling; any existing process  instances
                     will "Terminate process" on exception.

                     Version  2.8.5  on  WINDOWS/NT  (patch  QO87965) or
                     2.7.6 on UNIX (patch QO87965) or later of  ApplyPTF
                     must be applied prior to applying this PTF.
                     The   most   recent   version   can  be  found  at:
                     http://supportconnectw.ca.com/public/ca_common_docs/
                     latest_applyptf.asp

                     PREREQS: None

                     MPREREQS: None

                     COREQS: None

                     MCOREQS: None

                     SUPERSEDED: None

HYPER: NO

DISTRIBUTION CODE: A (A=Available, I=Internal)

PROBLEM RESOLUTION:  Follow the instructions below:

SERVER INSTALLATION:
--------------------

1.  This fix requires Unicenter Service Desk r11.2 to be
    installed.

    This is a Server Component fix that should only be installed
    on the Service Desk primary machine that hosts CA-Workflow.
    It should NOT be installed to a standalone CA-Workflow.

2.  Installation of this patch requires to recycle USRD Server.

3.  You must use the Administrator account.

4.  Place received files for this patch in $NX_ROOT/patches
    directory. If this directory does not exist, please
    create one manually.

5.  IMPORTANT NOTE: If eIAM is configured to use an external
    directory for its user base, you need to make sure that the
    Service Desk Privileged User exists in the external
    directory, otherwise Configuration will fail. Please read
    the following guide for more details:

      Guide: Service Desk Implementation Guide.
      Page: 23  / Chapter 2-9

6.  To apply, run the following command as follows:

      APPLYPTF

7.  Once done with APPLYPTF installation, Shut down Service Desk
    services.

8.  Do the following steps to update the CA-WF Product Key:

   (A) Open the following file in Notepad for reading:
       NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\pm.xml.by_CAWEK40_1
   (B) Find the value of Environment name="ProductKey"
   (C) Open the following file in Notepad for editing:
       NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\pm.xml
   (D) Change the value of Environment name="ProductKey" to
       the same value from step (B)
   (E) Open the following file in Notepad for editing:
       NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\wl.xml
   (F) Change the value of Environment name="ProductKey" to
       the same value from step (B)

9.  Please manually copy the following file

       xercesImpl.jar

   from
   $NX_ROOT\add-ons\caflow\CAFlow\client
   to
   \Program Files\CA\SharedComponents\Tomcat\4.1.31\common\endorsed

   Note:
   please backup the original one before you copy the file above.


10. The following MDB patches will be copied to $NX_ROOT\patches
    directory automatically after applying this patch
    successfully:

      mssql_mdb030_15705345.zip (for Sql in Windows)
      mdb030_15786587.zip       (for Ingres in Windows)
      ora_mdb030_15705345.zip   (for Oracle in Windows)

    Please select the appropriate one for your system, uncompress
    the file, and follow the readme instructions to install the MDB
    patch.

    If the database is on another machine, please copy the
    appropriate MDB compressed patch to a remote machine and run
    the manual steps to install MDB database there.

    NOTE:
    Please backup your database before installing the MDB patch.


11. After installation of the MDB patch, please use the following
    database-specific grant SQL to grant rights to the
    workflow_admin_group for the new tables created for use by the
    BLOB change:


INGRES:

grant select on process_snapshots to group workflow_admin_group\p\g

grant update on process_snapshots to group workflow_admin_group\p\g

grant delete on process_snapshots to group workflow_admin_group\p\g

grant insert on process_snapshots to group workflow_admin_group\p\g

grant copy_into on process_snapshots to group workflow_admin_group\p\g

grant copy_from on process_snapshots to group workflow_admin_group\p\g


Microsoft SQL Server:

GRANT  SELECT, UPDATE, INSERT, DELETE ON [dbo].[process_snapshots]
  TO [workflow_admin_group]


ORACLE:


grant select on mdbadmin.process_snapshots to workflow_admin_group;

grant update on mdbadmin.process_snapshots to workflow_admin_group;

grant delete on mdbadmin.process_snapshots to workflow_admin_group;

grant insert on mdbadmin.process_snapshots to workflow_admin_group;


12. The change in build 019.028 adds a Boolean environment variable
    UpdateProcessInstances that is set to false by default in pm.xml.
    If you see this problem using .028 or later builds, the
    following procedure will repair the serialized data without loss:

  - Shut down CA Workflow by shutting down Tomcat.

  - Modify pm.xml to change the setting to true.
    i.e. pm.xml should have this entry:

      <Environment name="UpdateProcessInstances" override="true"
       type="java.lang.Boolean" value="true"/>

  - Start up the application server. Upon start-up of the Process
    Manager, instances with external XML attributes will be updated.

  - In your pdm_tomcat.log file, you should see some statements
    after the server startup as follows:

      "The Process Manager is processing instance rows that may need
       to be updated. XX instance rows will be processed."

    Somewhere later in the file you should see another message as
    follows which tells us that the update was complete.

      "Update complete. XX rows updated."

    XX would be the number of rows that would be updated.

  - Once you see this message, shut down Tomcat again and set
    UpdateProcessInstances to false.
    Do this so that the update process is executed only once.

    pm.xml should now have this entry:

      <Environment name="UpdateProcessInstances" override="true"
       type="java.lang.Boolean" value="false"/>

  - Restart Tomcat.


13. create a new key in the Server Configuration in the Workflow IDE.
    It will be called "UseSnapshots" and its value should be set to
    true. It will attain the benefits of BLOB optimization.


14. Recycle/Startup Service Desk services.


15. Along with the patch, please make sure to perform the best
    practice and maintenance as described on support connect:

http://supportconnectw.ca.com/public/caworkflow/infodocs/caworkflow_tecdoc.asp


*********************************************************************
*          INSTRUCTIONS FOR UNINSTALLING THIS PATCH                 *
*********************************************************************

1.  Shutdown Service Desk services.

2.  Run the following command and choose option 'Backout PTF on local
    or remote nodes'. Follow instructions and make sure it completes
    successfully before proceeding:

      APPLYPTF

3.  After a successful backout, manually delete the following files:

      NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\pm.xml
      NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\wl.xml

4.  Manually delete the following directories:

      NX_ROOT\site\Workflow\Client
      NX_ROOT\site\Workflow\Server
      NX_ROOT\site\Workflow\uninstall

5.  Run Configuration from Service Desk start menu.
    Make sure it completes successfully before proceeding.

6.  Manually delete the following files again:

      NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\pm.xml
      NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\wl.xml

7.  Manually rename the following files in directory
    NX_ROOT\bopcfg\www\CATALINA_BASE\webapps\

      - rename pm.xml.by_CAWEK40_1 to pm.xml
      - rename wl.xml.by_CAWEK40_1 to wl.xml

8.  Manually restore the original file xercesImpl.jar in the
    \Program Files\CA\SharedComponents\Tomcat\4.1.31\common\endorsed
    directory.

9.  Restore the database which is backup before installing the MDB
    patch.

10. Reset the UpdateProcessInstances to false in pm.xml with the
    following procedure:

  - Shut down CA Workflow by shutting down Tomcat.

  - Modify pm.xml to change the setting to false.
    i.e. pm.xml should have this entry:

   <Environment name="UpdateProcessInstances" override="true"
    type="java.lang.Boolean" value="false"/>

  - Start up the application server. Upon start-up of the Process
    Manager, instances with external XML attributes will be updated.

11. Use the IDE to set UseSnapshots to false to restore the original
    behavior.


12. Recycle/Startup Service Desk services.


PRODUCT(S) AFFECTED: Unicenter Service Desk                 Release 11.2

DOWNLOAD INFORMATION:
---------------------
NODE:  ftp.ca.com
PATH:  /CAproducts/unicenter/USRD/nt/0606/qo88986
FILES: QO88986.D33 QO88986.CAZ

UPDATED ROUTINES:
---------------
configui.jar    371614 THU SEP 28 12:12:46 2006
jaas.config    147 THU AUG 10 15:44:16 2006
password_check.xml    11 MON FEB 13 00:55:02 2006
version.txt    72 FRI MAY 04 22:25:24 2007
DefaultIcons.jar    121951 FRI MAY 04 22:26:34 2007
GenerateMSSQLSchema.bat    3440 FRI MAY 04 22:27:20 2007
ingres.sql    17038 FRI MAY 04 22:27:20 2007
ingres_2.6.sql    17078 FRI MAY 04 22:27:20 2007
ingres_r3.sql    17033 FRI MAY 04 22:27:20 2007
mssql.sql    19046 FRI MAY 04 22:27:20 2007
MSSQLUtil.jar    4771 FRI MAY 04 22:27:20 2007
oracle.sql    12477 FRI MAY 04 22:27:20 2007
processmanager_basic.war    7914796 FRI MAY 04 22:27:20 2007
wl-web_basic.war    9544898 FRI MAY 04 22:27:22 2007
axis.jar    1235721 FRI MAY 04 22:27:20 2007
branding.jar    64299 FRI MAY 04 22:27:20 2007
commons-codec-1.3.jar    46725 FRI MAY 04 22:27:20 2007
commons-discovery.jar    71442 FRI MAY 04 22:27:20 2007
commons-httpclient-3.0.jar    279383 FRI MAY 04 22:27:20 2007
commons-logging.jar    38015 FRI MAY 04 22:27:20 2007
commons-logging-api.jar    26202 FRI MAY 04 22:27:20 2007
concurrent.jar    192579 FRI MAY 04 22:27:20 2007
DefaultIcons_client.jar    48177 FRI MAY 04 22:27:20 2007
dom4j.jar    486522 FRI MAY 04 22:26:36 2007
dom4j-full.jar    513409 FRI MAY 04 22:27:20 2007
ide.bat    663 FRI MAY 04 22:27:20 2007
IDE.jar    2190453 FRI MAY 04 22:27:20 2007
ide.sh    659 FRI MAY 04 22:27:28 2007
IDEHelp.jar    1088864 FRI MAY 04 22:27:20 2007
IDEHelp_de.jar    1033566 FRI MAY 04 22:27:20 2007
IDEHelp_en.jar    1088870 FRI MAY 04 22:27:20 2007
IDEHelp_es.jar    1085543 FRI MAY 04 22:27:20 2007
IDEHelp_fr.jar    1102339 FRI MAY 04 22:27:20 2007
IDEHelp_it.jar    1146071 FRI MAY 04 22:27:20 2007
IDEHelp_ja.jar    1018950 FRI MAY 04 22:27:20 2007
IDEHelp_ko.jar    1067678 FRI MAY 04 22:27:20 2007
IDEHelp_pt_all.jar    1055272 FRI MAY 04 22:27:20 2007
IDEHelp_zh_CN_all.jar    1309587 FRI MAY 04 22:27:20 2007
IDEHelp_zh_TW_all.jar    1009000 FRI MAY 04 22:27:20 2007
jaxrpc.jar    35759 FRI MAY 04 22:27:20 2007
jhall.jar    557529 FRI MAY 04 22:27:20 2007
log4j-1.2.8.jar    352668 FRI MAY 04 22:27:20 2007
saaj.jar    18501 FRI MAY 04 22:27:20 2007
Safe.jar    354782 FRI MAY 04 22:27:20 2007
Worklist.config    128 FRI MAY 04 22:26:34 2007
worklistClient.properties    47 FRI MAY 04 22:26:50 2007
wsdl4j.jar    113853 FRI MAY 04 22:26:50 2007
xalan.jar    2952605 FRI MAY 04 22:26:50 2007
xercesImpl.jar    1010806 FRI MAY 04 22:27:20 2007
xml-apis.jar    124724 FRI MAY 04 22:27:20 2007
xmlParserAPIs.jar    124724 FRI MAY 04 22:26:50 2007
processmanager_eiam.war    8447583 FRI MAY 04 22:27:26 2007
wl-web_eiam.war    10077587 FRI MAY 04 22:27:26 2007
processmanager_ldap.war    7914834 FRI MAY 04 22:27:22 2007
wl-web_ldap.war    9544932 FRI MAY 04 22:27:22 2007
processmanager_portal.war    7914876 FRI MAY 04 22:27:24 2007
wl-web_portal.war    9544977 FRI MAY 04 22:27:22 2007
default.rsp    5325 FRI MAY 04 22:26:36 2007
eIAM_scoping.xml    2760 FRI MAY 04 22:26:36 2007
sample.rsp    4360 FRI MAY 04 22:26:48 2007
setup.jar    19663163 FRI MAY 04 22:26:26 2007
epdc.jar    1821 FRI MAY 04 22:26:36 2007
tools.jar    5082050 FRI MAY 04 22:26:48 2007
pm.xml    3582 FRI MAY 04 22:27:20 2007
wl.xml    2998 FRI MAY 04 22:27:20 2007
mdb030_15786587.zip    205711 THU APR 05 13:30:49 2007
mssql_mdb030_15705345.zip    255184 THU APR 05 13:30:20 2007
ora_mdb030_15705345.zip    95214 THU APR 05 13:30:32 2007

cazipxp -u QO88986.CAZ

applyptf

Locate the 'Apply PTF (Filename). Press 'Next'

After a certain time it will launch PDM_Configure. You'll walk through this screens like you've done before
Press 'Next'

Provide the required passwords and press 'Next'

Press 'Next'

Press 'Next'

Press 'Next'

Press 'Next'

Press 'Yes'

Press 'Finish'

Press 'OK'

Since we don't have additional patches to install, press 'Finish'

Press 'OK'



Shutdown the Service Desk services, with the following command in a DOS box

net stop "Unicenter Service Desk Server"

C:\>net stop "Unicenter Service Desk Server"
The Unicenter Service Desk Server service is stopping...............
The Unicenter Service Desk Server service was stopped successfully.