Administration and Configuration 
Technical Data
Product Version | SAP NetWeaver Enterprise Search Release: 7.2 Support Package: Stack 01 |
|---|---|
Area | BC-EIM-ESH |
Country Relevance | Valid for all countries |
Note the following changes and new features in the administration and configuration of SAP NetWeaver Enterprise Search:
Simplified Installation (New)
As of this release, the installation process has been restructured to make it easier and faster. The new automatic process comprises the installation and technical configuration of the operating system and the SAP NetWeaver Enterprise Search software. The installation process gathers all necessary entries at the start and then runs with a minimum of interaction.
You can find the installation guide on SAP Service Marketplace at http://service.sap.com/nwes72.
Changes to the Software Architecture (New)
The software architecture of SAP NetWeaver Enterprise Search has been changed. Only the Application Server ABAP is used for the design time and runtime. The Application Server Java is no longer used for the aggregation and display of the search results. The Application Server Java is now only used for life-cycle management tasks, such as executing the post-installation wizard and automatic import of support packages.
More information: Components and Architecture
Connection and Integration of Embedded Search Systems (New)
You can connect SAP Business Suite applications containing search functions that are based on an SAP NetWeaver system of release 7.0 EhP1 or later to SAP NetWeaver Enterprise Search.
This allows you to implement cross-system and cross-application search and navigation means, as well as central modeling, index persistence, and administration. The TREX servers for the individual systems of the release level specified are no longer required, unless they are used for other applications in parallel.
Once you have connected the Embedded Search system, the following data and objects are moved from the Embedded Search system to the SAP NetWeaver Enterprise Search system, also known as the hub system:
Modeling data
Configuration data (search object connectors, software components, system information, scheduled indexing runs, and extraction jobs)
TREX indexes and their content
After completion of the move, the Embedded Search system is no longer available for modeling, connector generation, and connector management. You can now perform these tasks for all connected and moved Embedded Search systems in one central location, the SAP NetWeaver Enterprise Search system.
On the hub system, federated searches across all connected Embedded Search systems are now possible. As before, you can also perform local searches on the connected Embedded Search systems.
More information: Connecting To an Embedded Search System
Backup and Restore (Enhanced)
As of this release, SAP NetWeaver Enterprise Search provides its own data backup. You can back up all important data in your system while it is running (online) with a few simple commands and restore it after a failure.
More information: SAP NetWeaver Enterprise Search Backup and Restore
Technical Management of the System Using the appliancecontrol Tool (New)
appliancecontrol is a new command line tool that allows you to manage the SAP system on the technical level. You can use this tool in a multiblade landscape to manage and moves instances, add blades, and much more.
More information: appliancecontrol Tool
Connection of SAP NetWeaver BW Systems, SAP KM, and File Servers and Web Servers (Changed)
As of this release, the creation of these search object connectors is done using the administration cockpit, as for all other search object connectors.
More information: Creating BW Search Object Connectors, Creating KM Search Object Connectors, and Creating Search Object Connectors for the File Search
Connection of External Search Service Providers via OpenSearch (New)
You can use the new search object connector of type OpenSearch to integrate external search providers that provide a search function available through OpenSearch. On the Internet, you can find many OpenSearch providers that you can integrate in SAP NetWeaver Enterprise Search.
More information: Connecting To OpenSearch
Connection of Non-ABAP-Based Search Service Providers via Data Provider Services (New)
You can use the new search object connector of type Data Provider Service to integrate external search service providers and use the data provider services (DPS) to search data in customer-specific systems and third-party systems that are not ABAP-based.
More information: Connecting To Data Provider Services
Central User Administration (New)
As of this release, we recommend using Central User Administration (CUA) in your customer landscape for SAP NetWeaver Enterprise Search. However, you can continue to use an existing LDAP directory for user administration.
An LDAP directory continues to be the prerequisite for file searching with authorization checks on file servers.
More information: Configuring User Management
Integrated Windows Authentication (Changed)
SAP NetWeaver Enterprise Search 7.2 runs in an ABAP environment, therefore, integrated Windows authentication (logon to SAP NetWeaver Enterprise Search at the same time as the logon to the Windows domain) is not possible in the standard configuration.
Definition of Navigation Targets (New)
In order to jump directly from a search result to the corresponding back-end system using a link, navigation targets are required. In earlier releases, these navigation targets contained links with fixed server information. As of this release, you can use variables for the server information. You maintain the server information outside the template modeler on the configuration screen for the UI technologies.
If a back-end system provides more than one UI technology to display a function, you can group together the associated navigation targets semantically. The grouping is done by function and using an operation ID.
More information: Defining Optional Settings and Maintaining UI Technologies
Actions in Connection with UI Technologies (New)
Before you can use the navigation targets defined in the template modeler, you must work through the following activities for the connected back-end system:
Activate supported UI technologies
WebClient UI
SAP GUI for HTML
SAP GUI
Web Dynpro
Define the sequence and thus the priority of the UI technologies
Specify the associated server connections
More information: Maintaining UI Technologies
New Features in the Connector Administration Cockpit (New)
The connector administration cockpit contains the following new features:
The overview table contains a new column called Searchable. You can use this column to identify whether or not the search object connector can be used for the search.
You can now choose more than one search object connector and perform an action that affects the entire selection, for example, you can simultaneously schedule indexing for more than one search object connector.
There is a new pushbutton called System Settings. Below this button, you can find the functions Maintain UI Technologies, Control Indexing in Real Time, and Connecting Back-End Systems. For more information about these functions, see the corresponding sections of this release note.
The pushbutton Switch to Modeler has been replaced by the link Template Modeler.
More information: Using the Connector Administration Cockpit
Changes to Search Object Connectors (Changed)
You can no longer make changes to search object connectors in the runtime, but only in the design time.
In SAP NetWeaver Enterprise Search 7.2, you can make changes of any sort at the level of the design-time objects, such as templates and virtual templates. You can sort runtime objects of type connector into categories and change their descriptions. You must make all other changes to the actual connectors that were possible in SAP NetWeaver Enterprise Search 7.0 in the design time.
Controlling Real-Time Indexing (New)
SAP NetWeaver Enterprise Search allows you to index data that exists in back-end systems with a minimal time delay. From the administration cockpit, you launch an administration UI that you can use to control and monitor real-time indexing.
More information: Controlling Real-Time Indexing
Entering Connectivity for Back-End Systems (Changed)
To allow the import of data from back-end systems to SAP NetWeaver Enterprise Search, you must store the connection data for the back-end system in a central location.
In the administration cockpit, you can find the command
System Settings 
Connect Back-End Systems 
to do this. You specify the connectivity of the back-end systems sorted by type on the associated screen.More information: Connecting Back-End Systems
Resolving Naming Conflicts (New)
No object types (templates, data types) within a hierarchy of software components may have identical names, therefore the system automatically performs a check for identical names during actions involving search object connector types.
However, in the case of an import, the automatic check and renaming does not take place during the import, but is done later. Therefore, we recommend checking the imported objects for naming conflicts as soon as possible after an import and resolving any conflicts manually.
More information: Resolving Naming Conflicts
Virtual Templates (New)
Virtual templates introduce an abstraction layer in the template modeler. They allow you to cover the following requirements:
You assign meaningful names that people can read easily instead of cryptic technical names.
The system can search through data using different virtual templates that each provide a different perspective on a template.
A normal template has one response structure. If you require a different response for the reasons listed above, you can use a virtual template to implement this requirement.
Virtual templates provide additional entry points to a search object connector template. This allows extraction models to be closely connected with the business object model.
Virtual templates allow you to refine the generic object types; this makes sense if you want to address an instance of a generic object type that is distributed across more than one subobject type.
More information: Creating Virtual Templates
Model Compression (New)
While SAP NetWeaver Enterprise Search is running, the system compresses the models that you have created with the template modeler in the background by default, if there are 1:1 relationships between nodes within a template. Fewer TREX indexes are generated when using model compression, which reduces memory usage on the TREX server and improves search performance.
More information: Model Compression