CA SOA Integration Bridge R121 ReadMe - CA Technologies
{{search ? 'Close':'Search'}}

SOA Integration Bridge r12.1 Readme

1.0 Welcome

2.0 Operating System Support
2.1 Windows

3.0 System Requirements
3.1 All Operating Systems
3.2 Windows

4.0 Installation Considerations
4.1 CA Endevor Integration with CA Service Desk Manager
4.2 CA SCM Integration with CA Service Desk Manager
4.3 CA SCM Integration with HP Quality Center

5.0 General Considerations
5.1 Before Using SOA Integration Bridge
5.2 All Users
5.3 CA SCM Integration with HP Quality Center
5.4 CA SCM Publisher

6.0 Known Issues
6.1 All Integrations
6.2 CA Endevor Integration with CA Service Desk Manager
6.3 CA SCM Integration with CA Service Desk Manager
6.4 CA SCM Integration with HP Quality Center

7.0 Published Fixes

8.0 Downloads

9.0 Documentation
9.1 Release Numbers on Documentation

10.0 Contact CA Support

1.0 Welcome

Welcome to SOA Integration Bridge r12.1. This file contains product installation considerations, operating system support, known issues, and information about contacting CA Support.

For additional information about SOA Integration Bridge:
CA Extends CA Change and Configuration Management.

Note: For product integration-specific installation considerations, operating system support, and known issues, see your product documentation.

2.0 Operating System Support

This section lists the operating systems supported by SOA Integration Bridge r12.1. CA supports these operating system for the duration of their life cycle (as determined by the operating system's manufacturer or until CA announces that we are dropping support). Visit the Technical Support website at http://www.ca.com/support for the latest information about supported operating systems.

2.1 Windows

SOA Integration Bridge on Windows requires the following operating system:

  • Microsoft Windows Server 2003 Standard or Enterprise

    3.0 System Requirements

    This section lists the hardware and software requirements for SOA Integration Bridge to install and run correctly.

    3.1 All Operating Systems

    The following software requirements must be met on all supported operating systems for SOA Integration Bridge to install and run correctly. Before you use the product, ensure that all required products for your selected integration are installed and running. For more information, see General Considerations.

    3.2 Windows

    The following hardware requirements must be met on Microsoft Windows for the product to install and run correctly.

    You must also meet the minimum hardware requirements for the products that comprise each integration you will be using. For example, if you will be using the CA Endevor Integration with CA Service Desk Manager, ensure your computer also meets the minimum hardware requirements for CA Endevor and CA Service Desk Manager.

    4.0 Installation Considerations

    Before installing SOA Integration Bridge (or any of its components), be sure to review the following sections carefully to determine if there are additional installation or configuration steps you need to follow for this release.

    Note: For more information about installing and configuring SOA Integration Bridge, see the SOA Integration Bridge Solution Guide on the installation media.

    4.1 CA Endevor Integration with CA Service Desk Manager

    Consider the following information when installing the CA Endevor Integration with CA Service Desk Manager

    Note: For more information about installing and configuring SOA Integration Bridge, see the SOA Integration Bridge Solution Guide on the installation media.

    4.2 CA SCM Integration with CA Service Desk Manager

    Consider the following information when installing the CA SCM Integration with CA Service Desk Manager.
    • CA Software Change Manager r12.1, r12.1 SP1.

      For more information about the CA SCM requirements, see the CA SCM r12.1 documentation, including the CA SCM r12.1 or r12.1 SP1 Release Notes. For more information about how to install CA SCM r12.1, see the CA SCM r12.1 Installation Guide. Updated guides for this product are available on the Technical Support website at http://ca.com/support.

    • CA SCM Web Services component

      You must install the CA SCM Web Services component of the product on a computer that already has the following application server installed:

    • JBoss Application Server 4.2.3 and later with JMS support installed.

      JBoss Application Server is J2EE-certified and is available for free. For more information, see the JBoss website, http://jboss.org.

      Note: This server is required for configuring the message queue and topic components of the product.

    • CA Endevor r7.0 SP3 (if you are using a CA Endevor integration)

      For more information about the CA Endevor requirements, see the CA Endevor documentation. Updated guides for this product are available on the Technical Support website at http://ca.com/support.

    • CA CM Enterprise Workbench r7.1 Patch 1 (if you are using a CA Endevor integration)

      For more information about the CA CM Enterprise Workbench requirements, see the CA Endevor documentation. Updated guides for this product are available on the Technical Support website at http://www.ca.com/support.

      Note: There is an additional Hot Fix (CA CHANGE MANAGER ENTERPRISE WORKBENCH R7.1 P0001 EFIX 161) that you must apply on top of CA CM Enterprise Workbench r7.1 Patch 1. More information about the Hot Fix, and instructions to download the Hot Fix are available on Support Online.

    • Quality Center 8.2 SP1 or 9.0 or 9.2 or 10.0 (if you are using a Quality Center integration)

      For more information about the Quality Center requirements, see the Quality Center documentation.

    • CA Service Desk Manager r12.5 (if you are using a CA Service Desk Manager integration)

      For more information about the CA Service Desk Manager requirements, see the CA Service Desk Manager documentation. Updated guides for this product are available on the CA Support website at http://ca.com/support.

    • Java Runtime Environment (JRE) 1.5 update 10 or later. JRE 1.5 is also referred to as JRE 5.0.
    • Pentium P4 1.4 GHz processor
    • 2 GB of RAM
    • 40 MB of free disk space
    • Ensure that the product is configured, or can be configured to use a local or remote service. A local service is typically provided by a J2EE application server. Use the following information for reference.

    • If you install SOA Integration Bridge and SCM Web Services on the same computer, you must select the SCM Web Services component and the local application server during installation.

    • If you install SOA Integration Bridge without SCM Web Services, you must specify a remote service. You are prompted to enter the host name and port number of the remote server to which the local computer connects.

    • If you have a GA version of the product installed on your computer, use these steps before you install the SCM r12.1/SDM r12.5/QC 10 Compatible version of the product to successfully remove the GA version:

    • Uninstall the GA version of the product (SOA Integration Bridge) using the Control Panel (Add/Remove Programs).

    • If you are prompted, reboot your computer.

    • Navigate to the C:Program FilesCommon FilesInstallShieldUniversalcommon directory.

      Note: On some computers, the Program Files directory is not located on your C: drive. We recommend that you check all drives.

    • Delete any directory named "Gen1".

      The GA version of the product is successfully removed, and you can now install the SCM r12.1 Compatible version of the product.

    • If you have a pre-GA version of the product installed on your computer, use these steps before you install the GA version of the product to successfully remove the pre-GA version:

    • Uninstall the pre-GA version of the product (ECM Integration Bridge) using the Control Panel (Add/Remove Programs).

    • If you are prompted, reboot your computer.

    • Navigate to the C:Program FilesCommon FilesInstallShieldUniversalcommon directory.

      Note: On some computers, the Program Files directory is not located on your C: drive. We recommend that you check all drives.

    • Delete any directory named "Gen1".

      The pre-GA version of the product is successfully removed, and you can now install the GA version of the product.
    • You must install the CA Endevor Web Services component of the product on the same service that has CA Change Manager Enterprise Workbench (CA CM Enterprise Workbench) installed and on a computer that already has the following application server installed:

    • JBoss Application Server 4.0.3 SP1 and later with JMS support installed.

      JBoss Application Server is J2EE-certified and is available for free. For more information, see the JBoss website, http://jboss.org.

      Note: This server is required for configuring the Message Queue component of the product.

    • The ew.cfg file (for CA Endevor Web Services) and JMS.cfg file must contain Java messaging service information.

    • You must install the CA Service Desk Manager Agent component on the CA Service Desk Manager primary server installation. If you install the agent component on the CA Service Desk Manager secondary server installation, the integration will not work.
    • If you have a GA version of the product installed on your computer, use these steps before you install the SCM r12/SDM r12/QC 10 Compatible version of the product to successfully remove the GA version:

      1. Uninstall the GA version of the product (SOA Integration Bridge) using the Control Panel (Add/Remove Programs).

      2. If you are prompted, reboot your computer.

      3. Navigate to the C:Program FilesCommon FilesInstallShieldUniversalcommon directory.

        Note: On some computers, the Program Files directory is not located on your C: drive. We recommend that you check all drives.
      4. Delete any directory named "Gen1".

        The GA version of the product is successfully removed, and you can now install the SCM r12 Compatible version of the product.
      5. If you have a pre-GA version of the product installed on your computer, use these steps before you install the GA version of the product to successfully remove the pre-GA version:

      6. Uninstall the pre-GA version of the product (ECM Integration Bridge) using the Control Panel (Add/Remove Programs).

      7. If you are prompted, reboot your computer.

      8. Navigate to the C:Program FilesCommon FilesInstallShieldUniversalcommon directory.

        Note: On some computers, the Program Files directory is not located on your C: drive. We recommend that you check all drives.
      9. Delete any directory named "Gen1".

        The pre-GA version of the product is successfully removed, and you can now install the GA version of the product.
      10. You must install the CA SCM Web Services component of the product on a computer that already has the following application server installed:

      11. JBoss Application Server 4.2.3 and later with JMS support installed.

        JBoss Application Server is J2EE-certified and is available for free. For more information, see the JBoss website, http://jboss.org.

        Note: This server is required for configuring the Message Queue component of the product.

      12. The computer on which you install CA SCM Web Services must have the CA SCM client installed, to enable communication between CA SCM Web Services and the CA SCM server.

      13. You must install the CA Service Desk Manager agent component on the CA Service Desk Manager primary server installation. If you install the agent component on the CA Unicenter Service Desk secondary server installation, the integration will not work.

        4.3 CA SCM Integration with HP Quality Center

        Consider the following information when installing the CA SCM Integration with HP Quality Center.

          6.0 Known Issues

          This section describes known issues, workarounds, and solutions for this release of SOA Integration Bridge.

          6.1 All Integrations

          6.2 CA Endevor Integration with CA Service Desk Manager

          Single Quotes in Change Order Request

          Single quotes in the change order sequence number prefix or suffix causes an error when polling for updates.

          Special Characters in Change Order Request

          Special characters such as an apostrophe and the percent sign in the prefix or suffix value of a change order causes an error during package creation.

          Change Order Category or Project Value Modification

          The integration will not work if you change either the Change Order category or project value to a value not supported by the integration.

          Deleting a CA Endevor Package

          When you delete a package in CA Endevor, a notification will not be sent to the appropriate CA Service Desk Manager change order.

          Change Order Summary Truncated

          Due to a character field limitation in CA Endevor for a package description, if you enter a change order summary that exceeds 50 characters, the summary will be truncated after the package is created and the data synchronized.

          CA Endevor Package Name

          Due to a character field limitation in CA Endevor for a package name, if the package name that you want (Format String + CA Service Desk Manager Change order name) exceeds 16 characters, the package name will be truncated to the first 16 characters. In addition, all characters will appear in upper case and unsupported CA Endevor characters will be translated to #.

          CA Endevor Package Notifications

          The CA Endevor package data will be synchronized with the Change Order summary, only when the Enterprise Package associated with the CA Endevor package is executed, cancelled, backed in, or backed out.

          No Message or Package Created

          If you try to create a change order using a Change Order category for which an integration does not exist, you will not receive a message within SOA Integration Bridge that the package could not be created. In addition, if you try to create a change order with a project that is not part of an integration, you will receive a message in the activity log about the integration process being invoked. However, a package will not be created.

          Duplicate Package Names

          If an Enterprise or CA Endevor package already exists with the name that is generated by an integration, that integration will not create or link these packages back to CA Service Desk Manager. However, a message will be recorded in the activity log.

          Time Zone

          If you have a CA CM Enterprise Workbench server using Ingres as the database, and the time zone for the server is set to daylight savings time, the transaction time that you see when you create and initiate a change order in CA Service Desk Manager will not match the transaction time that you see for the CA Endevor and enterprise package in CA CM Enterprise Workbench (the Execution Window).

          As a workaround, edit your Endevor.cfg files for the selected hosts to amend the time zone offset by one hour while daylight savings time is not in affect. For more information, see your CA CM Enterprise Workbench administrator.

          Special Characters in Change Order Summary and Description

          Due to a known limitation in CA Endevor, the CA Endevor package description cannot contain both quotes ( " ) and apostrophes ( ' ). When you try to create or update an integration in which both of these characters appear in the Change Order Summary, you will receive an error during package creation.

          CA Endevor Package and CA CMEW Enterprise Package Association

          If the association between CA Endevor Package and CA CMEW Enterprise Package is in the OFF status then events related to Endevor Package will not be reflected in Service Desk's Change Order Activity log.

          6.3 CA SCM Integration with CA Service Desk Manager

          Single Quotes in Change Order Request

          Single quotes in the change order sequence number prefix or suffix causes an error when polling for updates.

          Change Order Category or Project Value Modification

          The integration will not work if you change either the Change Order category or project value to a value not supported by the integration.

          No Message or Package Created

          If you try to create a change order using a Change Order category for which an integration does not exist, you will not receive a message within SOA Integration Bridge that the package could not be created. Additionally, if you try to create a change order with a project that is not part of an integration, you will receive a message in the activity log about the integration process being invoked. However, a package will not be created.

          Database Error

          If you create a change order with a description having a large number of characters (for example 4000), you may receive a database error in the Configurator. This can happen when the field length in the CA SCM form cannot accept all of the characters. As a workaround, increase the form field length in the database.

          CA SCM Web Service Broker Limitation

          A single CA SCM web service cannot connect to more than one CA SCM broker. As a result, updates to data in CA Service Desk Manager may be lost. As a workaround, install one CA SCM web service for each broker.

          6.4 CA SCM Integration with Quality Center

          Operation Error Message

          While working with a CA SCM Integration with Quality Center, you may receive an error message similar to the following:

          Operation 4 not allowed

          After you receive the message, CA SCM packages and their associated Quality Center defects may become unsynchronized. For example, updates that you make to a CA SCM form may no longer be made automatically to its associated Quality Center defect. Similarly, updates that you make to a Quality Center defect may no longer be made automatically to its associated CA SCM form.

          To re-synchronize the forms and defects (JBoss)

          Synchronization with SOA Integration Bridge

          After entering a defect in Quality Center, if you then change the setting of the Sync With SOAIB field to N, any updates made in CA SCM will not be made in Quality Center. If you then change the Sync With SOAIB field back to Y, the latest updates from Quality Center will be made in CA SCM. As a result, you may lose some data in CA SCM.

          CA SCM Broker Terminates

          If the CA SCM broker process terminates or shuts down, you must restart SOA Integration Bridge, CA SCM web services and CA SCM Publisher.

          Quality Center Attachment Support

          There is a known issue with the Quality Center API with downloading signature files, which impacts the Attachment support. As a result, attachment synchronization cannot be performed. In this release, do not map attachment related fields.

          Custom Fields of Type Date

          Custom fields of type date are not supported.

          Quality Center User

          After you create an integration and specify the Quality Center user name, you cannot change the user. If the user is not correct and needs to be changed, you must delete the integration and add it again with the correct user. In addition, when you create integrations that have the same domain and project, you must specify the same user name for all the integrations. If you do not, the integrations will not work correctly.

          Time Zone

          There is a known issue with the Quality Center server not providing time zone data correctly when mapping date fields. As a result, the synchronization agent will automatically make all Quality Center date fields read-only, even when you have not specified this in Quality Center. This means that even when a date field in Quality Center is writable, and an update comes from an integrated product, the synchronization agent will not update the date in Quality Center. As a result, when a date field is updated in Quality Center, the target tool may be updated with the incorrect date because the Quality Center server does not provide the correct time zone data.

          Field Mapping of Different Lengths

          When mapping fields between products that have different lengths (column lengths in the database), the data may be truncated to meet the product requirements.

          CA SCM Web Service Broker Limitation

          A single CA SCM Web Service cannot connect to more than one CA SCM broker. As a result, updates to data in Quality Center may be lost. As a workaround, install one CA SCM Web Service for each broker.

          Use of "&" Symbol in Memo Fields

          There is a known limitation in Quality Center 8.2 SP1 when retrieving the ampersand symbol "&" from a memo field in a defect such as the Description and Comments field. When retrieving the "&" symbol, the ampersand symbol appears, followed by "amp;" instead of "&".

          SOA Integration Bridge Hangs for CA SCM UDP Process

          When you create an integration between Quality Center and CA SCM in which a non-terminating post linked UDP process has been defined for the Create Package process, and you have logged into Quality Center to create a defect, and then try to modify another integration that is already running, SOA Integration Bridge will hang until you stop the UDP process in CA SCM. As a workaround, you can use CA SCM to create a UDP process in asynchronous mode using the hexecp command line utility. To run the hexecp command, the computer should have the CA SCM agent installed.

          The hexecp command executes the program specified by the -prg argument, on the computer specified by the -m argument, with options specified by the -args argument. The output is directed to standard output unless a file is named using the -o option.

          Note: -usr and -pw are not your CA SCM username and password. They are the username and password for the computer on which the program will be executed.

          hexecp attempts to log in to an agent. If the utility does not find an agent on the computer you have designated after the -m option, you will receive a message stating, "An agent for machinename cannot be found." Before executing hexecp, ensure that an agent is running on the target computer.

          The following is the syntax for the hexecp command:

          hexecp %7B-b name -prg program -m machinename%7D %7B-syn | -asyn%7D %7B-usr username -pw password%7D [-args arguments...] [-v] [-prompt]
          [-i inputfile.txt | -di inputfile.txt] [-er filename] [-o filename | -oa filename] [-arg] [-wts] [-h]

          -b name
          (Required.) Specifies the CA SCM broker name.

          -prg program
          (Required.) Specifies the full path and program you want to execute on the destination computer (-m).

          -m machinename
          (Required.) Specifies the name of the destination computer on which you want to execute the program.

          -syn
          (Required: -syn and -asyn are mutually exclusive and one is required.) Specifies synchronous mode.

          -asyn
          (Required: -syn and -asyn are mutually exclusive and one is required.) Specifies asynchronous mode.

          -usr username
          (Required, unless -prompt is specified.) Specifies the user name for login to the broker. If -usr is defined without -pw, the user is prompted for the password at runtime.

          -pw password
          (Required, unless -prompt is specified.) Specifies the password for login to the broker. To hide the password from being exposed in plain text on the command line, use the -prompt option.

          The following sample illustrates the syntax for the hexecp command:

          hexecp -asyn -prg "c:windowssystem32notepad.exe" -b harvest-cm-qa1 -m hqatest5-2003 -usr administrator -pw abcd

          To have this command execute, the computer should have the CA SCM agent installed, because the hexecp command interacts with the program execution by logging into the CA SCM agent. By providing -asyn in the hexecp options, you can execute a upd process asynchronously.

          Note: For more information, see the CA SCM Command Line Reference Guide.

          7.0 Published Fixes

          The complete list of published bug fixes for this product can be found through Published Solutions on Support Online.

          8.0 Downloads

          SOA Integration Bridge builds are available for download at:

          CA SOAIB r12.1 - SDM r12.5, SCM r12.1/12.1 SP1 and QC 10.x Compatible Build (This is the superset of previous build and it supports SCM r12.1 and SCM r12.1 SP1(new!), CA Service Desk r12.5 (new!), QC 9.0, 9.2 and 10.0, Endevor r7 SP4)

          CA SOAIB r12.1 - SDM r12.6, SCM r12.1 SP3 and QC 10.x Compatible Binaries (These binaries should be used on top of latest SOAIB 12.1 build to configure SOAIB with SDM r12.6 and SCM r12.1 SP3)

          CA SOAIB r12.1 - SDM r12.6, SCM r12.5 Compatible Binaries (These binaries should be used on top of latest SOAIB 12.1 build to configure SOAIB with SDM r12.6 and SCM r12.5)

          Following are the individual binaries of SOAIB available for download:

          9.0 Documentation

          CA SOA Integration Bridge Solution Guide
          CA SOA Integration Bridge Technical Document Index - FAQs
          CA SOAIB - QC 9.2/QC10.0 Customization Document
          CA SOAIB - Plug-in Development Guide

          Updated guides for this product are available at http://ca.com/support.

          The PDF guide for this product is titled SOA Integration Bridge Solution Guide (SOAIntegrationBridge_SolutionGuide_ENU.pdf).

          To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

          9.1 Release Numbers on Documentation

          The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, will support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r11 may still be valid for r11.1 or even r12. Documentation bookshelves always reflect the current product release number.

          Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.

          10.0 Contact CA Support

          For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact CA Support at http://www.ca.com/support.

        • You must install the CA SCM Web Services component of the product on a computer that already has the following application server installed:

          The computer on which you install CA SCM Web Services must have the CA SCM client installed, to enable communication between CA SCM Web Services and the CA SCM server.

          5.0 General Considerations

          5.1 Before Using SOA Integration Bridge

          This section contains general information you should know before using the product:

          5.2 All Users

          Before using the product, ensure that the following are installed and running in your environment:

          Important! Before using the product, access the Quality Center URL from the Quality Center synchronization agent computer (using Microsoft Internet Explorer) to download the DLL files required for communication between the agent and the Quality Center server. For more information, see your Quality Center documentation.

          Note: If you plan to use Quality Center 9.2/10.0 then you should refer to separate document for Quality Center customization. CA SOAIB - QC 9.2 Customization Document.

          5.3 CA SCM Integration with HP Quality Center

          Before using SOA Integration Bridge, consider the following information:

          5.4 Using the CA SCM Publisher component

          SCM Event Publisher lets you publish CA SCM events. You must start the publisher to publish the CA SCM events.

          Note: The SCM Event Publisher is common for all integrations associated with CA SCM. You must start the Publisher before starting the integration.

          To start SCM Event Publisher

        • JBoss Application Server 4.2.3 and later with JMS support installed.

          JBoss Application Server is J2EE-certified and is available for free. For more information, see the JBoss website, http://jboss.org.

          Note: This server is required for configuring the Message Queue component of the product.
        • SOA Integration Bridge, including the components required to integrate CA products with other products.

          For example, to use the product to integrate CA SCM with HP Quality Center, you must install the CA SCM Integration with HP Quality Center, Quality Center synchronization agent, the base product components, and the CA SCM Web Services.

          In this specific release, publishing the events from CA SCM has been separated from the CA SCM Web Services. There is a separate component called SCMPublisher which is used for publishing the events from SCM.This component needs to be started on the same machine as CA SCM Web Services.For detail steps to start the publisher component refer Section 5.4.

          If you are using CA SCM r12.1, we need to start jboss with SCM Web Services by setting the path as follows:

          Navigate to the bin folder of the jboss through commandline and execute

          set path=<path till SCM Publisher folder>;%path%

          Note: Refer Section 5.4 for SCM Publisher folder path.

        • Any third-party products for which you want to create an integration, such as HP Quality Center 10.0. For more information about how to install and configure Quality Center, see your Quality Center documentation.
        • A Java Virtual Machine (JVM) with server support. If you do not have a JVM installed with server support and you try to start the Configurator, you may receive an error similar to the following: ver' JVM at %JRE_HOME%binserverjvm.dll

          Either install a JVM with server support, or edit the SOAIB.ini file (located in the SOAIB home directory) and remove the -server option.
        • The computer on which you install the Quality Center synchronization agent (with or without other product components) requires Microsoft Extensible Markup Language (MSXML) Version 6.

        • The CA SCM plug-in does not allow the use of the dollar sign ($) as the suffix for setting the form name.

        • When setting the CA SCM context and specifying Quality Center format strings, do not use more than 127 characters when specifying the CA SCM package name format string and form name format string.

        • CA SCM packages created by SOA Integration Bridge cannot have more than one instance of the SOA Integration Bridge form type. If there is more than one instance, package rename may not work correctly.

        • If two users simultaneously change any field for either the source or target product, the last changes submitted will overwrite the previous changes.
        • Download the SCMPublisher.zip from the Support Online.

        • Unzip the SCMPublisher.zip to any local directory of the SCM WebService deployed machine.

        • Navigate to SCMPublisher/properties folder and edit the config.properties file with following changes:

        • Search for java.naming.provider.url=jnp://<scm webservice machine>:<jms port>

        • Replace <scm webservice machine> with the machine name where you have deployed SCM WebService.

        • Replace <jms port> with the jms port of the jboss where you have configured SCM Topics.

        • Copy jbossall-client.jar file to SCMPublisher/publisher_lib directory.

          Note: jbossall-client.jar is available in the JBOSS_HOMEclient directory.

        • Navigate to SCMPublisher folder from command prompt.

        • Execute the following command, only if you have CA SCM r12.1:

          set path=<path till SCM Publisher folder>;%path%

        • Use the following command to create an encrypted form of CA SCM credentials:

          svrenc -usr <username> -pw <password> -dir <scmpublisher folder path> -f <encrypted file name>

        • Run the following command to start the CA SCM publisher:

          Option-1: java -jar publisher.jar -b <brokername> -f <encrypted file name>
          Option-2: java -jar publisher.jar

          The above command will prompt for broker, username, and password. All the CA SCM events generated from this point, will be posted to configured CA SCM topic.
        • After you install the product, you cannot modify your installation. This means, for example, that if you selected the "typical" installation type and did not install all of the components you needed for your distributed environment, you cannot go back and install the remaining components or uninstall individual components. You must uninstall all components first, and then re-install all of the components that you need.

        • In an integration, if updates in both products happen at the same time, updates in one product may be lost.

        • If you have multiple integrations, and a particular integration cannot be automatically started when the Startup Type is set to Automatic, you must manually start the integration.
        • Restart SOA Integration Bridge by performing the following tasks:
        • Exit the open instance of SOA Integration Bridge.
        • Access the product installation folder (for example, c:program_filesCASOAIntegrationBridge).
        • Run the SOAIB.exe file.
        • Restart the SCM Web Services by performing the following tasks:
        • Navigate to the JBoss Application Server home directory.
        • In that directory, access the bin directory.
        • Run the shutdown.bat file.
        • Run the run.bat file.
        • Verify that any changes made to defects and packages since the error message was issued are properly synchronized.
        • Verify that any new changes you make to a package or defect are synchronized automatically.
        • SOAIB r12.1.iso (This ISO is same as previous builds and will have main product installer for all four plug-ins, SCM Web Service, HP QC Sync Agent, Endevor/CMEW Web Services etc.)
        • SOAIntegrationBridge_SolutionGuide_ENU.pdf (This is an updated Solution guide for SOAIB.)
        • SCMPublisher.zip (This is a new stand-alone component to publish the SCM events to SCM plug-in sitting in SOAIB installed box.)
        • SCM Publisher.doc (This is a document on "How to" use SCM Publisher.)
        • Utils.zip (These are supplementary migration utilities to support customer upgrading from previous SOAIB build to newer one or for any product upgrade. E.g., SDM r11.2 to SDM r12.5)
        • Utils.doc (This is a document on pre-requisite and "How to" use these utilities.)

        Chat with CA

        Just give us some brief information and we'll connect you to the right CA Expert.

        Our hours of availability are 8AM - 5PM CST.

        All Fields Required

        connecting

        We're matching your request.

        Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

        • {{message.agentProfile.name}} will be helping you today.

          View Profile


        • Transfered to {{message.agentProfile.name}}

          {{message.agentProfile.name}} joined the conversation

          {{message.agentProfile.name}} left the conversation

        • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
          Thank you for your interest in CA.


          How Did We Do?
          Let us know how we did so that we can maintain a quality experience.

          Take Our Survey >

          Rate Your Chat Experience.

          {{chat.statusMsg}}

        agent is typing