This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring your system for the BPCU

Make sure that your CLASS path and Oracle Java Runtime Engine (JRE) are correctly configured for the Best Practice Conversion Utility (BPCU).

To configure your system for the BPCU

  1. On UNIX, grant yourself execute permission to the BPCU by typing the following command:

    chmod +x bpcu.sh
  2. Make sure the following files are in your CLASS path:
    • arutilversionNumber.jar
    • arcmnappversionNumber.jar
    • bpcu.jar
    • commons-jxpath-1.3.jar
    • jaxb-api.jar
    • jaxb-impl.jar
    • jsr173_1.0_api.jar
    • log4j-1.2.14.jar
  3. To produce the BPCU difference report in XLSX format, make sure that the following files are in your CLASS path:
    • dom4j-1.6.1.jar
    • ooxml-schemas-1.0.jar
    • poi-3.5-FINAL-20090928.jar
    • poi-ooxml-3.5-FINAL-20090928.jar
    • xmlbeans-2.3.0.jar
  4. To specify the JRE for the utility, add the following entry to the appropriate file:

    set JAVA_HOME=<fullPathToJRE>

    Tip

    Run BPCU with a 64-bit JRE. 

    The BPCU uses the JRE specified by the JAVA_HOME environment variable in the following files:

    • (Windows) bpcu.bat
    • (UNIX) bpcu.sh

    To avoid out-of-memory issues, set Max Heap Size option in the bpcu.bat file to 4 GB.
    If you plan to run the BPCU on an AR System server that enforces encryption in its API, add the following items to the JRE that the BPCU will use.
    Files and providers to add to BPCU JRE on encrypted servers

    JRE directory or file to add the files to

    Files to add for Oracle Solaris, UNIX,

    and Microsoft Windows

    Files to add for IBM AIX and DB2,

    UNIX, and Windows

    jre\lib\extjsafeJCEFIPS.jar

    jsafeJCEFIPS.jar

    bcprov-jdk15-133.jar

     jre\lib\security

    US_export_policy.jar

    local_policy.jar

    US_export_policy.jar

    local_policy.jar

    These files should be from IBM.

    jre\lib\security\java.security

    security.provider.<n>+1=com. rsa._jsafe.provider.JsafeJCE

    <n> can be the last number in the section.

    security.provider.<n>+1=org. 
    bouncycastle.jce.provider. 
    BouncyCastleProvider

    security.provider.<n>+2=com.rsa.
     
    jsafe.provider.JsafeJCE 

    n can be the last number in the section.

      

    Note

    If you have installed a BMC Remedy Encryption Security product on a BMC Remedy Java client, such as BMC Remedy Developer Studio or BMC Remedy Data Import, you do not have to verify that your configuration matches the preceding specifications. Instead, use the same Oracle Java Developer's Kit (JDK) and JRE used by the client for BPCU.

      

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments