|Oracle® Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide
Release 11g R1 (188.8.131.52)
Part Number E29138-02
|PDF · Mobi · ePub|
Data lenses and DSAs are stored on an Oracle DataLens Server of your choosing for use by an Oracle DataLens Administration Server. The Administration Server contains information about the different versions of the data lenses and DSAs and instances of the versions themselves. Only users of the Knowledge Studio and users using the Administration web page for the Administration Server can directly manipulate these data lenses. There is no direct access to the repository from the Oracle DataLens Servers. These data lenses are checked into the server from the Knowledge Studio.
Oracle DataLens Server data lenses and DSAs are those that are under version control by the Administration Server for shared use by different team members. This prevents possible problems with more than one user updating a data lens at the same time and possibly losing work. This also provides a single location for backing up the valuable data lenses. These data lenses can be checked out for editing or as read-only by users of the Knowledge Studio that have the correct privileges.
Once these are in the Administration Server repository, any of the data lenses and DSAs can be edited and upgraded when needed.
This chapter describes the following functions contained in the Server panel:
From the Server panel, select Data Lens to begin managing the data lenses in your Administration Server.
The columns contain the following information:
This is the name of the data lens and is a link to the complete history information for the data lens. Click the link to review the data lens details. See "Viewing Data Lens Details and Managing Deployment".
The action buttons that may be active, left to right, are used as follows:
|View or Manage||Click to review or edit the parameters of the given data lens and you are advanced to the Data Lens Component Details for the given data lens panel. See "Viewing Data Lens Details and Managing Deployment".|
|Lock and Unlock||Click to lock or unlock the data lens. The icon toggles from a locked lock to an unlocked lock based on the state of the data lens. You are prompted for a user name when unlocking a data lens to identify who unlocked it. When the user logged in does not have administrative permissions, this button is not displayed.
Typically, the user locks on data lenses are created by users of the Knowledge Studio. Occasionally, these locks need to be overridden by an administrator.
For example, a user might be on vacation and left a data lens locked that is needed by another user or a user inadvertently started editing a data lens in the Knowledge Studio and failed to lock it first. This user would not want to check out the data lens to lock it because that would overwrite the work the user has done on the data lens.
Administrators must be careful when resetting locks to ensure that the latest data lens version is held intact.
|Delete||Click to delete the data lens. This button is active when the data lens is not deployed, is unlocked, and the user logged in has administrator privileges. Once deleted, the data lens is no longer on the Administration Server and cannot be used by any user.|
The revision number of the deployed data lens to the Development (or the Administration/development), Quality Assurance (QA), or Production Servers. The development column is always displayed because it is the default for all data lens. However, the QA and Production columns are displayed when there are one or more data lenses deployed to these types of servers.
The Knowledge Studio user that has locked this data lens for exclusive access or the last administrator that locked it. When the field is blank, it means that the data lens is available for checkout by any Knowledge Studio user with access privileges.
The initial description of the data lens when it was first checked into the repository. This description can be updated from the Application Studio when checking the data lens into the Administration Server.
You can view the complete history of the data lens listed from the most recent to the oldest and change how it is deployed.
To review data lens history or change its deployment, click the data lens name link or the adjacent View or Manage button.
This panel contains the following information about the selected data lens.
The initial description of the data lens when it was first checked into the repository. This description can be updated from the Knowledge Studio when checking the data lens into the Administration Server.
Indicates a whether the parse results of the data lens will be cached is turned on or off for the data lens as a yes or no value respectively. This option is set in data lens in the Knowledge Studio by modifying the data lens options.
This is the language that the data lens uses as the basis translation language.
This is a list of the alternate standardizations that the data lens uses. In this case there is only the default standardization being used, so this column is blank.
This is a list of the classifications that the data lens uses. In this case there are two separate classifications that are being used by the data lens.
This is a list of the languages that the data lens can be translated to.
This is a list of the numeric conversions that have been defined for this data lens.
This panel enables you to view the deployment status of a data lens, as well as deploy and undeploy it. It contains the following information and tasks.
The particular revision, starting from one, listed in reverse order so the latest revision is always at the top of the list. In this example there are two revisions.
Select an icon (P, Q, or D, which indicate Production, QA, and Development respectively) to deploy a particular version of this data lens to the Administration Server or Oracle DataLens Server. This means that the data lens will be listed as a data lens available for loading on the Administrator or Oracle DataLens Server. The icons displayed are based on the configured server groups.
This shows the revisions of the data lens including:
Comments about what the Knowledge Studio user changed in the data lens in each revision.
The name of the Knowledge Studio user that made the revision.
The date/time that the revision was checked into the Administration Server.
These icons show how the data lens is currently deployed to the Administration and Oracle DataLens Servers.
Undeploy from Development
This will undeploy a data lens from the Development Server, which means it will not be listed as a data lens to be loaded as well. This button is only available for the version that is deployed to the Administration Server.
Undeploy from Production
This will undeploy a data lens from the Oracle DataLens Server, which means it will not be listed as a data lens to be loaded as well. This button is not available if the data lens is not currently deployed to the Oracle DataLens Server.
Undeploy from QA
If there is a QA server group defined, then there will be a button to undeploy or deploy to the QA area.
It is recommended that data lens only be deployed to the development area. Data lens deployment to the QA and Production areas can be done more easily by using the package deployment of DSAs, and the packages give a level of version tracking that cannot be done by manual data lens deployment.
Data lenses groups are created and managed in Application Studio for use with Item Definition transformations in a DSA instead of selecting them individually in each transform. A data lens group can be used in one or multiple DSA steps and in multiple DSAs. When a data lens group is changed in Application Studio, the change is effective immediately in both Application Studio and on your Oracle DataLens Server.
To view the data lens groups associated with all of the DSAs checked into the Administration Server, click Data Lens Group.
All of the DSAs on the Administration Server that contain data lens groups are listed by data lens group name, description, and what type of data lens it is, Development, QA, or Production. Additionally, data lenses that are not deployed to QA or Production include '[Not Deployed]' after the data lens name. Data Lens Groups cannot exist with no data lenses.
The default view is that only the first data lens group is expanded though you can expand or collapse each one by clicking the arrow adjacent to the name. You can view all of the data lens group information by clicking Expand All.
To alphabetize the list, hover to the right of the name and use the up and down arrows to sort the list alphabetically either ascending or descending respectively.
A data lens group can only be deleted if it is not being used by any DSAs so attempting to do so results in an error that details which DSAs are still using it. To delete an unused data lens group, click the delete button in the Actions column, which will delete it and refresh the panel list.
You can manage all DSAs on the Administration Server by clicking DSAs.
This DSA - Administration panel operates in a similar manner to the Data Lens Administration panel, see "Viewing Data Lens Details and Managing Deployment". The following sections describe the DSA specific functions.
The one exception is the additional Promote column, which allows you to create and promote DSA packages, with the data lenses contained within, from development status to Production or QA for users to check out. DSA packages include the data lenses and data lens groups associated with the DSA.
To create a production or QA DSA package:
Click the green arrow in the Promote column for your DSA.
(Optional) Change the Tag Name that will identify the package.
Enter a description for the package to aid in identification.
Select whether or not the package configuration has been tested in Application Studio with either true or false.
Click the appropriate link to view the promoted package, QA or Production.
Example 2-0 shows both a true (blue check mark) and false (red R icon) data lens package. If there is more than one package for the DSA, then all of the package versions are listed as in this example. This is to ensure that users are able to identify the testing state of the data lenses that are available for production use.
You can view all of the promoted data lens packages for each DSA as described in "Viewing DSA History Chronology".
Click the name of the data lens package to view its details.
The history details for a DSA including deployment status, area of deployment, and the check in information is obtained by clicking the on name of a DSA.
The Deploy Status and Deployed columns contain deployment icons that enable you to toggle the deployment of the DSA. Oracle recommends that only the Deploy to Development icon be used. For deployment to QA or Production, the best practice is to promote the DSA package rather than using the Production and QA deployment icons so that you can track versions in the QA or Production server groups. See "Promoting DSA Packages".
You can view any data lens packages that have been promoted for the DSA by clicking View Production Package and results in viewing the data lens package details as in Figure 2-7.
To view all of the input and output steps, transformation maps, data lenses, web services, and database connections in the DSA, click the History Chronology for DSA Name link.
StatSim is a matching application created in a DSA in the Application Studio that allows you to quickly identify similar records in your data. The process of identifying matches consists of two steps:
Creating an index from a dataset.
Finding the records in your index that are similar to your query records.
The StatSim indexes created by DSAs are stored on the Administration Server. You must create a StatSim database connection prior to use by DSAs in the creation of StatSim indexes, see "Creating a StatSim Database Connection".
To view and manage StatSim indexes, from the Server panel, select StatSim Index.
This panel contains the following information about the StatSim indexes.
The name of the StatSim index that is creating or has been created.
You can remove a StatSim index by clicking the delete button.
If the index does not previously exist, and an index creation job is cancelled, then the index is deleted. By contrast, if the index exists and you run a job to update the index, the original index is automatically deleted. In other words, the original index is not left intact.
You can view the status of the StatSim index as it is being created and after successful completion. Click the refresh button to ensure that you are viewing the current progress. The progress icon is dimmed until the StatSim index creation has completed. The green arrow icon means the database connection is responsive, but no StatSim indexes are present. The red arrow means that the database connection is unresponsive and the StatSim index status is unknown.
You can also view the job process status by selecting Job Status in the Jobs panel.
The database connection used to retrieve the dataset.
The number of data rows processed to create the StatSim index.
Reports how much memory was required to build the index.
The number of Ngram characters set in the DSA.
Reports the amount of time required to build the StatSim index.
Reports the last time that the StatSim index was built.
From the Server panel, select Reports to access the data lens and DSA reports.
Use the options in the Data Lens Reports panel as follows:
Click to view the data lens version history and the transformation types and revisions in this comprehensive repository history report. All deployment types are included in this report.
Select a Datalens and a deployment Area from these list options, then click Datalens Usage to view how a the selected data lens is being used in the selected deployment area.
Click to view only the Production deployed data lens version history and the transformation types and revisions in this production specific repository history.
Use the options in the DSA Reports panel as follows:
Click to view a comprehensive repository history of all the DSAs on the Administration Server.
Select a DSA, the type of report you want (deployed DSA or repository), and a deployment Area from these list options, then click DSA BOM to view the data lenses and database connections that are used by the selected DSA.