Configuring reverse proxy. SAP SAP BusinessObjects Business Intelligence platform 4.0
Реклама
Реклама
Platform Search
For example, the following command deploys OpenSearch to a WebSphere 7 Web application server: wdeploy.bat websphere7 -Dapp_source_tree=<BOE_Install_Dir>\<Enterprise_DIR>\warfiles" -DAPP=OpenSearch deploy
4.
Restart the application server.
21.2.2 Configuring reverse proxy
To deploy Business Intelligence Web Applications on a Web application server located behind the reverse proxy server, configure reverse proxy server to map incoming URL requests to the correct WAR file.
To illustrate the configuration steps, we use Apache 2.2 Reverse Proxy server as an example. To configure Apache 2.2 Reverse Proxy server for OpenSearch:
1.
Set up the reverse proxy and make the changes in the WEB-INF\config.properties file of
OpenSearch.
2.
Enable the following context parameters and change the values accordingly.
• proxy.rpurl
: This is the reverse proxy URL for OpenSearch (such as http://machineIPAd dress/RP/OpenSearch/
).
• proxy.opendoc.rpurl
: This is the reverse proxy URL for Open Doc (such as http://ma chineIPAddress/RP/BOE/
).
3.
Update the httpd.conf file, located under the Apache Reverse Proxy installation folder, with the following settings:
•
ProxyPass /RP/BOE/OpenDocument/ http://<Tomcat host>:<Connector
Port>/BOE/OpenDocument/
•
ProxyPass /RP/OpenSearchRP/ http://<Tomcat host>:<Connector
Port>/OpenSearch/
•
ProxyPassReverseCookiePath /BOE /RP/BOE
•
ProxyPassReverseCookiePath /OpenSearchRP /RP/OpenSearchRP
4.
Restart the Apache 2.2 Reverse Proxy server.
21.2.3 Configuring Application Properties in CMC
To configure the Platform Search application properties, complete the following steps:
1.
Go to the "Applications" area of the CMC.
2.
Select Platform Search Application.
3.
ChooseManage > Properties. The "Platform Search Application Properties" dialog box appears.
682 2012-12-12
Platform Search
4.
Configure the platform settings that you want.
The configurable properties are described in the following table:
683 2012-12-12
Platform Search
Option
Search Statistics
Stop / Start Indexing
Deafult Index Locale
Description
Platform Search offers the following search statistics:
• Indexing Status: displays the status of the indexing process.
• Number of indexed documents: displays the number of documents that are indexed.
• Last indexed time stamp: displays the time stamp at which the document was last indexed.
Start or Stop Indexing options enable you to start or stop the indexing process when you want to switch from continuous crawling to schedule crawling, or for maintenance purpose.
To stop indexing, click Stop Indexing and then click OK in the confirmation dialog box.
Platform Search uses the locale specified in CMC page for indexing all the default BI documents.Once the document is localized the corresponding language analyzer is used for indexing.
Search is based on the Client 's product Locale and the weightage is given to client product locale.
You can configure the weightage in CMC configuration properties.
Crawling Frequency
684 2012-12-12
Platform Search
Option Description
You can index the entire SAP BusinessObjects BI platform repository by using the following options:
• Continous Crawling: With this opinion, indexing is continuous where the repository is indexed whenever an object is added, modified, ordeleted. It allows you to view or work with the most up-to-date BI platform content. Set by default, the continuous crawling updates the SAP BusinessObjects BI platform repository continuously with the actions that you perform. Continuous crawling works without a user's intervention and reduces the time taken for indexing a document.
• Scheduled Crawling: With this option, indexing is based on the schedule set by the Schedule options.
For more information about scheduling an object, refer to Scheduling an Object section of Platform Search in the SAP BusinessObjects
Business Intelligence platform CMC Online Help.
Note:
• If you select Schedule Crawling and set the Recurrence to an option other than Now Platform Search displays the date and time stamp when the document is scheduled to be indexed next.
• If you select Schedule Crawling, then the Start Indexing button is enabled and the Stop Indexing button is disabled.
• Once the scheduling is complete, the Stop Indexing button is disabled.
685 2012-12-12
Platform Search
Option
Index Location
Description
When the documents are indexed, they are stored in shared folders in the following locations:
• Master index location (indexes and speller): The master and speller indexes stored in this location. During a search workflow, the initial hits are retrieved using the Master Index and the speller indexes are used to retrieve suggestions. In a clustered BI platform deployment, this location should be on a shared file system that is accessible from all nodes in the cluster.
• Persistent data location (Content stores): The content store is placed in this location. It is created from the master index location and remains in sync with it. The content store is used to generate facets and process the initial hits generated from the Master Index location.
In a clustured SAP BusinessObjects BI platform deployment, content stores are generated at every node.
The persistent data location is the only index location that is affected by the clustered environment as it contains the content store folders.If
a machine has a single search service, then there will be only one content store location. For example, {bobj.enterprise.home}\data\PlatformSearchData\workspace\Server\ContentStores.
However, in a clustered environment, if there are multiple search services, then each search service will have one content store location.
For example, if you have two instances of a server running, then the content store locations would be as follows: a. {bobj.enterprise.home}\data\PlatformSearchData\workspace\Server\ContentStores.
b. {bobj.enterprise.home}\data\PlatformSearchData\workspace\Server1\ContentStores.
• Non-persistent data location ( Temporary files, Delta Indexes): In this location, the delta indexes are created and stored temporarily before being merged with the Master index. The indexed documents from this location are deleted once they are merged with the Master
Index.In addition, surrogate files (output of the extractors) are created in this location and stored temporarily until they are converted into delta indexes.
Note:
• All the index locations must be shared locations.
• You need to click Stop Indexing to modify the index location.
• If you modify an index location, you need to copy the content to a new location, else the existing index information will be lost.
686 2012-12-12
Platform Search
Option
Level of indexing
Description
You can tune the search content by setting the level of indexing in the following ways:
• Platform Metadata:An index is created only for the platform metadata information such as titles, keywords, and descriptions of the documents.
• Platform and Document Metadata: This index includes the platform metadata as well as the document metadata. The document metadata includes the creation date,modification date, and name of the author.
• Full Content: This index includes the platform metadata, document metadata, and other content such as:
• The actual content in the document.
• The content of prompts and LOVs.
• Charts, graphs, and labels.
Note:
When you modify the level of indexing, the indexing is initialized for the entire SAP BusinessObjects BI platform repository refresh.
687 2012-12-12
Platform Search
688
Option
Content Types
Description
You can select the following content types for indexing:
• Microsoft Word
• Microsft Excel
• Microsoft PowerPoint
• Text
• Adobe Acrobat
• Rich Text
• Crystal Reports
• Universe
• Web Intelligence
Rebuild Index
This option deletes all the existing indexed content and re-indexes the entire document from the start.
You can select the Rebuild index option irrespective of the indexing status. However, the Rebuild index option would not function if indexing is stopped, and you select the Rebuild index, save and close the Platform Search application.
When indexing is stopped, and you select the Rebuild index, save and close the Platform Search application, then re-open the configuration page and click Start Indexing, the stored rebuild index would re-index the entire document automatically.
If you do not want Platform Search to re-index the documents, you need to deselect the Rebuild index before clicking Start Indexing.
Documents Excluded from indexing
The Documents Excluded from Indexing option excludes documents from indexing. For example, you may not want extremely large Crystal reports to be made searchable to ensure the report application server resources are not overloaded. Similarly, you may not want publicationswith hundreds of personalized reports to be indexed.
By excluding particular documents, you can prevent them from being accessed by Platform Search. It is important to note that if a documentis already indexed before it is put into this group, the document may stillbe searchable. To ensure that documents in the Documents Excluded from
Indexing group are not searchable, you must rebuild the index.
By default only the Administrator account has full control of the Documents Excluded from Indexing. Other users with the following rights can only add documents to the Documents Excluded from Indexing group:
• View and edit rights on the category.
• Edit the document directly.
2012-12-12
Изтегляне
Реклама