Release Notes: BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.
04
Release Notes
January 2011
www.bmc.com
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
If you have comments or suggestions about this documentation, contact Information Design and Development by email at doc_feedback@bmc.com.
Copyright 2011 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. DB2, and IBM are the trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Linux is the registered trademark of Linus Torvalds. Oracle is a registered trademark of Oracle Corporation. UNIX is the registered trademark of The Open Group in the US and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation..
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or email. To expedite your inquiry, please see Before Contacting BMC Software.
Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can:
s s s s s s s
Read overviews about support services and programs that BMC Software offers. Find the most current information about BMC Software products. Search a database for problems similar to yours and possible solutions. Order or download product documentation. Report a problem or ask a question. Subscribe to receive email notices when new product versions are released. Find worldwide BMC Software support center locations and contact information, including email addresses, fax numbers, and telephone numbers.
Support by telephone or email

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or send an email message to customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC Software

Have the following information available so that Customer Support can begin working on your issue immediately:
s
Product information Product name Product version (release number) License number and password (trial or permanent)
Operating system and environment information Machine type Operating system type, version, and service pack System hardware configuration Serial numbers Related software (database, application, and communication) including type, version, and service pack or maintenance level
s s s
Sequence of events leading to the problem Commands and options that you used Messages received (and the time and date that you received them) Product error messages Messages from the operating system, such as file system full Messages from related software
License key and password information

If you have a question about your license key or password, contact Customer Support through one of the following methods:
s
E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support center for assistance. Submit a new issue at http://www.bmc.com/support.
Release Notes
BMC Atrium Core 7.6.04

BMC Software is releasing version 7.6.04 of the BMC Atrium Core solution. These Release Notes provide information about the enhancements and known issues in this version. This information supplements and supersedes information in the documents listed in BMC Atrium Core documentation on page 38. Before you install the solution, check the Customer Support website at http://www.bmc.com/support for updated information about this version. Flashes, technical bulletins, and resolutions on the site contain details about any fixes that were issued for this version after its release. The following topics are provided: Whats new? (page 6) Installation instructions (page 15) Known issues (page 16) Updating the WSDL and EPR links in the UDDI Registry to display the HTTPS port (page 36) Support information (page 38)
Whats new?
This section briefly describes the new features that are available in BMC Atrium Core 7.6.04. This version incorporates new features since the 7.6.03 release of BMC Atrium Core components.
Atrium Integrator
Consolidating external data easily, consistently, and quickly in the BMC Atrium CMDB is key to unlocking its value. BMC has introduced the next generation in ease of integration with a wizard-based toolAtrium Integrator.
Figure 1-1: Atrium Integrator wizard
Utilizing a best-of-breed architecture, Atrium Integrator provides a wide breadth of pre-packaged connectors for almost every type of data integration (for example, JDBC, ODBC, native databases, nested XML, web services, JMS, and so on.). In addition, out-of-the-box templates allow seamless automatic mapping of business terms to CIs and addition of relationshipsdramatically reducing the most labor intensive part of data transformations. For more information, see the Atrium Integrator 7.6.04 User's Guide.
Release Notes
Atrium Integrator is installed using its own installer. You can download the Atrium Integrator installers from BMC Atrium CMDB version 7.6.04 parent directory on the Electronic Product Download (EPD) website. For information about installing Atrium Integrator, see the BMC Atrium Core 7.6.04 Installation Guide.
Atrium Service Catalog

ITIL V3 has raised the importance of service lifecycle management and the need to align IT with business goals. Creating a service catalog has two main challenges. First, customers and partners need to know clearly what services IT offers and what it does not. One reason is that services are fragmented, and service information is managed in different places or silos. Process and end user information is managed in one place, service level management is managed elsewhere, and another application manages costs.
Figure 1-2: Service Catalog UI redesigned for 7.6.04
Second, service models tend to focus on the infrastructure and on the technical services and associated CIs in an environment. The focus is on the supporting services and details and not on the business services. For example, when a particular server fails, an IT staff member might not know the business service that is affected, such as the ability to book orders. In this situation, the service model and the service catalog present only a partial view of the services. As a result of these challenges, an IT user cannot view the whole service. Rather than design a service catalog starting with the CIs, ITIL V3 requires starting with the business service.
Whats new?
The redesigned Service Catalog in BMC Atrium Core allows you to overcome fragmentation and to provide a more complete view of services: Focus on services to generate better business results. Create a catalog of services in which you manage cost, quality, and value. Use a common language for IT and businesses to communicate clearly what IT does and does not do. For information about these changes, see the BMC Atrium Core Web Services Online Help and the BMC Atrium CMDB 7.6.04 Administrator's Guide.
Atrium Explorer
To make it easier to use Atrium Explorer and to reduce the learning curve for new users, BMC Atrium Core 7.6.04 includes the following UI improvements.
Figure 1-3: Atrium Explorer enhanced for 7.6.04
To make data easier to read and for better analysis of your data, the 7.6.04 release provides several new ways to view data. New layout controls were added to make the graphical map more predictable. You now can choose a Layered view that organizes the CIs in horizontal layers according to the type of CI, relative to other CI types. The Layered layout arranges the items by levels pre-defined for each type. You can customize the layers as needed. You can view expanded CIs and relationships in a popup dialog box. The popup lets you preview the expanded CIs before you decide to add them to the view.
Release Notes
When too much data clutters your views, folded queries let you use folding rules to hide instances which are currently visible. CIs are then displayed in a special Query view. The Query view is a restricted view of the CIs, limited to the data returned from the query. The CIs returned in the Query view are a static snapshot of the data. To better manage data, the 7.6.04 release provides new actions that you can perform on CIs. Several new actions that you can perform were added to the Atrium Explorer display pane. You can choose the following context-menu options in the Atrium Explorer display pane when editing CIs: You can select a CI and choose Expand Both to view the parents and children of the CI. You can select a CI and choose Expand Default to view the CI according to its scope. A scope is a predefined query that limits the type of CIs displayed when you expand a CI. Not all CI classes have scope definitions. To view the impact of CIs from other applications, the 7.6.04 release provides a streamlined version of Atrium Impact Simulator. If you have BMC Remedy Change Management installed (or other BMC applications integrated with BMC Atrium Core), you can run a special version of Atrium Impact Simulator to proactively determine how a change to the availability of a CI affects other CIs and services. Certain features have been removed from the user interface for ease-of-use (for example, you cannot add or remove CIs).
Common Data Model

The following classes and attributes are added in BMC Atrium CMDB 7.6.04.
Table 1-1: New classes and attributes in BMC Atrium CMDB 7.6.04(Sheet 1 of 2) New class Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Existing class BMC_BaseElement BMC_BaseRelationship BMC_Offering BMC_ServiceLevelTarget BMC_Document BMC_BusinessService BMC_ContractLine BMC_FileSystem BMC_Collection New attributes ReconciliationIdType, LastUpdatedDatasetId ReconciliationIdType, LastUpdatedDatasetId IsLocked, WarrantyLevel SLTClassification DocumentPurpose, ExecutionDate, TerminationDate ServiceLifeCycle Quantity, PerPricePeriod, PriceAmount, PriceUOM, ServiceRequestId FileSystemSize, AvailableSpace, FileSystemType, BlockSize IsVirtual
Whats new?
Table 1-1: New classes and attributes in BMC Atrium CMDB 7.6.04(Sheet 2 of 2) New class Not applicable Existing class BMC_ResourcePool New attributes HighWaterMark, LowWaterMark, MaxConsumableResource, MinConsumableResource IsDefault IsAddOn, DeliveryRO ActualDecommissionDate, ProposedDecommissionDate, ProvisionDate ChoiceSelectionMode, FulfillmentDetails, OptionType Sequence, IsDefault PerTimePeriod, UOM CostAmount, CostDeliveredFlag IsLocked, MaximumQuantity, MinimumQuantity, PriceAmount, PriceLifeCycle, PriceQuantity BlockSize, NumberOfBlocks, AvailableCapacity, ConnectionType No attributes added LUNID IsCategory, CategoryName IsLocked, WarrantyLevel SLTClassification DocumentPurpose, ExecutionDate, TerminationDate ServiceLifeCycle Quantity, PerPricePeriod, PriceAmount, PriceUOM, ServiceRequestId FileSystemSize, AvailableSpace, FileSystemType, BlockSize IsVirtual HighWaterMark, LowWaterMark, MaxConsumableResource, MinConsumableResource
BMC_ServiceOffering BMC_RequestableOffering BMC_ServiceOfferingInstance
Not applicable Not applicable BMC_BaseElement
BMC_Option BMC_OptionChoice BMC_FinancialElement BMC_Cost BMC_Price
BMC_ComputerSystem BMC_IPEndpoint BMC_ApplicationSystem BMC_BaseRelationship BMC_HostedAccessPoint
BMC_StorageExtent BMC_LogicalDisk BMC_StorageVolume BMC_Tag Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable
Not applicable Not applicable Not applicable Not applicable BMC_Offering BMC_ServiceLevelTarget BMC_Document BMC_BusinessService BMC_ContractLine BMC_FileSystem BMC_Collection BMC_ResourcePool
10
Release Notes
Normalization Engine
With BMC Atrium Core 7.6.04, the following changes have been made to the Normalization Engine: The Relation Name Normalization and Impact Normalization features can now be disabled for individual datasets by using the Normalization Configuration Editor. By default, these features are enabled for all datasets. The Auto Impact Manual Editing setting for individual datasets has been added in the Normalization Configuration Editor. You can now configure the Normalization Engine to perform one of the following actions when you run a normalization job: (default) Retain any updates that you have made to the impact attributes (HasImpact, ImpactDirection, ImpactWeight, and ImpactPropagationModel) Overwrite any updates that you have made to the impact attributes with the values that are defined in the best-practice impact normalization rules The best-practice impact normalization rules now identify matching relationships by comparing the ImpactPropagationModel and ImpactWeight attributes in addition to the Name, HasImpact, and ImpactDirection attributes. For more information, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide.
Product Catalog
With BMC Atrium Core 7.6.04, the following changes have been made to the Product Catalog: In the earlier BMC Atrium Core releases, you had to select individual Product Catalog entries to update details such as the lifecycle status. If you had a large number of Product Catalog entries, updating the entries was a very slow and difficult process. For example, if you wanted to associate all the versions of 50 different product entries with a software license contract, you had to open the entry for each product version and then set the Requires Contract field to Yes. With this release, BMC Atrium Core significantly improves the ability to simultaneously update a large number of Product Catalog entries that are associated with the same company. You can perform bulk updates on the product entries that you have manually created, imported through the staging forms, or created using the Normalization Engine. The Search New Products console has been renamed as the Manage Products Console. You can access this new console by selecting Bulk Functions > Manage Products in the navigation bar on the Product Catalog Console. The Manage Products Console provides the ability to search for product entries related to a single company and to select multiple product entries from the search results list.
Whats new?
11
Figure 1-4: Manage Products Console in Product Catalog
You can choose to perform the following bulk updates on the selected product and version entries: Hide or display the products and versions in the Product Catalog Console Relate the product versions to a software license contract Set the lifecycle status of the products and versions Set the status flags for the products and versions Delete the offline products and versions
12
Release Notes
Additionally, the Approved, Managed, and Blacklisted flags are not displayed on the Manage Products Console. Instead, you can select an option from the Product Associations with CMDB or Version Associations with CMDB list to specify a predefined combination of these flags. The following table provides information about the mapping between the status flags and the options that are displayed in the Product Associations with CMDB and the Version Associations with CMDB lists.
Product or Version Associations with CMDB Approved and Managed Description Approved Managed Blacklisted
Yes Select this option for products or versions that are approved for use in the production environment and which should trigger an action from IT. Yes Select this option for products or versions that are approved for use in the production environment but which should not be tracked by IT. Yes or No Select this option for products or versions that have been identified as a security risk in the production environment and should trigger an action from IT. No Select this option for products or versions that are not approved for use in the production environment and which should trigger an action from IT. Select this option for products or versions that are not approved for use in the production environment but which should not trigger an action from IT. No
Yes
No
Approved and Unmanaged
No
No
Blacklisted
Yes or No
Yes
Unapproved and Managed
Yes
No
Unapproved and Unmanaged
No
No
The Verification Key, Minimum CPUs, Minimum CPU Speed, Minimum RAM, and Minimum Disk Space fields have been added to the Product Model / Version form. The BMC Atrium Core 7.6.04 Product Catalog and DML Guide has been restructured to ensure that information can be accessed more effectively. For more information, see the BMC Atrium Core 7.6.04 Product Catalog and DML Guide.
Whats new?
13
Reconciliation Engine
With BMC Atrium Core 7.6.04, the following changes have been made to the Reconciliation Engine: The ReconciliationMergeStatus attribute has been added to the BMC_BaseElement class. When an instance is added or updated in a dataset, BMC Atrium CMDB sets the ReconciliationMergeStatus attribute of that instance to Ready to Merge. The Merge activity considers only those instances that have a Reconciliation ID and for which the ReconciliationMergeStatus attribute is set to Ready to Merge. If you resume a reconciliation job that was paused during the Merge activity, the Reconciliation Engine now considers only those CIs for which the ReconciliationMergeStatus attribute value was Ready to Merge when the job was paused. You can now run multiple reconciliation jobs in continuous mode at a given time. The Look Into Other Datasets for Parallel Continuous Jobs option has been added in the Server Configuration Editor. This option enables you to configure the continuous jobs to run the identify activity on all the source datasets in addition to the production dataset. This ensures that the same Reconciliation ID is assigned to identical CIs in all the source datasets and the data integrity is maintained. If the logging level is set to Error, the Reconciliation Engine creates a new 0 byte log file for each run of a reconciliation job, even when a job is successful. You can now configure the deletion of 0 byte log files for individual reconciliation jobs. For more information, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide.
Web Services
The atrium_businessobjects and atrium_query services have been deprecated and replaced with new atrium_ businessobjects and atrium_ querybypath services. These services include updated operations and business objects for the changes to the Service Catalog. For information about these changes, see the BMC Atrium Core Web Services Online Help.
Software license management

With BMC Atrium Core 7.6.04, the following changes have been made to the Suite Rollup and Version Rollup features: The Suite Rollup feature is now supported in continuous normalization mode. BMC recommends that you create and enable the Suite Rollup rules based on the Product Catalog data before you enable continuous normalization mode. The Suite Rollup feature now supports the deletion and upgrade of required components in a product suite.
14
Release Notes
When the Product Catalog has priority over the Version Rollup rules in normalizing the MarketVersion attribute, the Normalization Engine now applies the activated Version Rollup rules to a configuration item (CI) instance only if the Market Version is not set in the Product Catalog. This change significantly improves the performance of the Version Rollup feature. For more information, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide.
Installation instructions
This section contains information about supported configurations and installation or upgrade procedures. Except where noted, see the instructions in the BMC Atrium Core 7.6.04 Installation Guide when you are installing or upgrading to BMC Atrium Core 7.6.04.
Prerequisites
You must install BMC Remedy AR System 7.6.04 or later before installing BMC Atrium Core 7.6.04.
Installation
For detailed instructions about planning your BMC Atrium Core deployment and running the installer, see the BMC Atrium Core 7.6.04 Installation Guide. This section provides information about BMC Atrium Integration Engine licenses and installing online help.
Installing BMC Atrium Core online help

WARNING
Only English is supported in the 7.6.04 release of the BMC Atrium Core online help. When you are installing BMC Atrium Core online help with the Microsoft IIS web server, the default path constructed in the Confirm URL panel is wrong (SW00372079).
http://webServer:portNumber/inetpub/wwwroot/ARSServer/AtriumCMDB
When registering the URL for the installation directory in the SHARE:Application_Properties file, enter the following URL instead:
http://webServer:portNumber/ARSServer/AtriumCMDB
For example:
http://calbro-idd02:80/calbro-idd01/AtriumCMDB
Installation instructions
15
Known issues
The following section describes the known issues in BMC Atrium Core and Atrium Integrator: BMC Atrium Core known issues on page 16 Atrium Integrator known issues on page 32
BMC Atrium Core known issues

Table 1-2 describes the known issues in BMC Atrium Core version 7.6.04.
Table 1-2: BMC Atrium Core Known issues Issue SW00221073 SW00244510 Description When you are adding a Currency attribute to a class, you cannot specify Allowable Currency Types for it. Exporting a Reconciliation Engine job that contains an execute job activity does not export the job called by that activity. Workaround: When exporting an individual job that contains an execute job activity, you must also export the job called for in the execute job activity. SW00264484 If you extend the BMC Atrium CMDB and the parent class has categorization subclasses, warnings in the log files might state that certain fields could not be found. For example: [Tue Apr 14 2009 12:38:26.6834] [WARNING] [TID: 000002] : Could not create Field: SubnetMask on form: AST:DLCI on server: myserver [Tue Apr 14 2009 12:38:26.6836] [WARNING] [TID: 000002] : Message: Field does not exist on current form - 260140107 You can ignore these warnings, which appear because the BMCSynchronizeUI process finds fields on the parent form for categorization subclasses. Because these attributes are not derived from the class in question, they should not be created on the UI forms. SW00279844 When two or more categorization subclasses are derived from one class, auditing does not work properly for the subclasses. For example, if you enable log auditing, the audit does not produce a log file for the categorization subclasses. In the BMC Atrium Core Console, after you open any widget, clicking the browsers refresh button logs you out of the BMC Atrium Core Console. Workaround: Use the Refresh button in the BMC Atrium Core Console. SW00304034 When using a BMC Remedy User client to access Flex-based interface elements, you cannot use the mouse to select items in a combo box. Workaround:
1 Click the list with the mouse to open the list. 2 Use the up and down arrow keys to select the list item. 3 Click the list item with the mouse.
SW00288931
SW00305649
In the Product Catalog, the Atrium Foundation Viewer permission is not fully functional. A user belonging to only the Atrium Foundation Viewer group is not restricted to view-only operations.
16
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00311037 SW00314472 Description HP-UX Itanium is not backward compatible with the BMC Atrium CMDB 2.1 client binaries. For the Reconciliation Engine, the standard jobs fail to execute after execution of a Rename job for the dataset for which the standard jobs were created. Workaround: After executing a rename dataset job, you must modify the dataset name in all job definitions where it is referenced. SW00315179 Installation fails on the Sun Solaris platform if any processes are running on port 12333. Workaround: Locate and stop any processes running at port 12333. Then restart installation. SW00316799 SW00322538 BIGINT gets translated into ULONG by the federation JDBC adapter, but gets initialised with INT limits. If you are running a DB2 database on AIX, a chained nested query raises an exception (when you use query-by-path).
Note: This is a known DB2 issue for complex queries, which does not allow the subquery in
an ON clause used with the join. SW00325683 In the BMC Atrium Integration Engine, when you create a new CI or relationship class mapping and then select the Primary Key Mapping tab, the DatasetId and Name attributes appear in red. The red indicates that they are required fields for primary key mapping, but they are not. Workaround: Ignore the red text in the Primary Key Mapping tab. Select the appropriate attribute as the primary key.
Known issues
17
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00336843 Description After upgrading to BMC Atrium Core, logging for the AR adapter is not enabled because the log configuration file is missing entries. Workaround: Use the following procedure to add entries for the AR adapter.
1 In a text editor, open the log4j_pluginsvr.xml file in atriumInstallDirectory/ 2
4 5
cmdb/plugins/shared. In the <appender> section, add the following entries for the AR adapter: <appender name="com.bmc.atrium.federation.ar.appender" class="org.apache.log4j.RollingFileAppender"> <param name="File" value="atriumInstallDirectory/Logs/federationar.log" /> <param name="MaxFileSize" value="5MB"/> <param name="MaxBackupIndex" value="100000"/> <param name="Append" value="true" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="(%.10t) %d{ISO8601} %p %F:%L %m%n"/> </layout> </appender> In the <logger> section, add the following entries: <logger name="com.bmc.atrium.federation.ar" additivity="false" > <level value="INFO" /> <appender-ref ref="com.bmc.atrium.federation.ar.appender" /> </logger> Replace the value for the Name parameter with your directory structure. Restart the BMC Remedy AR System server.
SW00337378
The computed groups for Demo do not appear in the Computer Group List, and the Class Manager and Service Catalog application icons are not visible. Workaround: Use the following procedure:
1 Open the Group form. 2 For any of the missing groups, add a space and then remove the space. 3 Save the form. 4 In the User form, refresh the Demo instance.
All the missing Computed Groups appear. SW00338441 If you create alias mappings from the Catalog Mapping window, the Normalization Engine does not update existing CIs with the Model, ManufacturerName, Category, Type, and Item values specified in the aliases. Workaround: Restart the BMC Remedy AR System server, and run the normalization job again. The Normalization Engine updates the CI with the alias values. SW00340759 On an HP-UX Itanium computer, if you enable Product Catalog data import during the BMC Atrium Core installation, the import is extremely slow.
18
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00342891 Description Custom administrative users with full access see errors when creating CIs in Atrium Explorer (as described in Calbro Services exampleCreating users in the BMC Atrium CMDB 7.6.04 Administrator's Guide). The CI is created, but the user cannot view the CI due to incorrect permissions on the CI. Workaround: Map the full-access administrator regular group to the CMDB Data View All and CMDB Data Change All roles. Custom administrative users with full access can then create and view the CIs in Atrium Explorer. SW00343412 Sometimes, when you reconcile new or updated relationships into a target dataset, a cardinality violation error occurs, and the creation or update of those relationships fails. This rare, inconsistent behavior is caused by a lower reconciliation ID for an active relationship instance than a relationship marked for deletion. Workaround:
1 Modify all mark-as-deleted relationships and then run the job again so that all mark-as-
deleted relationships are created and merged into the target dataset.
2 Modify all active relationships that will be created or updated in the target dataset. The
modification of relationships should be done for only failure relationships. SW00343442 SW00340870 When you install the Product Catalog on Linux with an IBM DB2 database, the following error appears on the Product Catalog Console: No item matches active link conditions; this operation has been defined so that no match generates an error. (ARERR 1602) SW00343600 Users assigned to the Administrator group list cannot run simulations with a floating license. Workaround: Assign the user a fixed license. SW00344249 After you run the BMC Atrium Core installer to remove the Web Services components, the installer provides the following options for restarting your computer: Yes, restart my system. No, I will restart my system myself. If you select the first option, the installer does not restart your computer automatically. Workaround: Restart your computer manually. SW00344627 BMC Atrium Core Console has a time delay between creating a base class and the next correct read of the class data. For example, if you create a base class and immediately create an instance of it, an error results because the required Submitter field is not specified. Workaround: After creating a new base class in the Class Manager, wait 5 minutes before creating a subclass or doing any operation on the newly created base class.
Known issues
19
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00348336 Description When your computer is running AR System 7.5.00/BMC Atrium Core 7.6.00 and you upgrade to 64-bit BMC Remedy AR System 7.6.04, you see the following errors in the arerror.log file because BMC Atrium Core remains in an intermediate 32-bit state: ProcessMain : Error encountered while loading the shared library (ARERR 9750) cmdbsvr76.dll: %1 is not a valid Win32 application. You must upgrade BMC Atrium Core to 64-bit, as described in the BMC Atrium Core 7.6.04 compatibility matrix. SW00356310 If you turn on the auditing for a class and the auditing type is Copy, and then if the auditable attribute is changed, you cannot see the history of the record from the user interface. Workaround:
1 Log in to your server. 2 Open the Server Information form (choose AR System Administration Console > System >
General > Server Information). 3 Click the Configuration tab. 4 Select Disable Audit Change Only Fields. 5 Click OK. If these steps do not allow you to see the history of the record, try the following steps:
1 Open the class form in BMC Remedy Developer Studio.
For example, the form name for the BMC_ComputerSystem class is BMC.CORE:BMC_ComputerSystem.
2 Select Form > Form Properties. 3 In the left pane, click Audit. 4 Set the Audit Only Changed Fields option to No. 5 Click OK.
SW00358695
The Atrium_ServiceImpact web service throws a NoClassDefFound exception when queried with an empty attributesToInclude list for the GetRelatedServices operation.
Note: At least one attribute needs to be passed in attributesToInclude list for the operation to
work. SW00363699 When upgrading BMC Remedy AR System from version 7.5.00 on Linux with either BMC Atrium CMDB 7.5.00 or BMC Atrium CMDB 7.6.00 installed, the BMC Remedy AR System server upgrade crashes. Workaround: If you are upgrading BMC Remedy AR System only, contact Customer Support to obtain a hot fix for BMC Atrium CMDB that will enable the upgrade to BMC Remedy AR System 7.6.04 to complete successfully. After you upgrade BMC Remedy AR System, you can upgrade to BMC Atrium CMDB 7.6.04 (or remain on BMC Atrium CMDB 7.5.00). If you are upgrading BMC Remedy AR System and BMC Atrium CMDB, comment out the following lines in the file ARSystemServerInstallDir/conf/ar.conf to prevent the CMDB engine library from being loaded: #Load-Shared-Library-Path: /data1/bmcsoftware/Atrium76/cmdb/ server/bin #Load-Shared-Library: libcmdbsvr76_lx64.so
Note: Your Load-Shared-Libray-Path might be different from the example.
20
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00364449 Description The Apply To All Children of Class property (in the BMC.CORE.CONFIG:BMC_NotificationRule form) does not work as expected. For example, you define the relationship name normalization rule ABC for the BMC_Component relationship instance. This rule sets the name to COMPONENT when a relationship is created between any source and destination class type. When an instance of BMC_ContractComponentwhich is a child of BMC_Componentis created, the rule ABC is not applied as expected. Workaround:
1 In the BMC.CORE.CONFIG:BMC_NotificationRule form, create a copy of the rule. 2 Modify the record to change the Rule Class Name to the name of the child class for
which the rule should be applied. For example, create a copy of the rule that was defined for class BMC_CORE:BMC_Component class, and then change the Rule Class Name to BMC.CORE:BMC_ContractComponent. SW00369564 Upgrading BMC Atrium Core 2.0.1 or 2.1 to 7.6.04 fails in a BMC Remedy ITSM 7.0.3 Patch 10 environment. Workaround: Before upgrading BMC Atrium Core, rename the following forms in BMC Remedy ITSM 7.0.3 Patch 10 using BMC Remedy Developer Studio. Old form names PCT:Product M-V Utilization PCT:Product M-V Uti Com LookUp PCT:Product M-V Company Lookup PCT:Product Model-Version New form names PCT:Product M/V Utilization PCT:Product M/V Uti Com LookUp PCT:Product M/V Company Lookup PCT:Product Model/Version
Known issues
21
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00370909 Description In Class Manager, the audited values do not display properly in the View History of the CI when: auditing is turned on for the class Audit Type is set to Copy auditable attribute is changed (for example, Audit Option of attribute is set to Audit & Copy) Workaround:
1 Open the Server Information window in the AR System Administration Console. 2 Navigate to the Configuration tab. 3 Select the Disable Audit Only Change Fields option. 4 Click OK.
If you still cannot see the audited values, perform the following additional steps:
1 Open the class form in BMC Remedy Developer Studio. For example, the form name for
the BMC_ComputerSystem class is BMC.CORE:BMC_ComputerSystem.

2 Choose Form > Form Properties. 3 Select Audit on the left pane. 4 Set the Audit Only Changed Fields option to No. 5 Save your changes.
SW00372156
In the BMC Atrium Integration Engine, when you export data to a file with the AIE Definitions Admin role, you see an error saying that you cannot access the Application Pending form. This problem occurs because the Application Pending form could not find a new group mapped to the AIE Definition Admin and CMDB Definition Viewer roles. Workaround: Before running the export utility, add the group that you created to the Application Pending form as follows:
1 Open the Application Pending form in BMC Remedy Developer Studio. 2 Select Form > Form Properties. 3 In the left pane, click Permissions. 4 Grant permissions to the new group. 5 Click OK.
SW00373105
When you save a new query, you might see an error message if you are using Java version 1.6. This error is displayed because the JAXB 2.0 API is being loaded from the bootstrap classloader, whereas this runtime instance needs the JAXB 2.1 API. Workaround: You must place the jaxb-api.jar file in the bootstrap classloader by following the directions in the following URL: http://java.sun.com/j2se/1.5.0/docs/guide/standards/ To avoid this error, upgrade to Java version 1.6.04.
22
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00373849 Description If you have Adobe Flash 9 installed, the right-click menu items for multibyte strings appear as question marks. This is a known issue for Adobe Flash 9. Workaround: Upgrade to Adobe Flash 10, which fixes this issue. If you cannot upgrade to Adobe Flash 10, you can modify the regional settings, as follows:
1 From the Windows Control Panel, choose Regional and Language Options. 2 From the Advanced tab, change the Language for non-Unicode programs option to the
required multibyte language. SW00373851 Uninstalling BMC Remedy AR System does not clear the Mid-Tier cache. Workaround: Clear the Mid-Tier cache after uninstalling BMC Remedy AR System. SW00374055 When you create a BMC Atrium Integration Engine instance on the primary server in a server group environment, the instance does not get propagated to the secondary server Workaround: Make sure that at least one instance is active on the primary server before creating a new instance. SW00374225 You cannot delete Site Alias and Site Company Relationship records unless you have Administrator permissions. You see the following error message: You do not have write access to field : 1000000076 (ARERR 330) Workaround:
1 Open BMC Remedy Developer Studio. 2 Open the SIT:Site Alias form. 3 Select Form > Add/Remove Fields In View and then add the z1D Action field (1000000076) 4 5 6 7
to the form view. In Permissions under the Properties tab, modify the permissions on the z1D Action field to include the General Access Group with Change permission. Select Form > Add/Remove Fields In View and then remove the z1D Action field (1000000076) from the form view. Save your changes. Open the SIT:Site Company Association form and perform steps 3 to 6 to it.
SW00374286
If you create new attributes in a class, the client cache is not immediately updated. As a result, you cannot use these attributes in the Query Builder widget to construct queries. Workaround: You must update the cache on your browser client with the following steps:
1 Open the BMC Atrium Core Console. 2 Right-click in the display pane and choose Settings. 3 From the Local Settings in the Adobe Flash Player Settings dialog box, move the slider 4 5 6 7
down to a low number (for example, 10 KB) but do not select None. Click OK. Click Close Refresh the browser or reload the page. In the Adobe Flash Player Settings dialog box, click Allow to store the updated information on your computer.
The attributes will now be available for use in the Query Builder widget. Known issues 23
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00374582 Description When you are using the AR System Server Group with a Load Balancer, the launch interface link to the Product Catalog in Atrium Explorer tries to access the primary server but returns ARERR [9280] Server not present in the configured servers list, because the link cannot find the primary server in the list of servers configured with BMC Remedy Mid Tier. Workaround:
1 Open Federation Manager. 2 Click the Launch Definitions tab. 3 Select the Product Catalog entry in the Federation Launch Interfaces section, and then click
Edit. 4 In the Server Name field, remove the primary server and enter the Load Balancer name. 5 Click OK.
Note: This setting will continue to work even if the primary or secondary servers are down,
because Load Balancer handles sending the client requests to the correct server. SW00374712 When you create a federation plugin in an AR System Server Group environment with a Load Balancer, the Server Plugin Alias entry in the ar.cfg file contains the load balancers name. This prevents the plugin from properly loading. Workaround:
1 Open the ar.cfg file on the primary server. 2 Replace the load balancers name by the primary server name. 3 Restart the primary server. 4 Open the ar.cfg file on the secondary server. 5 Replace the load balancers name by the secondary server name. 6 Restart the secondary server.
SW00379933
Although you configured the web services port to HTTP by using the atriumws utility, the Web Services Definition Language (WSDL) and Endpoint Reference (EPR) links in the UDDI Registry display the HTTPS port. Workaround: For information about resolving this issue, see Updating the WSDL and EPR links in the UDDI Registry to display the HTTPS port on page 36.
SW00380379
Due to WAR file path change on AIX systems, the BMC Atrium Core Console returns the following error: Error calling destination cmdbclassservice [object Object] Workaround:
1 Copy websvcjava7604_build002.jar from midTierInstall/WEB-INF/lib
folder to another location.

2 Open the JAR file with a zip utility. Rename the file to .zip if necessary. 3 Navigate to the xerces (org/apache/xerces) directory. 4 Delete the xerces directory and all the files under/in it. 5 Rename back to websvcjava7604_build002.jar. 6 Copy over the original JAR file in the midTierInstall/WEB-INF/lib folder. 7 Restart the BMC Remedy Mid Tier.
24
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00383098 Description Running an Identify job in the Reconciliation Engine sometimes ends at 99%, leaving the remaining 1% of CIs unidentified and unprocessed. Workaround: This condition is intermittent and not serious. Your next Identify job will identify and process the remaining CIs. SW00383260 Values are missing from the description of BMC_ComputerSystem attribute PrimaryCapability. The BMC Atrium CMDB 7.6.04 CDM Help does not display the complete list of values for the PrimaryCapability attribute of the BMC_ComputerSystem class. The missing values are: VPN Concentrator(50) Proxy Server(51) Layer 3 Proxy Server (52) WAN Accelerator (53) SAN Processor (54) SW00383365 If you are displaying the Manage Products Console in the Product Catalog with the 7.1.00 or 7.5.00 versions of BMC Remedy User, you cannot perform the selected action for the selected product as well as the model version as expected. Workaround: Use the 7.6.04 version of BMC Remedy User or use the BMC Remedy Mid Tier. SW00383367 If you are displaying the Manage Products Console in the Product Catalog with the 7.1.00 or 7.5.00 versions of BMC Remedy User, the selected product details are not properly displayed when you select the product and click the View Details button. Workaround: Use the 7.6.04 version of BMC Remedy User or use the BMC Remedy Mid Tier. SW00384574 After successfully upgrading to BMC Atrium Core 7.6.04, you sometimes see a warning message: (Dec 07 2010 04:38:16.061 PM +0530), WARNING, com.bmc.install.utility.platform.CommandLineHelper, LOG EVENT {Description=[20101207 163816.060079 mkill: MCLI: BMC-IMC300011E: Could not connect to Cell ais]} You see this warning because the installer has already stopped the AIS service but then executes another stop command to make sure that the AIS service has stopped. You can safely ignore the warning. SW00385894 When you upgrade to BMC Atrium Core 7.6.04 and create a new Version Rollup rule in the Normalization Console, the following error message is displayed if the Normalization Job Run Schedules form contains invalid data: Internal Normalization Engine Error - Rule id returned was null. Workaround:
1 In BMC Remedy User or a browser, open the Normalization Job Run Schedules form in the
search mode. 2 Click search to display the list of existing job schedules. 3 Select the job schedule entries in which the value of the Schedule String field is empty or 0;0. 4 Delete the selected job schedule entries.
Known issues
25
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00385992 Description If you re-run the BMC Atrium Core installer on the same computer and you change the port numbers (for example, the ports 9555, 9556 and 7791 were modified to 8555, 8556, and 8791) during installation, perform the following steps in the ar.cfg (Windows) or ar.conf (UNIX) files so that Atrium Core functions properly:
1 Open the ar.cfg (or ar.conf) file in ARInstallDirectory/Conf. The file will
contain two sets of plugin alias stringsone set with the old port number and one set with the new port number. 2 Delete all the plugin strings with the old port numbers 9555 and 9556. The updated configuration file should now list only the plugin strings with the new port numbers. For example: Server-Plugin-Alias: BMC.FILTERAPI.NORM.ENGINE BMC.FILTERAPI.NORM.ENGINE vm2-w2k3-prem06:8555 Server-Plugin-Alias: BMC.ARDBC.DEPRECATION.PLUGIN BMC.ARDBC.DEPRECATION.PLUGIN vm2-w2k3-prem06:8556 Server-Plugin-Alias: BMC.FILTERAPI.NOE BMC.FILTERAPI.NOE vm2w2k3-prem06:8556 Server-Plugin-Alias: BMC.FILTERAPI.EVENT_ENGINE BMC.FILTERAPI.EVENT_ENGINE vm2-w2k3-prem06:8556 Server-Plugin-Alias: AIS.FILTERAPI AIS.FILTERAPI vm2-w2k3prem06:8556 Server-Plugin-Alias: BMC.ARDBC.ATRIUM.API BMC.ARDBC.ATRIUM.API vm2-w2k3-prem06:8556 Server-Plugin-Alias: DSM.FILTER DSM.FILTER vm2-w2k3-prem06:8556 Server-Plugin-Alias: BMC.ARDBC.ATRIUM.NGIE BMC.ARDBC.ATRIUM.NGIE vm2-w2k3-prem06:8556 3 Re-start the AR System server.
Note: You can go to the \cmdb\plugins\shared Atrium Install Directory and read the
pluginsvr_config.xml file for the new port number. To update the AIS listener port, the mcell.dir file (under $ATRIUMCORE_HOME\ais\etc) could similar entries as the following example: cell ais ais 127.0.0.1:7793 gateway.imcomm ais_gateway ais w8k-atrium-vm15:7791 gateway.imcomm ais_gateway ais w8k-atrium-vm15:8791 gateway.imcomm ais_gateway_w8k-atrium-vm15_8791 ais w8k-atriumvm15:8791 gateway.imcomm ais_gateway_w8k-atrium-vm15.dsl.bmc.com_8791_FQDN ais w8k-atrium-vm15.dsl.bmc.com:8791 gateway.imcomm ais_gateway_w8k-atrium-vm15_8791 ais w8k-atriumvm15:8791 gateway.imcomm ais_gateway_w8k-atrium-vm15.dsl.bmc.com_8791_FQDN ais w8k-atrium-vm15.dsl.bmc.com:8791 Remove all entries that start with gateway. Leave the one entry that starts with cell and the proper port. Make sure only the new entry is included in the mcell.dir file. For example: cell ais ais 127.0.0.1:7793 Restart the AIS cell. The proper entries will be regenerated in the mcell.dir file.
1 2 3 4
26
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00386052 Description After an upgrade, log statements from the CMDBf plugin erroneously appear in the AtriumPluginSvr.log file. These statements occur because of a parameter in the AtriumCoreInstall/cmdb/plugins/shared/log4j_pluginsvr.xml file under the  section. The additivity="true" setting should be additivity="false". You can safely ignore these statements. Workaround: You can stop these log messages by changing the additivity flag to false and then restarting the AR System server. SW00386369 If the DSO link is not functioning but creating or modifying CIs still continues on both the Cloud and Enterprise CMDB servers, you might encounter the following error when the DSO link recovers and if bulk data (for example, 5000 CIs or more) is pending for transfer to the destination server: No such form/entry, no work needed-- occurred in stage 3 -- Get source entry details. This problem is a defect on the BMC Remedy AR System DSO server. BMC intends to fix this problem in a future release. SW00386683 When running the extension loader for first time in a DSO environment, you might see an error about not finding the Distributed Logical Mapping form. This problem typically occurs only when you run the extension loader for the first time, because the first extension loader task is adding the DSO license (which creates some system forms). The second extension loader task is creating an entry in one of those system forms. If your system is slow and the first task is not finished, you might see an error when the second task is executed. Workaround:
1 Remove the DSO-related entries from the SHARE:Application_Properties form. 2 Run the extension loader again.
BMC intends to fix this problem in a future release. SW00386734 When processing bulk data, Reconciliation Identify and Merge jobs sometimes slow down dramatically, or get stuck. This behavior is intermittent. Workaround: For Identify and Merge runs with bulk data on an Oracle database, set the Cursor_Sharing parameter to Force. For more best practices to optimize performance, see the Performance Tuning for Business Service Management white paper.
Known issues
27
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00386743 Description The GetSavedQuery operation in the atrium_query_20 Web service returns SOAP responses containing elements which are not valid against the XML schemas which define them. Client tools which require elements to strictly conform to the referenced XML schemas will likely fault when receiving these responses, though the error messages will vary depending on the client tool. When analyzing the response through an XML validation tool, the following response identifies the nature of the failure: 1 : cvc-complex-type.2.4.a: Invalid content was found starting with element 'queryByPathObject'. One of '{categoryName}' is expected. Workaround: The only workaround is on the client-side. When you generate client stubs against the WSDL, select an appropriate option that prevents errors in the client when any required elements are missing in the responses. For example, when you generate client stubs in Axis2 using the wsdl2java tool and use ADB binding, add the "-Eosv" option to turn off strict parsing. The available options in client tools differ, and this particular option might not be available to you. However, some clients perform this action as their default behavior. SW00386744 The ExecuteSavedQuery operation in the atrium_query_20 Web service returns SOAP responses containing elements which are not valid against the XML schemas which define them. Client tools which require elements to strictly conform to the referenced XML schemas will likely fault when receiving these responses, though the error messages will vary depending on the client tool. When analyzing the response through an XML validation tool, the following response identifies the nature of the failure: 1 : cvc-elt.3.1: Attribute 'http://www.w3.org/2001/XMLSchemainstance,nil' must not appear on element 'aliasOrderForListFormat', because the {nillable} property of 'aliasOrderForListFormat' is false. Workaround: The only workaround is on the client-side. When you generate client stubs against the WSDL, select an appropriate option that prevents errors in the client when any required elements are missing in the responses. For example, when you generate client stubs in Axis2 using the wsdl2java tool and use ADB binding, add the "-Eosv" option to turn off strict parsing. The available options in client tools differ, and this particular option might not be available to you. However, some clients perform this action as their default behavior. SW00387044 After you successfully install the web services registry in an IBM DB2 database, the atriumcore_install_log.txt file displays a severe error message. For example: SEVERE,com.bmc.install.product.atriumfoundation.wsc.task.WSCDatabas eInformationValidationTask, THROWABLE EVENT {Description=[Failed to getARServerDBVersion],Detail=[com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: ROOT.CONTROL]}, Throwable=[com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: ROOT.CONTROL
28
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00387140 Description For UNIX systems running DSO, the Atrium Maintenance tool does not properly configure the destination server name and does not uncomment serverds.exe in the armonitor.cfg file. Workaround:
1 Provide the name of destination server in the Distributed Logical Mapping form. 2 Comment out the #/opt/bmc/ARSystem/bin/arservdsd -s serverName -i
/opt/bmc/ARSystem entry in the armonitor.cfg file.

3 Restart the AR System server. When DSO is executing, the server throws a
NullPointerException error. This error is benign and can be safely ignored. SW00387262 On Windows 64-bit computers, if you create a class and you try to synchronize the class in BMC Atrium CMDB with BMC Remedy Asset Management (Application Administration Console > Custom Configuration > Asset Management > Advanced Options > Sync Asset UI), sometimes the CMDBSynchronizeUI.log is not properly generated. When this log file is not generated, the AST form for that class is not generated either. This condition is intermittent. Workaround:
1 Create a folder path (for example, C:\arservdb\arserver\db\) before you run the
cmdb2asset utility.
2 Run the cmdb2asset utility to synchronize the UI. The CMDBSyncUI.log file is then
properly generated in the new folder. SW00387494 If you are upgrading from version 7.5.00 or later, choose a new installation directory for the upgrade that is not below the BMC_AR_SYSTEM_HOME directory. During the upgrade when you use new directory, you see the following message: BMC Atrium Core installation found installed on the system. Select the same path to upgade BMC Atrium Core components. Ignore the error message. For more information, see the upgrade chapter in the BMC Atrium Core 7.6.04 Installation Guide.
Known issues
29
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00387504 Description If you are upgrading BMC Atrium Core from version 7.5 or later, you now must make sure that the AtriumCore directory is not under BMC_AR_SYSTEM_HOME. As a result however, the installer runs into exceptions when it cannot find the AtriumCoreInstalledConfiguration.xml file. Workaround:
1 Clean out the %temp% folder 2 Uninstall the Web Services Components if they are already installed. 3 Create a new folder for the upgrade. For example:
C:\Program Files\BMC Software\AtriumCore_New

4 Copy the AtriumCoreInstalledConfiguration.xml file from the old location to the
new location. 5 Create a backup of AtriumCoreInstalledConfiguration.xml. 6 Create an aie folder in your new installation folder. 7 Create a aie file under C:\Program Files\BMC Software\AtriumCore_New\aie. For Windows, name the file aie.exe For UNIX, name the file aie During the AIE upgrade, the installer looks for the aie executable to ensure that the aie binaries are in place and that the existing installation is proper.
8 Update the ATRIUMCORE_HOME environment variable with the new path. 9 Run the installer and install BMC Atrium Core in the new path.
SW00387511
When you are migrating your business service CIs during an upgrade and they are not classified as either Business or Technical type, no default Service Offering is created for them. Without a default Service Offering, the migration fails for any SRD that references the service in BMC Service Request Management. You typically see this problem if the business services CIs were created manually but improperly classified. Workaround: Make sure the service CIs are properly classified before you start the upgrade, so that they conform to the BMC service model.
1 Open the Service Request Definition Base form in Search mode. 2 Choose View > Advanced Search Bar. 3 Enter the following qualification, and then click Search to find matching requests: 4
5 6
7 8 9
'BusinessServiceInstanceId' != $NULL$ For each request, note the value in the BusinessServiceInstanceId field, or export the matching request and include the value of the BusinessServiceInstanceId field in the exported data. Open BMC.CORE:BMC_BusinessService form in Search mode. In the Advanced Search Bar, enter the following search terms: 'InstanceId' = "instanceIdFromStep3" AND 'ServiceType' = "Unknown" If your query returns the record, click the Custom tab and then set the Service Type field in the CIs either to BusinessService or TechnicalService. Click Save. Repeat step 5 and step 6 for all requests found in step 3.
30
Release Notes
Table 1-2: BMC Atrium Core Known issues (Continued) Issue SW00387701 Description When upgrading BMC Atrium Integration Engine 7.1.00 Patch 008 to 7.6.04 on a 64-bit system, BMC Atrium Integration Engine is not detected in the upgrade. As a result, BMC Atrium Integration Engine is detected as a fresh install. Workaround:
1 Open the registry editor (by running regedit from command prompt). 2 Go to the following location:
3 4 5 6
HKEY_LOCAL_MACHINE\Software\Wow6432node\BMC Software\BMC Atrium Integration Engine Export the registry key. Edit the exported reg file and replace all instances of \Wow6432node\ with \. Save the reg file and import it into the registry. Run the BMC Atrium Core installer to upgrade BMC Atrium Integration Engine. BMC Atrium Integration Engine will upgrade successfully.
SW00387801
If you install Atrium Core Web Services 7.6.04 on a UNIX system using a non-root user account that does not have writable permission to the JRE installation folder and its subfolders, the installer displays a panel with the following message: java.securty file is not writable. java provider directory is not writable. Workaround: Provide the non-root user account with writable permission to the JRE installation folder and its sub-folders.
SW00387924
While running the extension loader, the existing data is transferred to the destination server. For the DSO transfer to succeed, the DSO import dataset must first exist on the destination server. The DSO import dataset is created on the destination server when the extension loader is executed on it. For example, if the extension loader is executed on the Enterprise CMDB first and it has existing data to be transferred using DSO to the Cloud CMDB, then you must first create the DSO import dataset on the Cloud CMDB manually before you run the extension loader on the Enterprise CMDB. BMC intends to fix this problem in a future release.
Note: The name of the DSO import dataset for the Cloud is BMC.IMPORT.ENTERPRISE and
the DSO import dataset name for the Enterprise is BMC.IMPORT.CSM. SW00388154 When using the Continuous Merge feature of the Reconciliation Enginerunning a continuous Merge job in parallel with a ID batch jobsometimes a Merge operation shows end-point validation errors while processing relationships. Although there is no functional impact of these errors, you might experience slow performance when merging CIs.
Known issues
31
Atrium Integrator known issues

Table 1-3 describes the known issues in Atrium Integrator.
Table 1-3: Atrium Integrator known issues Issue SW00366596 Description While running multiple or parallel job using Pentaho Carte, make sure that the sum of all threads (number of copies) on CMDBOutPutPlugin step in a job does not exceed 100. Otherwise, you might see the following message: We have reached the max number proxies in the pool; wait for one to become available for thre ad Tid_91 for server prdswin01 Workaround: This is not an Atrium Integrator issue. By default, the number of connections (proxies) for BMC Atrium CMDB is set to 100 in the CMDB_Api.properties file. Make sure that sum of all threads (Number of copies) on CMDBOutPutPlugin step in a job does not exceed 100. For example, there is a job that consists of multiple transformations and these transformations use CMDB Plugins like Output.Lookup and Input. Make sure that the summation of Number of Copies does not exceed 100 for a such a job. SW00366612 When you set Minimal Logging in Atrium Integrator and you execute a successful job, the Spoon log file is not clear about the job status. Workaround: Use the NGIELOG table instead of Atrium Integrator logging in Spoon. SW00366809 While transferring data from a CSV file to any CI class using CMDB output, the primary key and data key are not updated with correct data. Workaround:
1 Open your transformation in Pentaho Spoon application. 2 Double-click the input step.
The input step dialog box appears.

3 Deselect the Lazy conversion check box. By default, the Lazy conversion check box is
selected. SW00370329 If you run the same job or transformation multiple times, Spoon might crash. Workaround: Change the JVM environment variable Xmx from 250 to 1024 in the following files: Windows: spoon.bat and carte.bat UNIX: spoon.sh and carte.sh SW00370870 While installing the Atrium Integrator server, if you already have a repository named AIntRepository in your database, you will not able to proceed with the installation. Workaround: With MS SQL Server, delete the database name and run the installer again. With Oracle, drop the tablespace, user, and roles, and then run the installer again.
32
Release Notes
Table 1-3: Atrium Integrator known issues (Continued) Issue SW00371511 Description When you right-click the CMDBOutput or CMDBLookUp step in Pentaho Spoon, the Generate Mapping menu which facilitates mapping between the Input step and the CMDBOutput (or CMDBLookUp) step does not always work as expected. Workaround: Double-click the CMDBOutput or CMDBLookUp steps instead to create the field or attribute mappings. SW00380328 If you use the Atrium Integrator Integration Job Builder wizard to transfer data from an XML source file that has multiple records, the wizard recognizes only the first root element and transfers only the first record. Workaround: Perform the following steps to transfer data from multiple rows.
1 Open the transformation in the Spoon. 2 Edit the Get XML step. 3 Go to the Content tab and click the GetXpathNodes button.
The Available paths dialog box appears.

4 Select the rows you need and click OK. 5 Go to the Fields tab and click Get Fields. 6 Click OK to save the changes.
SW00380329
The Integration Job Builder wizard does not support data transfer from an XML file that contains an embedded file. Example: If the first row of the XML file contains data in the following syntax, you will not be able to map the target attributes to any column: (<?xml version="1.0" ?> PULL_EMP_AR.xsd">) Workaround: Remove the tag that contains the embedded file name from the XML source file. <results xmlns="http://tempuri.org/
SW00380859 SW00380326
While creating a job (using the Integrator Job Builder wizard) to transfer data from an XML or CSV source file, if you plan to use the Delta transformation option, the date in these files should be in DD/MM/YYYY format. Workaround: Change the date format by editing the transformation in the Spoon. After generating the transformation or job through the Integrator Job Builder wizard, you can change the date format again.
Known issues
33
Table 1-3: Atrium Integrator known issues (Continued) Issue SW00382224 Description While editing mapping conditions of transformations in the Spoon, you might see error messages indicating that the fields from the previous steps could not be fetched. For example: Unable to get query fields for SQL: Select * from SOURCE_TABLENAME where LAST_MODIFIED_TIME > ? ORDER BY LAST_MODIFIED_TIME Workaround:
1 Open the table source. 2 Replace the question mark (?) in the query with blank value ( ). 3 Deselect the Replace variables in script check box. 4 Make sure the Insert data from step field is blank. 5 Click OK.
You can now edit the transformation. Make sure to revert the changes you made in the table source from step 1 to step 5 before saving the transformation. SW00382574 When you create a job to transfer data from a CSV file with Delta=No, the correct number of records are transferred to BMC Atrium CMDB. However, when you open the job in Spoon, the values in the Written and Output columns in the Execution History tab are incorrect. This is a known Spoon issue. Use the following explanation for the number of records displayed in Spoon: ReadNumber of rows coming from previous Steps WrittenNumber of rows leaving from this Step toward the next InputNumber of rows read from a file or table OutputNumber of rows written to a file or table SW00382597 SW00382760 While creating a job by using the Integrator Job Builder wizard, you cannot use special characters (\ / | : * " ? < >) in the job name. The Integration Job Builder wizard supports data transfer from CSV files with comma delimiters only. Workaround: If you want to use a different delimiter or file format other than CSV, create your own transformation for the file format by using the Spoon. SW00383183 In Atrium Integrator installed on Linux, jobs created from the Integration Job Builder wizard do not always run consistently at first. Jobs in Linux sometimes throw various errors and fail to complete. Workaround: Try running the job again. SW00383208 If you run a job twice, the login information is overwritten in the Pentaho Carte server log. This is a Pentaho limitation. Workaround: You can do any of the following: Use the Atrium Core UI to view Logs for the specific job Clear the job log history in the Spoon and rerun the transformation or job, and then view the log details.
34
Release Notes
Table 1-3: Atrium Integrator known issues (Continued) Issue SW00383223 Description When creating a job in Atrium Integrator, you sometimes cannot include a CI from the Available List of CI Types by selecting it and then clicking Add. Workaround: Double-click the CI Type instead to add it to the list. SW00383347 When creating a data store connection for XML or CSV by using the Integrator Job Builder wizard, only the source file path and the AR server connection are validated. The Integrator Job Builder wizard doesnt validate if the XML or CSV source file exists at the specified path. Make sure you place the file at the specified path before you create a job. When you create and run a job in Atrium Integrator and you do not properly map the Response datatype, you see the following error: Implicit conversion from datatype 'VARCHAR' to 'INT' is not allowed. Use the CONVERT function to run this query : sybase database Workaround: You must change the Response datatype in Spoon to the INT datatype (because zero is the String datatype). You can then run the job successfully. SW00386432 In Atrium Integrator, you sometimes see the Start Job icon still enabled even while you are running a job. The Stop Job icon should be enabled and the Start Job icon should be disabled while jobs are running. You typically see this problem when you create jobs with a schedule attached. When you start a job in Atrium Integrator using the Scheduler and that job is scheduled to run at 10 minutes, if the job actually takes more time to run (due to the amount of data in the Source data store), then the Scheduler continues to keep it continuously running even after 10 minutes. As a result, you lose track of which job history to monitor. Workaround: If you have a large amount of data to transfer, make sure that you schedule enough time for your job to finish before running the next job. SW00386493 When accessing Atrium Integrator on HP-UX or AIX systems through the BMC Remedy Mid Tier, the Atrium Integrator icon is enabled even when Atrium Integrator is not installed. If you try to access Atrium Integrator, an error appears. If you create a job with mysql adapter from the wizard in Atrium Integrator and you try to map a user tablespace as the source table but cannot map its columns, you return errors in the log. Workaround: Do not map the tables under the User Tablespaces. You cannot retrieve column data from these tables.
SW00385677
SW00386434
SW00386504
Known issues
35
Table 1-3: Atrium Integrator known issues (Continued) Issue SW00387278 SW00388046 Description If you change the AR System password or server ports after installing Atrium Integrator, you cannot select a dataset ID for creating a job or running an existing job. The relationship for the CIs you selected on the CI Type Selection page of the Integration Job Builder does not appear on the CI TypeRelationships page. Workaround: Create a relationship by performing the following steps.
1 In BMC Remedy User, open the CMDB:DataModelReference_RelationshipName
form in New mode. 2 Enter the required information to create the relationship. The relationship now appears on the CI TypeRelationships page.
Updating the WSDL and EPR links in the UDDI Registry to display the HTTPS port
Although you configured the web services port to HTTP by using the atriumws utility, the WSDL and EPR links in the UDDI Registry display the HTTPS port. To work around this issue, you must manually replace the HTTPS port with the HTTP port in the UDDI Registry.
To update the WSDL and EPR links in the UDDI Registry on Windows
1 On the system where Web Services Registry is installed, open a command prompt
window.
2 Enter the following command: cd %ATRIUMCORE_HOME%\wsc\wsregistryapi 3 Enter the following command to set the CLASSPATH variable: SET CLASSPATH=WSRegistryAPI7.604.jar;lib/tibco-uddiclient3.0.jar;lib/activation.jar 4 Enter the following command to delete the incorrect WSDL and EPR links from the
UDDI Registry:
java -cp %CLASSPATH% com.bmc.webservices.uddiapi.test.UDDIRegistryInstallUtil deleteaccesspts localhost <UDDI_PORT> <UDDI_USER> <UDDI_PASSWD> .\webservices_list_template.xml 5 Open the webservices_list_template.xml file and apply the following
changes:
a Replace all instances of https with http. b For each service, replace the HTTPS port number with the HTTP port number
in the EPR and WSDL URL links.
36
Release Notes
6 Enter the following command to add the correct WSDL and EPR links in the UDDI
Registry:
java -cp %CLASSPATH% com.bmc.webservices.uddiapi.test.UDDIRegistryInstallUtil publish localhost <UDDI_PORT> <UDDI_USER> <UDDI_PASSWD> .\webservices_list_template.xml
To update the WSDL and EPR links in the UDDI Registry on UNIX or Linux
1 On the system where Web Services Registry is installed, open a shell window. 2 Enter the following command: cd $ATRIUMCORE_HOME/wsc/wsregistryapi 3 Enter the following command to set the CLASSPATH variable: export CLASSPATH=WSRegistryAPI7.604.jar:lib/tibco-uddiclient3.0.jar:lib/activation.jar 4 Enter the following command to delete the incorrect WSDL and EPR links from the
UDDI Registry:
java -cp $CLASSPATH com.bmc.webservices.uddiapi.test.UDDIRegistryInstallUtil deleteaccesspts localhost <UDDI_PORT> <UDDI_USER> <UDDI_PASSWD> ./ webservices_list_template.xml 5 Open the webservices_list_template.xml file and apply the following
changes:
a Replace all instances of https with http. b For each service, replace the HTTPS port number with the HTTP port number
in the EPR and WSDL URL links.

6 Enter the following command to add the correct WSDL and EPR links in the UDDI
Registry:
java -cp $CLASSPATH com.bmc.webservices.uddiapi.test.UDDIRegistryInstallUtil publish localhost <UDDI_PORT> <UDDI_USER> <UDDI_PASSWD> ./ webservices_list_template.xml
Updating the WSDL and EPR links in the UDDI Registry to display the HTTPS port
37
Localized versions
Localized versions of BMC Atrium Core components are available in the following languages: English French German Italian Japanese Korean Simplified Chinese Russian Spanish Brazilian Portuguese
NOTE
BMC Atrium Integration Engine and BMC Atrium Core 7.6.04 online help are only offered in English.
Support information
To get the latest documentation, product, or support information, review the following sections.
BMC Atrium Core documentation

This section describes the complete set of BMC Atrium Core documentation, including manuals, help systems, videos, and so on. Unless otherwise noted, documentation is available free of charge on the BMC Atrium Core documentation media (DVD or Electronic Product Download bundle) and on the BMC Customer Support site, at http://www.bmc.com/ support.
38
Release Notes
To find this documentation on the BMC Customer Support site, choose Product Documentation > Supported Product A-Z List > BMC Atrium CMDB Enterprise Manager >7.6.04.
Title Atrium Integrator 7.6.04 User's Guide Description Information about defining source and target connections, creating jobs and transformations, editing and monitoring jobs, and other Atrium Integrator concepts. Audience Users who are responsible for setting up data transfer integrations between external data stores and BMC Atrium CMDB.
BMC Atrium CMDB 7.6.04 Information about setting permissions, configuring Configuration managers, Administrator's Guide federation, modifying the data model, configuring application administrators, an impact model, and other administrative tasks in and asset analysts. BMC Atrium Configuration Management Database (BMC Atrium CMDB). BMC Atrium CMDB 7.6.04 Hierarchical diagram of all classes in the Common Configuration managers, Common Data Model Data Model (CDM), including unique attributes and application administrators, Diagram applicable relationships. and asset analysts. BMC Atrium CMDB 7.6.04 Data Model Help Description and details of superclasses, subclasses, attributes, and relationship classes for each class. Contains only information about the CDM at first, but you can update it to include information about data model extensions that you install.
Note: This Help is provided in HTML and is available
Configuration managers, application administrators, and asset analysts.
on the BMC Atrium Core media. It is not available on the BMC Customer Support site. Configuration managers, BMC Atrium CMDB 7.6.04 Best practices for using the classes that BMC application administrators, Data Modeling Guide provides for BMC Atrium CMDB (both the CDM and extensions) to model complex business entities, and asset analysts. focusing on the use of multiple related CIs to model an entity rather than on general information about a class or attribute. BMC Atrium CMDB 7.6.04 Javadoc Help Information about Oracle Java classes, methods, and Application programmers. variables that integrate with BMC Atrium CMDB.
on the BMC Atrium Core media. It is not available on the BMC Customer Support site. BMC Atrium CMDB 7.6.04 Information about normalizing data in BMC Atrium Configuration managers, Normalization and CMDB and reconciling CIs from different data application administrators, Reconciliation Guide providers into a single production dataset. and asset analysts. BMC Atrium CMDB 7.6.04 Online Help Help for using and configuring BMC Atrium CMDB, including Atrium Integrator, BMC Atrium Product Catalog, Reconciliation Engine, Normalization Engine, and so on. Configuration managers, application administrators, asset analysts, and users that work with CIs and need to understand the Note: This Help is provided in HTML and is available relationships that exist through the Help links in the BMC Atrium CMDB within BMC Atrium CMDB. user interface. It is not available on the BMC Customer Support site.
Support information
39
Title
Description
Audience Users that work with CIs and need to understand the relationships that exist within BMC Atrium CMDB. Configuration managers, application administrators, and asset analysts.
BMC Atrium CMDB 7.6.04 Information about using BMC Atrium CMDB, User's Guide including searching for and comparing CIs and relationships, relating CIs, viewing history, running impact simulations, and viewing federated data. BMC Atrium Core: Taking Your Data Into Production End to End End-to-end high-level steps for bringing data into BMC Atrium CMDB from a third-party source and making it available in your production dataset.
Note: This Flash video is available on the BMC
Atrium Core media. It is not available on the BMC Customer Support site. BMC Atrium Core 7.6.04 Compatibility Matrix Information about the BMC Atrium Core configurations that are expected to work together based on design, testing, or general understanding of the interaction between products.
Note: Download the BMC Atrium Core 7.6.04
Configuration managers, application administrators, and asset analysts.
Compatibility Matrix from the BMC Customer Support site at http://www.bmc.com/ support/reg/remedy-compatibilitytables.html?c=n. BMC Atrium Core 7.6.04 Concepts and Planning Guide Information about CMDB concepts and high-level steps for planning and implementing BMC Atrium Core. Anyone who wants to learn about and understand BMC Atrium Core products, CMDBs in general, and the functionality of BMC Atrium CMDB in particular. IT leaders, configuration managers, application administrators, and asset analysts are some who will benefit from this information. BMC Atrium Core 7.6.04 Information about creating API programs using C Developers Reference Guide API functions and data structures. BMC Atrium Core 7.6.04 Installation Guide BMC Atrium Core 7.6.04 Master Index BMC Atrium Core 7.6.04 Product Catalog and DML Guide Information about installing, upgrading, and uninstalling BMC Atrium Core features. Combined index of all guides. Application administrators and programmers. Application administrators. Everyone.
Information about configuring the Product Catalog System administrators, IT and DML, adding products, and creating aliases for managers, network products, manufacturers, and categorizations. managers, and other qualified personnel who are familiar with their computing and networking environment. Information about new features, known issues, and Everyone. other late-breaking topics.
BMC Atrium Core 7.6.04 Release Notes
40
Release Notes
Title BMC Atrium Core 7.6.04 Troubleshooting Guide BMC Atrium Core 7.6.04 Web Services Help
Description
Audience
Information about resolving issues with BMC Application administrators, Atrium Core components, including API, filter, and programmers, and BMC Support personnel. console error messages and their solutions. Application administrators Information about using BMC Atrium Core Web and programmers. Services, including how to publish and find interfaces in the Web Services Registry, set versions, disambiguate web services, configure security policies and encryption, and use BMC Atrium Core Web Services data structures and operations.
on the BMC Atrium Core media. It is not available on the BMC Customer Support site. BMC Atrium Integration Engine 7.6.04 ADK Developer's Guide Information about how to build adapters that can transfer information between an external data store and either BMC Remedy AR System forms or BMC Atrium CMDB. Developers who have a basic understanding of BMC Atrium Integration Engine and want to build adapters that can exchange data between two data sources.
BMC Atrium Integration Help for using and configuring BMC Atrium Engine 7.6.04 Online Help Integration Engine.
Users who are responsible for setting up data transfer integrations between Note: This Help is provided in HTML and is available external data stores and through the Help links in the BMC Atrium either BMC Atrium CMDB Integration Engine user interface. It is not or BMC Remedy available on the BMC Customer Support site. AR System. Users who are responsible for setting up data transfer integrations between external data stores and either BMC Atrium CMDB or BMC Remedy AR System. Configuration managers, application administrators, and asset analysts.
BMC Atrium Integration Information about creating data exchanges and data Engine 7.6.04 User's Guide mappings, defining rules and queries, activating event-driven data exchanges, defining connection settings, and other BMC Atrium Integration Engine concepts.
Mapping Your Data to Spreadsheet that maps common IT objects to the BMC Atrium CMDB 7.6.04 appropriate class, whether part of the CDM or an Classes extension. This spreadsheet also includes information about further categorizing instances using key attributes, and best practices for creating normalized relationships.
Support information
41
Searching PDF documents

If you have Adobe Acrobat version 6.0 or later, you can search for text within all of the PDFs that are in the same folder. You do not need to open the files before running your search. To upgrade your version of Adobe Acrobat, go to http://www.adobe.com.
To search PDF documents in a specific location

1 Copy the BMC Atrium Core PDF files to a folder. 2 Open Adobe Acrobat. 3 Choose Edit > Search. 4 In the Search PDF pane, type the word or phrase to search for. 5 Select the All PDF Documents in option and browse to the folder containing the
PDF files for BMC Atrium Core.

6 Click Search. 7 In the Results window, click a document.
The document opens at the first occurrence of the search term.

8 To navigate to other occurrences of the search term within the document, click a
link under the document name. To navigate to occurrences in other documents, click the plus (+) symbol to the left of a document name.
Where to get the latest product information

To view the latest BMC documents, see the Customer Support website at http://www.bmc.com/support. Notices, such as flashes, technical bulletins, and release notes, are available on the website. You can subscribe to proactive alerts to receive e-mail messages when notices are issued or updated. For more information about proactive alerts, see the Customer Support website.
Customer support information

If you have problems with or questions about a BMC product, or for the latest support policies, see the Customer Support website at http://www.bmc.com/ support. You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 1 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.
42
*087671* *087671* *087671* *087671*
*176780*

Release Notes: BMC Atrium Core 7.6.04

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Release Notes: BMC Atrium Core 7.6.04

Diunggah oleh

Hak Cipta:

Format Tersedia

BMC Atrium Core 7.6.

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or email

Before contacting BMC Software

License key and password information

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

Atrium Service Catalog

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

Common Data Model

BMC Atrium Core 7.6.04

BMC_ServiceOffering BMC_RequestableOffering BMC_ServiceOfferingInstance

Not applicable Not applicable BMC_BaseElement

BMC_Option BMC_OptionChoice BMC_FinancialElement BMC_Cost BMC_Price

BMC_ComputerSystem BMC_IPEndpoint BMC_ApplicationSystem BMC_BaseRelationship BMC_HostedAccessPoint

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

Figure 1-4: Manage Products Console in Product Catalog

BMC Atrium Core 7.6.04

Approved and Unmanaged

Unapproved and Managed

Unapproved and Unmanaged

BMC Atrium Core 7.6.04

Software license management

BMC Atrium Core 7.6.04

Installing BMC Atrium Core online help

BMC Atrium Core 7.6.04

BMC Atrium Core known issues

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

the BMC_ComputerSystem class is BMC.CORE:BMC_ComputerSystem.

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

folder to another location.

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

/opt/bmc/ARSystem entry in the armonitor.cfg file.

BMC Atrium Core 7.6.04

C:\Program Files\BMC Software\AtriumCore_New

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

Atrium Integrator known issues

The input step dialog box appears.

BMC Atrium Core 7.6.04

The Available paths dialog box appears.

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

BMC Atrium Core 7.6.04

in the EPR and WSDL URL links.

BMC Atrium Core 7.6.04

087671 087671 087671 087671