Skip to Content

New and changed features in version 7.6.02

This page describes the new and changed features in this release of the following BMC Atrium Orchestrator platform components:

BMC Atrium Orchestrator Platform server components

  • Improved performance on multiple-peer grids
     The setup of your environment determines your actual performance improvements.

  • New operating system support
     You can now install the BMC Atrium Orchestrator server components on computers that run the SUSE Linux Enterprise 11 operating system.

  • New platform support for external Access Manager databases:
    • Microsoft SQL Server 2008
    • MySQL 5.1
    • Oracle 11g

  • Discontinued platform support for external Access Manager databases:
  • Repository Manager application that enables you to perform administrative tasks on adapters and modules (content) in the repository
     The Grid Manager application now includes an Applications menu that enables you to access the Repository Manager application. From the Repository Manager, you can perform the following tasks:
    • Delete selected content from the active repository.
    • Transfer content between production and development repositories.
    • Download content from the repository and save it to your local file system or external media.
    • Upload custom content or content saved to an external device to the repository.
       The new REPOSITORY_ADMIN role enables its users to access the Repository Manager. Users who have the ADMIN role can also access the Repository Manager application. After using Repository Manager, you can select the Applications menu again to return to Grid Manager.

  • Enhancements to the log files for improved troubleshooting
    • The grid.log file captures health metrics by default. You no longer need to set the log level of the Health component to INFO to start logging health metrics.
       Health metrics are not recorded in the grid.log file on the computer where BMC Atrium Orchestrator Development Studio is installed.
    • Workflow execution time is recorded in the processes.log file. When a workflow is completed, the processes.log file records the start time, the end time, and the total time to execute the workflow.
    • You can use Grid Manager to set log levels for peers as soon as the peer has been added to the grid, even if the peer has not been installed or is offline. When the peer comes online, it uses the log levels that you set in Grid Manager.
    • Log levels that you set by using Grid Manager supersede log levels you set by using log4j files, and they remain at the same levels until changed in Grid Manager. They are not reset to the default levels when a peer is restarted.

  • Operation disabled on ORCA web services
     The executeProcessGraph operation has been disabled in ORCA web services.

  • Support for Unicode characters in all text boxes in Access Manager
     Access Manager can also authenticate Unicode characters in external LDAP or Active Directory systems.

BMC Atrium Orchestrator Development Studio

In addition to consolidating the corrected problems from the 7.6.01.01, 7.6.01.02, 7.6.01.04, and 7.5.02.09 patches, this release resolves defects in several areas.

Also, BMC Atrium Orchestrator Development Studio includes the following enhancements:

  • BMC Atrium Orchestrator Development Studio can rename processes in the workspace more quickly. When you start the program or import a module, it prepares an index of all the processes in the workspace. If you rename a process, the index helps BMC Atrium Orchestrator Development Studio to implement the name change in all the affected processes, rules, and schedules.

  • You can use BMC Atrium Orchestrator Development Studio to rename a process directory, and you can use drag-and-drop within the Project Navigator to move a process directory to a different module or process directory.

  • BMC Atrium Orchestrator Development Studio automatically maps the output items from called processes to context items with matching names in the calling process. If the context items with matching names do not already exist, BMC Atrium Orchestrator Development Studio creates them.

Installation program

This section contains information about changes to the platform installation programs for version 7.6.02.

Platform installation programs now provide the required JVM

The 7.6.02 platform installation programs now automatically install version 1.6.0_21 of the Java Runtime Environment (JRE) in the BMC Atrium Orchestrator installation path. Earlier versions of the product required you to download and install the JDK prior to installing the platform components.
During platform component upgrades, the installation programs change the links from earlier JVM instances to the new JREs installed by the 7.6.02 installation programs.
This change to the installation program also eliminates the requirement to use the following silent installation properties:

Property name

Description

AO_JAVA_HOME

Property that designated the name and location of the JVM for the server platform components

DEVSTUDIO_JAVA_HOME

Property that designated the name and location of the JVM for BMC Atrium Orchestrator Development Studio

Initial grid added during CDP installation

For fresh installations of the CDP, the installation program now adds the initial grid.

  • When installing with the GUI installation, you now specify the CDP properties on two panels.
    • On the first panel, you specify whether the CDP is primary or secondary (HA) CDP.
    • On the second panel, in addition to the CDP properties, you also specify the following grid properties: grid name, grid type, and grid log level.
  • When installing with the silent installation, you can specify the following grid properties in the options file. If you omit a property from the options file, the installation program adds the grid, using the default property.
    • AO_GRID_NAME
    • AO_GRID_TYPE
    • AO_GRID_LOGGING_LEVEL

For more information about these new properties, see Installation-properties-for-platform-options-files.

Admin password change during CDP installation

If you change the Admin password in Access Manager before you install the CDP, you can now provide the name of the new password during CDP installation. If you do not provide a new password, the installation program uses admin123, which is the default password for the Admin role.

  • During a GUI installation, you can type the changed password in the Administrator Password text box on the Configuration Peer Settings panel.
  • During a silent installation, you can specify the changed password with the AO_ADMIN_PASSWORD property in the CDP options file.

Expanded communications port range

To limit potential port conflicts on peer computers, the default range of available ports for peer communications has been expanded. To view a list of all port requirements, see Communications-port-requirements.

Component

Previous default port

New default port

CDP

8081

8501

HA-CDP: The installation program sets the default HA-CDP port number by adding 2 to the primary CDP port number. For example, if you specified port 8504 for the primary CDP, the installation program assigns port 8506 for the HA-CDP.

8083

8503

AP: The first available port in the range becomes the default port. The installation program sets the start of the default port range by adding 2 to the primary CDP port number. It sets the end of the default port range by adding 256 to the starting port range. The first available port in the range becomes the listening port for the AP.

8083-8339

8503-8759

LAP: The installation program sets the start of the default port range by adding 2 to the primary CDP port number. It sets the end of the default port range by adding 256 to the starting port range. The first available port in the range becomes the listening port for the LAP.

8083-8339

8503-8759

Related topics

Corrected-issues-in-version-7-6-02Known-and-corrected-issues

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

(archive) BMC Atrium Orchestrator Platform 7.6.02