IBM Support

PM63619: Exception with automation actors when publishing workflow

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issue 1: When publishing a workflow from RSA to RBF, only the
    project level selector is being set to the value of the overall
    workflow automation actor, the selectors for each individual
    step within the project are being left as 'default', despite the
    tasks in the workflow having a specific automation actor set.
    The workflow will only publish if all steps have their
    automation actor set to either default or the same actor as the
    overall workflow automation actor.
    Issue 2:  When publishing a workflow with multiple tasks where
    each task requires a separate automation actor, RSA is returning
    the following error, and not publishing anything to RBF.
    Exception Stack Trace:
            com.buildforge.services.common.api.APIException
            at
    com.buildforge.services.client.api.APIClientConnection.call(Unkn
    own
    Source)
            at
    com.buildforge.services.client.dbo.Selector.create(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.fin
    dOrCreateSelectorForHostname(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.fin
    dOrCreateDummySelector(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.cre
    ateOrUpdateSelectorForMultiNodeProject(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.cre
    ateMasterProject(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.pub
    lishMultiSelectorWithProgress(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.pub
    lishWithProgress(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.util.BuildForgeHelper.pub
    lishWithProgress(Unknown
    Source)
            at
    com.ibm.ccl.soa.deploy.exec.buildforge.ui.internal.publisher.Bui
    ldForgeWFPublishJob.run(Unknown
    Source)
            at org.eclipse.core.internal.jobs.Worker.run(Unknown
    Source)
    Session Data:
            eclipse.buildId=unknown
            java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows Server
    2003 x86-32 jvmwi3260sr9-20110726_87724 (JIT enabled, AOT
    enabled)
            J9VM - 20110726_087724
            JIT  - r9_20101028_17488ifx17
            GC   - 20101027_AA
            BootLoader constants: OS=win32, ARCH=x86, WS=win32,
    NL=en_AU
            Framework arguments:  -product
    com.ibm.rational.rsa4ws.product.v80.ide
            Command-line arguments:  -os win32 -ws win32 -arch x86
    -product com.ibm.rational.rsa4ws.product.v80.ide
    
    Impact of Issues: The RSA workflow can be published using a
    project level automation actor, and project steps will still run
    under this actor, so all steps are executed on the same server.
    This isn't an issue if that's all the job requires.  However, if
    they are meant to run on separate servers, then either the
    workflow fails to publish with the exception above, or the RBF
    project steps needs to be manually updated each time the
    workflow is published if you use the workaround of setting all
    the actors to the same value prior to publishing.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Cannot properly use multiple automation actors with
    workflows.
    

Problem conclusion

  • Fix workflow and buildforge publishing so multiple
    automation actors/selectors can be used properly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63619

  • Reported component name

    SW ARCHITECT WI

  • Reported component ID

    5724I7001

  • Reported release

    803

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-30

  • Closed date

    2012-12-04

  • Last modified date

    2012-12-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SW ARCHITECT WI

  • Fixed component ID

    5724I7001

Applicable component levels

  • R803 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYKBQ","label":"Rational Software Architect Designer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"803","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JCV","label":"Rational Software Architect for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"803","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
04 December 2012