| Oracle® Adaptive Access Manager Administrator's Guide Release 10g (10.1.4.5) Part Number E12055-03 |
|
|
View PDF |
| Oracle® Adaptive Access Manager Administrator's Guide Release 10g (10.1.4.5) Part Number E12055-03 |
|
|
View PDF |
A Transaction is any process a user performs after successfully logging in. Examples of Transactions are making a purchase, bill pay, money transfer, stock trade, address change, and others.
With each type of Transaction, different type of details are involved. For example, in a stock trade, the data involved would be the symbol, unit price, number of shares, buy or sell action, time of trade, total amount, broker commission, and so on.
Before the client-specific Transaction with its corresponding Entities can be captured and used for enforcing authorization rules, fraud analysis, and so on, it will need to be defined to the system first. Adaptive Risk Manager's Transaction Detail feature allows administrators to perform this task.
With Adaptive Risk Manager's Transaction Definition feature, an administrator is able to create entity and data element definitions and map them to the client-specific data (source data).
This chapter focuses on the creation of Entities and Transaction Definitions. Information on other procedures will also be provided.
The prerequisites for using Transactions is as follows:
Using the Transactions feature involves native integration.
Transaction data is saved into Adaptive Risk Manager using the APIs described in the Oracle Adaptive Access Manager Developer's Guide.
An Entity is a set of fields. It is like a user-defined structure that can be re-used across different transactions. Only appropriate and related fields should be grouped into an Entity.
Configuration of a Transaction Definition involves the following tasks:
Identify all the Entities related to the third-party Transaction.
Typical Entities are Address, Account, CreditCard, Customer, ProductDetails, and others.
Use the Entity Definition user interface to create Entity Definitions.
Refer to the "Creating an Entity" section.
Activate the Entity Definition using the Activate button in the Entity Definition user interface.
Create the Transaction Definition using the Transaction Definition user interface.
Refer to the "Creating the Transaction Definition" section.
Add the Entities to the Transaction Definition using the Entities tab in the Transaction Definition user interface.
Refer to the "Adding Entities to the Transaction Definition" section.
Add Transaction data elements using the Data tab in the Transaction Definition user interface.
For example, TransactionAmount and TransactionDate.
All data fields that do not fit into entities should be added as transaction data elements.
Refer to the "Adding the elements that need to be added directly to the Transaction Definition" section.
Add the source data elements to the Transaction Definition using the Source Data tab in the Transaction Definition user interface.
Source data elements are the list of fields that are coming from the external application. Make sure the source data "keys" match the "keys" used by the external application while sending the transaction data.
Refer to the "Adding the source data elements to the Transaction Definition" section.
Add the mapping for the data elements using the Data Mapping tab.
Refer to the "Adding the mapping for the data elements" section.
Add the mapping for the Entity elements using the Entity Mapping tab.
Refer to the "Adding the mapping for the Entity elements" section.
Activate the Transaction Definition.
To create an Entity, follow the steps below.
From the Admin menu, select Entities.
For the Entity Name field, choose Create New Entity.
Enter the Entity name.
Enter the Entity ID.
The Entity ID is a string that will indicate the Entity.
Enter a description.
Click Save.
In the Data tab, you will specify what elements are part of that Entity. For example, for an Entity like Address, the elements will be AddressLine1, AddressLine2, City, State, Country, and ZipCode.
Select Ext ID if there is an Ext ID value.
The client supplies the Ext ID value. Oracle Adaptive Risk Manager can either store this value for the client or use it to identify the Entity. For example, a client may send merchant, product, and customer Entities. These Entities will already have IDs with the client.
Provide a label.
Provide an Int ID.
The Int ID is used to identify a data element in the Entity. The keys specified in the Data tab will be for internal use. They are typically used in rule conditions and other purposes. Do not change this key after it is defined.
Provide a description.
Specify whether the element is required.
Some data elements are not populated all the time as the data might not be available. Those elements are marked as "not required." For example "Address Line 2" in an address is not required since many addresses will not have "Address Line2."
Specify whether the element should be encrypted.
If encrypted is set to true, data is encrypted before it is stored in the database. This feature protects sensitive data.
Encrypted fields have the following constraints:
These fields cannot be used in rules.
These fields cannot be used in the search criteria while querying for transactions through the query screen
Specify its data type.
If you want to add another element, click Add Row and repeat steps 1 through 7.
Click Save.
In the ID Scheme tab, you will select the elements that can be used to uniquely identify an Entity.
To select the elements, follow the steps below.
Select the Data Identification Scheme tab.
The scheme determines whether the elements that are selected should be stored as plain text (key) or encrypted (digest). The digest scheme is used when the data field value is too large or when there is sensitive data.
Add the elements to the ID Scheme.
Select the order of the elements
The order determines how the data is concatenated while forming the data that identifies the Entity. If you don't enter an order, it will be created automatically.
In the Display tab, you will select the data elements that form the Entity data that can be displayed.
To select the data elements, follow the steps below.
Select the Display tab.
Select the data elements you want to display by clicking Add.
Select the order of the elements
The order determines how the data is concatenated while forming the data to be displayed for the Entity.
To create a Transaction Definition, follow the steps below.
On the Admin menu, select Transactions.
For the Transaction Definition Name field, choose New Transaction Detail.
Enter the Transaction Definition name.
Enter the value for the transaction key.
This key value is used to map the client/external transaction data to transactions in Adaptive Risk Manager.
This value should be sent as the TransactionKey while making the API call for creating or updating the transaction data in Adaptive Risk Manager.
Enter the description.
Click Save.
The Entities tab is chosen by default after clicking Save during Transaction Definition creation in the previous section.
To add Entities to the Transaction Definition, follow the steps below.
Pick an Entity from the Entity Name menu.
The Entities available are the ones we defined earlier in the "Creating an Entity" section.
Enter the instance name.
Enter the relationship type.
For example, Address can be a Billing Address or a Shipping Address.
Enter the display order.
Click Save.
Elements are defined internally. To add elements that need to be added directly to the Transaction Definition, follow the steps below.
Select the Data tab.
Click Add Row.
Enter the data name.
Enter the data type.
Enter the key.
The key is used to identify the data element. The keys specified in the Data tab will be for internal use. They are typically used in rule conditions and other purposes. Do not change this key after it is defined.
Enter a description.
Specify the row and column.
If there is a need to change the Row and Column values, please follow the guidelines below:
Set the column values for the most commonly used fields to 1-3 or 11-13 based on whether it is non-numeric or numeric.
For a given row there can be a total of 13 fields.
For Non-Numeric fields, Column value should be 1 to 10.
For Numeric fields, Column value should be 11 to 13.
Fields in the Data tab are mapped to DATAX (for non-numeric), NUM_DATAX (for numeric) columns in VT_TRX_DATA table in database.
Fields in Entities are mapped to DATAX (for non-numeric), NUM_DATAX (for numeric) columns in VT_ENTITY_ONE_PROFILE table in database.
Specify whether the element should be encrypted.
If encrypted is set to true, data is encrypted before it is stored in the database. This feature protects sensitive data.
Encrypted fields have the following constraints:
These fields cannot be used in rules.
These fields cannot be used in the search criteria while querying for transactions through the query screen
Specify whether the element is required.
Some data elements are not populated all the time as the data might not be available. Those elements are marked as "not required." For example "Address Line 2" in an address is not required since many addresses will not have "Address Line2."
Add other elements by following steps 2 through 9.
Click Save.
The source data is defined by the client. To add source data elements to the Transaction Definition, follow the steps below.
Select the Data Source tab.
Click Add Row.
Enter the data name.
The data name provides a way to identify the element; especially if the key is cryptic. For example, the data name could be Transaction.amount while the key could be D1212.
Enter the data type.
Enter the key.
The client supplies the key.
Enter a description.
Specify whether the source data is needed.
Add other elements by following steps 2 through 7.
Click Save.
Mapping is a way to connect the source data to our Entities/data.
To add the mapping for the data elements, follow the steps below.
Select the Data Mapping tab.
Choose the destination data.
The data elements to choose from are the ones you defined in the "Adding the elements that need to be added directly to the Transaction Definition" section.
Pick the mapping type.
Select Direct, Concatenate, Endstring, and Substring.
Choose Direct if you want a one-to-one mapping of the source data element to the destination data element.
Choose Concatenate if you want to join two or more source data elements to form one data element.
Choose Endstring if you want to have last "x" number of characters from source data as the data.
Choose Substring if you want to have a part of the source data as the data.
If you selected Concatenate as the mapping type, you will have to enter separators.
If you selected Endstring, you will have to enter the last "x" number of characters.
If you selected Substring, you will have to enter the Start Index and the End Index (CSV format). For example if you want "acc" for "account," you would specify 1,3.
Translation Params are the parameters defined when selecting certain Mapping type such as endstring, lowerstring, and substring.
Pick the Source Data.
The client data elements to choose from are the ones that you added in the "Adding the source data elements to the Transaction Definition" section.
Map other elements by following steps 2 through 6.
Click Save.
To add the mapping for the Entity elements, follow the steps below.
Select the Entity Mapping tab.
Pick the Entity.
Select the destination data.
Pick the mapping type.
Select Direct, Concatenate, Endstring, and Substring.
Choose Direct if you want a one-to-one mapping of the source data element to the destination data element.
Choose Concatenate if you want to join two or more source data elements to form one data element.
Choose Endstring if you want to have last "x" number of characters from source data as the data.
Choose Substring if you want to have a part of the source data as the data.
If you selected Concatenate as the mapping type, you will have to enter separators.
If you selected Endstring, you will have to enter the last "x" number of characters.
If you selected Substring, you will have to enter the Start Index and the End Index (CSV format). For example if you want "acc" for "account," you would specify 1,3.
Translation Params are the parameters defined when selecting certain Mapping type such as endstring, lowerstring, and substring.
Select Source Data.
Click Save.
Activate the Transaction Definition using the Activate button.
Some steps are required before a transaction definition can be activated; otherwise, an error message will appear.
The following are required before you can activate a transaction definition:
Source/Input data elements
Mapping for all required Transaction Data Elements
Mapping for all required elements in the Transaction Entities
Log in to Adaptive Risk Manager.
On the Admin menu, point to Entities, and then click List Entities.
Select the criteria you want to filter the Entities on.
Click the Run Query button.
To list Transactions
Log in to Adaptive Risk Manager.
On the Admin menu, point to Transactions, and then click List Transactions.
Select the criteria you want to filter the Transactions on.
Click the Run Query button.
Log in to Adaptive Risk Manager.
On the Admin menu, point to Entities, and then click Export Entities.
Select the criteria you want to filter the Entities on.
Click the Run Query button.
Select the Entity you want to export.
Click the Export button.
Click OK.
Click Save To Disk and then click OK.
Log in to Adaptive Risk Manager.
On the Admin menu, point to Transactions, and then click Export Transactions.
Select the criteria you want to filter the Transactions on.
Click the Run Query button.
Select the Transaction you want to export.
Click the Export button.
Click OK.
Click Save To Disk and then click OK.
Log in to Adaptive Risk Manager.
On the Admin menu, point to Entities, and then click Import Entities.
Browse for your Entities zip file.
Click the Import button.
Log in to Adaptive Risk Manager.
On the Admin menu, point to Transactions, and then click Import Transactions.
Browse for your Transactions zip file.
Click the Import button.
Log in to Adaptive Risk Manager.
On the Admin menu, point to Entities, and then click Create Entities.
Select the Entity you want to modify from the Entity Name list.
From the top portion of the screen, you can modify the name, Entity ID, and description of the Entity; and activate or deactivate the Entity.
From the bottom portion of the screen, you can modify the data elements of the Entity.
Note:
When modifying Entities, do not change the key. The key may be referenced by other applications.Log in to Adaptive Risk Manager.
On the Admin menu, point to Transactions, and then click Create Transactions.
Select the Transaction Definition you want to modify from the Transaction Definition Name list.
From the top portion of the screen, you can edit the name and description of the Transaction Definition; and activate or deactivate the Transaction Definition.
From the bottom portion of the screen, you can edit the Entity and data elements of the Transaction.
Note:
When modifying Transactions, do not change the key. The key may be referenced by other applications.After the Transaction Definition is created, Adaptive Risk Manager will be able to capture information when the client application sends the data.
To view the data the client application sends:
On the Queries menu, select User, Location, or Device.
Select the criteria you want to filter on.
Click the Run Query button.
On the Recent Logins page, click the Session link.
On the Session Details page, click the Transaction Details link.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
