NRX Asset Hub 4.6.

15 Release Notes

Document Version: 4.6.15

Document Date: May 2009

NRX Global Corp. 150 York Steet 14th Floor Toronto, Ontario Canada M5H 3S5
Telephone : 416.368.4567 Fax Toll Free : 416.368.9844 : 877.603.4679

Copyright
Copyright 2009 NRX Global Corp. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of NRX Global Corp. The information contained herein may be changed without prior notice. Some software products marketed by NRX Global Corp. and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

www.nrx.com

NRX, VIP, and Asset Hub are trade marks or registered trade marks of NRX Global Corp. HP-UX is a registered trademark of Hewlett-Packard Company. JAVA is a registered trademark of Sun Microsystems, Inc. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, SAP Enterprise Portal and SAP Web Application Server are trademarks or registered trademarks of SAP AG in Germany and in several other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

Typographic Conventions
Type Style Example Text Represents Words or characters that appear on the screen. These include field names, screen titles, and pushbuttons, as well as menu names, paths, and options. Cross-references to other documentation Example text Emphasized words or phrases in body text, titles of graphics, and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code, as well as names of installation, upgrade, and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the Strg key.

Icons
Icon Meaning Caution Example Note Recommendation Syntax

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

NRX Asset Hub 4.6 Release Notes Table of Contents

Table of Contents
1 History of New Features ................................................................................. 6
1.1 Corrections and Enhancements in Asset Hub 4.6.14....................................................6 1.2 Corrections and Enhancements in Asset Hub 4.6.13....................................................6 1.3 Corrections and Enhancements in Asset Hub 4.6.12....................................................6 1.4 Corrections and Enhancements in Asset Hub 4.6.11....................................................6 1.5 Corrections and Enhancements in Asset Hub 4.6.10....................................................7 1.6 Corrections and Enhancements in Asset Hub 4.6.9......................................................7 1.7 Corrections and Enhancements in Asset Hub 4.6.8......................................................7 1.8 Corrections and Enhancements in Asset Hub 4.6.7......................................................7 1.9 Corrections and Enhancements in Asset Hub 4.6.6......................................................8 1.10 Corrections and Enhancements in Asset Hub 4.6.5......................................................8 1.11 Corrections and Enhancements in Asset Hub 4.6.4......................................................8 1.12 Corrections and Enhancements in Asset Hub 4.6.3......................................................9 1.13 Corrections and Enhancements in Asset Hub 4.6.2......................................................9 1.14 New Features in Asset Hub 4.6.1.....................................................................................9 1.15 New Features in Asset Hub 4.6......................................................................................10 1.16 New Features in Asset Hub 4.5.2...................................................................................10 1.17 New Features in Asset Hub 4.5.1...................................................................................10 1.18 New Features in Asset Hub 4.5......................................................................................11 1.19 New Features in Asset Hub 4.1......................................................................................11 1.20 New Features in Asset Hub 4.0......................................................................................11

2 Known Issues ................................................................................................ 11

2.1 Asset Hub Synchronization ...........................................................................................11 2.1.1 Problems during synchronization after upgrade to Asset Hub 4.6 .................11 2.1.2 Measuring Points: Annual Estimate field ...........................................................12 2.1.3 Synchronizing related objects in Realtime mode..............................................12 2.1.4 Synchronization of Task Lists into R/3/ERP ......................................................12 2.1.5 Multiple counter Maintenance plan.....................................................................12 2.1.6 Equipment Synchronization from Asset Hub to R/3 .........................................12 2.1.7 Creating Plants and Warehouses in Asset Hub ................................................12 2.1.8 Synchronization of Global BOMs........................................................................12 2.1.9 Creating or Changing Functional Locations......................................................13 2.1.10 Synchronization of Material from Asset Hub to R/3..........................................13 2.1.11 Material Synchronization from Asset Hub to R/3 ..............................................13 2.1.12 Numeric Values Sent in Attributes to R/3...........................................................13 2.1.13 Loading Data Dictionary ......................................................................................13 2.1.14 Synchronization of BOMs from R/3 to Asset Hub (Recursive BOMs).............13 2.1.15 Synchronization of BOMs from Asset Hub to R/3 (Empty BOMs) ...................13 2.1.16 Duplicate BOM items in the same BOM..............................................................14 2.1.17 Material Filter in Mat. Extractor from R/3 to Asset Hub ....................................14 2.1.18 Filters for Material Extractors/Delta Sync from R/3 to Asset Hub ...................14

May 2009

NRX Asset Hub 4.6 Release Notes Table of Contents

2.1.19 Changes to BOMs via Plant Assignment ...........................................................14 2.1.20 Real time Sync of Newly Created Multi-Level Tree ...........................................14 2.1.21 Maintenance Planning Plant and maintenance plan. ........................................14 2.1.22 Measuring Point has a Logical Connection to Maintenance Planning Plant..14 2.1.23 Initial Sync Programs vs. Direct 'Pull' Functionality in Asset Hub..................14 2.1.24 Problem with Direct Download of Maintenance Procedures ...........................15 2.1.25 Order of Objects Processing ...............................................................................15 2.2 Support for Exporting Report Results to PDF..............................................................15 2.3 MDM ..................................................................................................................................15

3 Ability to Turn off Lucene Database Backup on the Single-Server Setup 15 4 Additional Configuration Required When Using the Asset Hub Auditors
Deployed on SAP Web Application Server. ................................................ 16

May 2009

NRX Asset Hub 4.6 Release Notes

Note: The software and documentation for NRX Asset Hub 4.x is available in the English language only.

1 History of New Features 1.1 Corrections and Enhancements in Asset Hub 4.6.15
Submission back to Passport MR failed if any material added to the material list had a blank part number. Warehouse location removed from CAT ID did not get removed in Asset Hub after synchronization

1.2 Corrections and Enhancements in Asset Hub 4.6.14

Bug fix: BOMs fail to synchronize under certain circumstances. Bug fix: Maintenance plan XML failed to import.

1.3 Corrections and Enhancements in Asset Hub 4.6.13

BOMs were not appearing in Create Work Order mode under certain circumstances (VIP) Moving equipment in PassPort could leave orphaned items. Some SKU matches made in Manager were not displayed in Viewer

1.4 Corrections and Enhancements in Asset Hub 4.6.12

Reintroduced support for SAP R/3 4.6c SAP Synchronization: added configuration setting to allow imported XMLs to be split into several synchronization sessions to improve performance Increased the default size for the Pick List Summary dialog Corrected certain cases when users were getting Java heap errors while hotpointing books Bug fix: In the Book Editor, changing a table of contents name without making other changes resulted in the change not being saved properly.

1.5 Corrections and Enhancements in Asset Hub 4.6.11

User was unable to search Materials Filtered by the Warehouse if site permission was set to Viewer access only Corrected issue assigning material to warehouse from material properties (list of warehouses was not available) Inbound Session state still displayed "Has Conflict" instead of "Successful" after the session was resolved. Fixed issues with editing material classification after material is synchronized from SAP

May 2009

NRX Asset Hub 4.6 Release Notes

Improved speed of creating hyperlinks in parts books Classification values for a material were modifiable for synchronized materials regardless of restrictions Corrected issue with disappearing material list when Count Result button clicked in the material filter Child Equipment Type disconnects from the equipment type hierarchy after synching an equipment assigned to that child equipment type from SAP

1.6 Corrections and Enhancements in Asset Hub 4.6.10

Indexes are now stored in compressed form to reduce the file size. Importing manufacturers into a data repository may fail resulting in a "duplicate vendor" error in some situations. The material id was not set properly for BOM materials with item category "S". Fix for Indus Passport Material Request direct navigation to handle the case where the user has access to multiple facilities in Passport. Fix for Indus Passport Material Request direct navigation to be able to locate equipment by E-CODE Fix for Indus Passport Material Request to handle assets that are not attached to functional locations. Navigation to the lowest level functional location is done instead. Advanced find for functional location ERP codes containing spaces was not working ERP Synchronization stopped processing pending sessions in some cases when indexing was ran during synchronization SKUs were not being displayed in parts books if materials were detached from site prior to SKU matching

1.7 Corrections and Enhancements in Asset Hub 4.6.9

Validation of mandatory properties in the Book Editor didn't work after the validation error link was clicked. Parts books failed to publish if a parts list with extended columns was imported via a text file. Summary view for BOMs with lots of line items didn't display properly. The BOM line items are now truncated at 100. Couldn't create a content type with the same name as a deleted content type. Note that the fix does not apply to content types deleted before this patch release.

1.8 Corrections and Enhancements in Asset Hub 4.6.8

Fixed problems with manufacturer and attribute merge during synchronization of assets

1.9 Corrections and Enhancements in Asset Hub 4.6.7

Enhancement: Appended the item long text to the material description for BOM line items

May 2009

NRX Asset Hub 4.6 Release Notes

Enhancement: The FROM field when emailing a material list from the Viewer is now read-only and automatically prepopulated with the logged in user's email address. Synchronization fails when previously synched object has been deleted and then manually recreated with the same ERP code Creating SQL report templates with parameters didn't work.

1.10 Corrections and Enhancements in Asset Hub 4.6.6

Bill of Material line items for materials display the long text for the item as part of the description.

1.11 Corrections and Enhancements in Asset Hub 4.6.5

Asset Hub Manager could lock up when sorting on the "Storage Bin" column in the materials list. Synchronizing from Passport could cause exceptions on Asset Hub Server. BOM synchronization conflicts could not be resolved. Synchronizing functional locations could incorrectly report conflicts. Exception could occur when resolving a conflict for a functional location with no parent. Flagging a material for deletion at plant level in SAP and synchronizing to Asset Hub did not work. Exception occurs when viewing an asset with a BOM attached after synchronizing from Passport. Asset Hub Viewer could lock up with previewing a multi-page material list with summary option selected. Could not delete a tool from an operation in Maintenance Procedure properties. Could not "Add Material" or "Add Tool" to an operation in a maintenance procedure before specifying all mandatory fields. Asset Properties button in maintenance procedures for Equipment Types did not work. Exception occurs if user adds a tool to a maintenance procedure if no asset tools are available Books containing attachments referenced by https were not displayed

1.12 Corrections and Enhancements in Asset Hub 4.6.4

Some photo book thumbnails were not being displayed correctly with Asset Hub manager client running Java 1.4.2_13 or older.

May 2009

NRX Asset Hub 4.6 Release Notes

Modifying the address for a contact caused the address to be duplicated. Asset Hub Manager could lock up when books were being published while large asset trees were open. Sync session failed when assets were synchronized before BOMs from Indus Passport. Sync session failed when synchronizing certain BOMs from Indus Passport. Workflow task could not be set for a large number of materials . "Storage Bin" column in the materials table was not sorted properly. Importing data retrieved from Excel template through Collaboration failed under certain circumstances. Updated upgrade script from ACM 3.7.1 to Asset Hub 4.0 - issue with outbound SAP synchronization. Multiple Collaboration request items were created even though option was selected for a single request item.

1.13 Corrections and Enhancements in Asset Hub 4.6.3

Fixed issue with warehouses not being linked to enterprise when they are being created during the material synchronization Fixed issue with incorrect interpretation of space character following ampersand in functional location names during passport synchronization Corrected Passport synchronization issue with functional location bills of materials synchronization (updated ClearSiteTree report) Corrected issue with filtering enterprise materials when multiple criteria is used Reimporting material list multiple times was causing duplicate info to appear on material summary page Sorting Material list by Storage Bin column was not sorting properly

1.14 Corrections and Enhancements in Asset Hub 4.6.2

Adding Saved Text to the description in Maintenance Procedures overwrote part of the existing description. Deleting the text description of the maintenance procedure was not always deleting the old text completely Enhancement: Appended the asset tag to the name in the asset tree launched from the "For" field in the Maintenance Plans properties dialog.

1.15 New Features in Asset Hub 4.6.1

Asset Hub 4.6.1 contains minor changes needed to support integration with VIP 4.0

May 2009

NRX Asset Hub 4.6 Release Notes

Upgrading Asset Hub from earlier versions: no upgrade .sql scripts are needed to upgrade Asset Hub database from 4.6 to 4.6.1. However, if you are running a version of Asset Hub lower than 4.6, please run all .sql scripts from your version up to upgrade_4.5.2.0_to_4.6.0.0.sql. For example, if your ACM server is currently ACM 3.7 and you want to upgrade it to Asset Hub 4.6.1, you must run all seven .sql files, from upgrade_3.7.0.0_to_3.7.1.0.sql to upgrade_4.5.2.0_to_4.6.0.0.sql inclusive

1.16 New Features in Asset Hub 4.6

Support for strategy-based maintenance plans and task lists Support for production resource tools Support for sub-operations for maintenance procedures/task lists "Annual estimate" field for measuring points Option to copy associated maintenance objects when copying and pasting assets Ability to define Standard Text that can be inserted into Maintenance Procedure Description, or Operation Description in Maintenance Procedures Support for default value for book properties Support for customizable pick lists for book properties Improve the branding mechanism for Collaboration Portal Support for multiple asset trees Media packages and work packages moved to Enterprise level Material search moved to Advanced search screen in Viewer Additional filtering capabilities for assets Ability to get a count of the results passing an asset or material filter before running the filter

1.17 New Features in Asset Hub 4.5.2

Ability to apply approval codes to files associated with collaboration request items. Site and warehouse management views now located at the Enterprise level (moved from System level). Support for the synchronization of users from multiple Active Directory servers. Ability to specify contact information and address details for users. Ability to customize copied assets from data repositories. Ability to import partners via XML.

1.18 New Features in Asset Hub 4.5.1

Ability to specify optional due date when creating collaboration requests. Ability to map collaboration request item data templates to equipment classifications compressors, motors or pumps, for example. This facilitates the creation of requests by pre-populating the appropriate template when users select a request item type. Ability to associate assets with collaboration request items. Support for mandatory book properties. Pagination support in the Collaboration Portal. Ability for logged-in users to view all requests in the Collaboration Portal, with which they are actively involved (not just those assigned to them). Online Help available in the Collaboration Portal.

May 2009

10

NRX Asset Hub 4.6 Release Notes

1.19 New Features in Asset Hub 4.5

Ability to manage asset data by equipment classifications Support for maintenance programs Support for Active Directory user synchronization Ability to import master data in standard ISO 15926 format Support for hierarchical equipment types Indus Passport Synchronization enhancements Improved Documentum support Improved robustness of EAM synchronization Microsoft Internet Explorer 7 support SAP Web Application Server 7.0 SP9 (part of SAP NetWeaver 2004s) support Various usability enhancements

1.20 New Features in Asset Hub 4.1

Added MS SQL support Added SAP ECC 6.0 support Added support for integration with SAP MDM Added ability to import master data via XML files received via collaborative data exchange Added ability to reference existing Document Management System files from the Asset Hub Book Editor Ability to add a data translator to collaboration templates Asset Hub Indus Passport Synchronization: Added data dictionary, site and warehouse download functionality Location attributes made available in the Viewer Added custom branding support for Collaboration Portal Added ability to sort by columns in request list in the Collaboration Portal

1.21 New Features in Asset Hub 4.0

Generic Mapping Utility to map Asset Hub Data Objects to content and or data residing in external systems External Workflow Integration Collaborative Data Exchange External System Connections for Data Extraction and Transformation Added ability to perform filters for flags NOT set in Tasks Made alert types dynamically configurable

2 Known Issues 2.1 Asset Hub Synchronization

2.1.1 Problems during synchronization after upgrade to Asset Hub 4.6
The note below is required for customers who are planning on upgrading to Asset Hub 4.6. This correction is applicable to synchronization. Please review OSS NOTE 1097017: NRX: Equipment, Floc and Measuring Pointes Change Pointers and follow the correction instructions as described.

May 2009

11

NRX Asset Hub 4.6 Release Notes

2.1.2 Measuring Points: Annual Estimate field

It is possible for scientific notation values to be displayed for measuring points in Asset Hub. This is due to a conversion to scientific notation which can occur occasionally in the IDoc. Also note that backend EAM/SAP systems may sometimes round measuring point values they receive from Asset Hub. When they send these rounded values back to Asset Hub, they conflict with the Asset Hub measuring point values.

2.1.3 Synchronizing related objects in Realtime mode

When sending related objects from Asset Hub to SAP in Realtime mode, it is important that all related object types are set as Realtime in the /nrx/46sync_conf table. Otherwise, some data will go to the staging tables for SAPLOAD while other data will attempt to synchronize immediately. For example, if you set your equipment to Realtime, and your classes to Manual, then attempt to synchronize them simultaneously using Synchronize related objects, the equipment will attempt to synchronize immediately, but the Classes will go to the staging tables.

2.1.4 Synchronization of Task Lists into R/3/ERP

Sub-operations added to maintenance procedure in AH are not shown in task list in R/3. There is an OSS note fix for this, note number not known at time of publication.

2.1.5 Multiple counter Maintenance plan

Multiple counter Maintenance plan created in Asset Hub is shown as Single cycle in R/3 after synchronization.

2.1.6 Equipment Synchronization from Asset Hub to R/3

In Asset Hub synchronization, there is a known issue that sub-equipment always inherits attributes from the parent equipment, whether the inheritance flag is set or not. In future release it will be possible to override this with the inheritance flag on the SAPLOAD selection screen or the user parameter /NRX/EQUIP_ORIGIN for Realtime.

2.1.7 Creating Plants and Warehouses in Asset Hub

Plants and warehouses are downloaded from R/3 into Asset Hub. Plants are downloaded from the System page in VIP and warehouses are downloaded with the data dictionary. It is possible to create new plants and warehouses in Asset Hub, but this makes it possible for a plant or warehousethat does not exist in R/3to be attached to Asset Hub objects and sent to R/3. Because the plant or warehouse does not exist in the R/3 configuration, an error occurs in R/3 in this situation.

2.1.8 Synchronization of Global BOMs

There is no support for the outbound synchronization of global BOMs from Asset Hub to R/3. This means that a BOM created in Asset Hub at the enterprise level, cannot be synchronized back to R/3. The synchronization of global BOMs from R/3 to Asset Hub is also not supported.

May 2009

12

NRX Asset Hub 4.6 Release Notes

2.1.9 Creating or Changing Functional Locations

Be cautious when creating or changing functional locations in Asset Hub. When synchronizing functional locations from R/3 to Asset Hub, it is currently possible to send a different structure indicator to that sent from R/3, or to send an invalid one when creating a new functional location in Asset Hub. You must be certain the correct structure indicator is filled in Asset Hub. In a future release, R/3 will check this and send an appropriate message back.

2.1.10

Synchronization of Material from Asset Hub to R/3

When creating a new material item at the enterprise level in Asset Hub, it is not linked to a plant, and as a result, cannot be synchronized to R/3. This synchronization may be supported in a future release. The same is true for synchronization from R/3 to Asset Hub. If a material item is not an assembly, and it is not liked to any plant in R/3, it cannot be synchronized to Asset Hub

2.1.11

Material Synchronization from Asset Hub to R/3

There is no support for changing material type when editing an existing material item in Asset Hub. When a material item is created in R/3, it depends on the material type. Because of this dependence, changing the type later does not make sense.

2.1.12

Numeric Values Sent in Attributes to R/3

Numeric values entered as ERP attributes must adhere to the convention, which requires they be the default of the R/3 user used to connect Asset Hub to R/3 (in SU01).

2.1.13

Loading Data Dictionary

When loading the data dictionary from an XML file, you must ensure the XML is from the correct client, and that it matches data already in Asset Hub. Otherwise, when data is sent to R/3 with these attributes, R/3 may return errors such as Data Inconsistent, and it may appear that there is a configuration problem in R/3, which is not the case. The same applies to downloading the data dictionary directly. You must ensure the R/3 client connection is correct.

2.1.14 Synchronization of BOMs from R/3 to Asset Hub (Recursive BOMs)

Note that the total number of BOMs shown in the status bar at the bottom of the VIP application window as BOMs are being processed may differ slightly from the final number of BOMs actually sent to Asset Hub. This is because recursive BOMs are not supported in this release, and therefore they are ignored. This is true both when synchronizing data from R/3 to Asset Hub, and when synchronizing from Asset Hub to R/3.

2.1.15 Synchronization of BOMs from Asset Hub to R/3 (Empty BOMs)

Sending a BOM with no line items from Asset Hub to R/3 is not supported in this release

May 2009

13

NRX Asset Hub 4.6 Release Notes

2.1.16 2.1.17 2.1.18 Hub

Duplicate BOM items in the same BOM Material Filter in Mat. Extractor from R/3 to Asset Hub Filters for Material Extractors/Delta Sync from R/3 to Asset

Synchronization of Duplicate BOM items in the same BOM are not supported.

Only one filter group supported in this release (in the ALE distribution model) for the material filter

During the synchronization of materials from R/3 to Asset Hub (initial and delta), the Plant filter works such that there needs to be a blank entry in the Plant filter group if the customer makes use of IBAUs (assemblies). Because IBAUs are not connected to any plant, this is the only way to send IBAU materials to Asset Hub. You should also ensure that there is only one filter group for material.

2.1.19

Changes to BOMs via Plant Assignment

Changes to BOMs via plant assignment are not captured as changes and therefore they are not sent to Asset Hub.

2.1.20

Real time Sync of Newly Created Multi-Level Tree

Real time Synchronization of Newly Created Multi-Level Tree Branch Tree is not Supported Workaround: Repeat sending the whole branch as many times as many levels it contains Or Use manual outbound sync

2.1.21

Maintenance Planning Plant and maintenance plan.

The Maintenance Planning plant for all items must be the same within a maintenance plan. Asset Hub does not support maintenance plans where items are linked to multiple Maintenance Planning Plants.

2.1.22 Measuring Point has a Logical Connection to Maintenance Planning Plant

Because of previous note, we can make an association between a measuring point for a maintenance plan, and the plant to which the reference object (Functional Location or Equipment) is linked. This is seen in Asset Hub as the Plant for the Measuring point, hence Measuring Point is at the Plant/Site level.

2.1.23 Hub

Initial Sync Programs vs. Direct 'Pull' Functionality in Asset

In the case of large datasets to be initially synchronized from R/3, NRX recommends that the Initial Synchronization programs /NRX/AH45_INIT* be used (in background jobs),

May 2009

14

NRX Asset Hub 4.6 Release Notes

and Not the Direct 'Pull' from Asset Hub, for performance reasons.

2.1.24

Problem with Direct Download of Maintenance Procedures

When pulling down maintenance procedures from R/3 into Asset Hub, components and the unit of measure are not pulled down. Please use the Initial Sync program /NRX/AH45_INIT_TASKLIST for the initial synchronization of Maintenance Procedures.

2.1.25

Order of Objects Processing

Due to complexities in tracking newly created objects, it is recommended that each type of object be processed separately. That is, before processing the next type of object in SAPLOAD you must refresh the object data from Asset Hub. For example, if you create a new BOM with new materials you must process the materials first, (re-)sync the BOM, and then process the BOM. Please refer to the configuration guide for the order in which to process the objects.

2.2 Support for Exporting Report Results to PDF

When Asset Hub is deployed to an Oracle Application Server using SUN JDK 1.5, there is no support for exporting Asset Hub report results as pdf files.

2.3 MDM
The data extractors for equipment and material produce IDocs in XML format. The program messages indicate that these are initial syncs to Asset Hub. Despite this message, the XMLs that are produced are valid for the MDM repositories for equipment and material as well.

3 Ability to Turn off Lucene Database Backup on the

Single-Server Setup
The Lucene database backup process consists of zipping up and uploading the database file to the central database. By default, this backup process is enabled. If the Lucene database is large, this can be a very intensive process. Since the main purpose of the Lucene database backup is cluster support, it is recommended that it be disabled on single-server Asset Hub installations. To disable it, use the following method: Modifying "com.nrx.textsearch.index.backup.enabled" Parameter

SAP WAS: 1. Open the Visual Administrator.

May 2009

15

NRX Asset Hub 4.6 Release Notes

2. On the Cluster tab, expand the tree MachineName... Server 0 0_xxxx... Services... Web Container. 3. In the right panel of the Visual Administrator window, expand the Asset Hub application nrx.com/nrx, and click the assetHub node. 4. Click View. 5. Click the Environment tab, then the Environment Entries sub-tab. 6. Locate the following environment entry: com.nrx.textsearch.index.backup.enabled Set it to false. 7. Click Modify, then Save, to commit your changes. Click OK in the dialog that appears.

4 Additional Configuration Required When Using the

Asset Hub Auditors Deployed on SAP Web Application Server.

The following procedure must be performed on the SAP Web Application server in order for the Asset Hub warehouse and plant auditors to function properly: 1. Launch Visual Administrator for the server 2. Select Global Configuration->Cluster-><SID>->Server XXXXX->Services->HTTP Provider 3. Click on the Properties tab 4. Remove "*.htm,*.html,text/html" from "AlwaysCompressed" 5. Append "*.htm,*.html,text/html" to the end of "NeverCompressed" 6. Set the "CompressedOthers" value to "false" 7. Save the changes

May 2009

16