How to: |
This section describes how to configure and use the WebFOCUS domain security model with Magnify.
The New Enterprise Domain dialog opens, as shown in the following image.
Note: Since Magnify and the repository are case-sensitive, the name should be entered using lowercase characters.
The Resource template processing complete message is displayed, which indicates that the domain has been created, as shown in the following image.
The Security Rules dialog opens for the new domain, as shown in the following image.
Note: You may need to deselect the Only show Groups with Rules check box to see the domain.
Note: Ensure that a Magnify rule has already been created before performing this step. For more information on configuring rules in WebFOCUS, see the WebFOCUS Security and Administration documentation.
You are now ready to add users that have access to this resource.
The Security Center opens, as shown in the following image.
For more information on configuring users and groups in WebFOCUS, see the WebFOCUS Security and Administration documentation.
Notice that the user bill can view three items in the Resources tree, as shown in the following image.
This is the list of items that Magnify will use to access data.
Notice that the folder name is somebankname, as shown in the following image.
This is the name of the index that you need to create.
The first method is to create an index using the same name as the domain you created earlier (for example, somebankname).
In this example, notice that somebankname is in the directory where the Lucene indexes are located (lucene_index).
The second method is to edit the collections.xml file, which is located in the ibi\config\magnify directory and map a name of a collection to the index(s) with different names.
<collections>
<group name=" somebankname" id="somebankname">
<search lang="en" analyzer="MagnifyAnalyzer" stylesheet="en/en_stylesheet_peter" id="en_search_cent_sales"/>
<component id="centurycustomers" member="centurycustomers"/>
<component id="centuryorders" member="centuryorders"/>
</group>
</collections>
<indexes>
<index name="centurycustomers" directory="centuryelectronics\centurycustomers"></index>
<index name="centuryorders" directory="centuryelectronics\centuryorders"></index>
</indexes>
This method allows you to join multiple indexes into a single collection, or move indexes onto other physical disks, because all of the data cannot fit on a single disk.
For performance reasons, if you have many large indexes, then you can use multiple physical drives.
When you run a search, the new collection names will appear in the drop-down list, as shown in the following image.
However, the domain/group/index name does not appear here. The description appears to the user.
http://hostname:port/ibi_apps/search?form=3&viewname=searchresultsview
&q=a*&site=somebankname&btnG=Search&oe=utf8&ie=utf8&spelling=true&num=
10&getfields=*¶llelreaders=1&facetcounts=false&access=p
This is the name that is validated at search time, to ensure that the user has access to this resource. If you were to try and hack the system by changing the name, then you would not be given access to an index that you were not allowed to view.
Notice that the user cathy can view a different set of items (names) in the Resources tree, as shown in the following image.
The same names are now available in the collection drop-down list. Notice that the name Public is missing from the Search page, as shown in the following image.
This is because there is no index named Public in the directory where the Lucene indexes are located (lucene_index). Indexes that do not exist, do not appear in the collection drop-down list.
WebFOCUS |