IBM i2 Enterprise Insight Analysis Configuring a deployment before going live. Version 2 Release 1 IBM

Size: px
Start display at page:

Download "IBM i2 Enterprise Insight Analysis Configuring a deployment before going live. Version 2 Release 1 IBM"

Transcription

1 IBM i2 Enterprise Insight Analysis Configuring a deployment before going live Version 2 Release 1 IBM

2 Note Before using this information and the product it supports, read the information in Notices on page 29. This edition applies to version 2, release 1, modification 3 of IBM i2 Enterprise Insight Analysis (product number 5725-G23) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2014, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Going live to Enterprise Insight Analysis users Replacing the i2 Analyze schema Creating an i2 Analyze schema and charting schemes Specifying the i2 Analyze schema and the charting scheme Configuring the security schema and users Security schemas Creating a security schema Specifying a security schema Setting default dimension values Configuring Cognos Cognos reports and i2 Analyze requests i2 Analyze requests and Cognos reports i2 Analyze to Cognos translation file Report results translation file Creating a translation from i2 Analyze requests to Cognos reports Adding an Information Store Configuring quick search Creating and configuring facets Modifying the wildcard minimum character limit 25 Redeploying and resetting i2 Analyze Clearing data from the system Deploying i2 Analyze Notices Trademarks Copyright IBM Corp. 2014, 2016 iii

4 iv Configuring a deployment before going live

5 Going live to Enterprise Insight Analysis users After you successfully create an example deployment of i2 Enterprise Insight Analysis, the next phase is to prepare it for production by customizing it for your organization. Before your deployment goes live, you must provide it with an i2 Analyze schema and a security schema, and you might decide to add services or data stores to the base functionality. Replacing the i2 Analyze schema When you have successfully created an example deployment of Enterprise Insight Analysis, the next step in the path to a production deployment is to customize it for your organization. An important part of this process is to modify or replace the i2 Analyze schema in the example deployment so that it models the data that you want to analyze. The i2 Analyze deployment toolkit contains four pairs of example i2 Analyze schemas and charting schemes: Law Enforcement The law enforcement schema deals with crimes. It contains entity and link types that are designed to track connections within criminal networks. Commercial Insurance The commercial insurance schema deals with fraud in a commercial setting. It contains entity and link types that are designed to track financial transactions such as credit card payments and insurance claims. Military The military schema helps with military intelligence tracking. It contains entity and link types that target military operations. Signals Intelligence The signals intelligence schema focuses particularly on the cellphones and cell towers that are involved in mobile telecommunications, and on the calls that take place between them. Note: Some of the example schemas and charting schemes are provided in multiple languages. These versions are located in a directory that is named with the language code inside the configuration\examples\schemas directory. Depending on the deployment pattern you chose, your example deployment has either the law enforcement or the signals intelligence schema. Unless your data is very close to those examples, the right approach is to start again from scratch. Note: If your data is close to the example schema, then you can modify the schema instead of replacing it, and there is slightly less for you to do. You can follow the procedure in Modifying the i2 Analyze schema One of the consequences of replacing or significantly modifying the schema is that it becomes incompatible with any data in your deployment. As a result, these activities require you to clear the data from i2 data stores. The other requirements depend on your deployment pattern. Copyright IBM Corp. 2014,

6 Based on the different example configurations that IBM provides, the procedures for replacing the i2 Analyze schema are as follows: v If your deployment contains only the Analysis Repository, then redeploying with your new schema (and an accompanying charting scheme) is enough. v If you deployed the Information Store with the Opal services, then you also need to replace the configuration file that governs what filters users see during quick search operations. v If you deployed the Information Store with the Onyx services, then you also need to replace the Cognos reports and mapping files that control how users interact with search results. Replacing the schema is about the most significant change you can make to a deployment of Enterprise Insight Analysis. Aim to do it soon after a successful example deployment, and long before a production deployment. Large changes to an i2 Analyze schema when users and data depend on it are hard to manage. Creating an i2 Analyze schema and charting schemes The supplied i2 Analyze schemas are suitable for production deployments of Enterprise Insight Analysis only when the target environment is close to one of the example deployments. Usually, you must prepare for production deployment by creating your own i2 Analyze schema and your own versions of the other configuration files that depend upon it. The i2 Analyze deployment toolkit includes example schemas that target particular domains: commercial insurance, law enforcement, military intelligence, and signals intelligence. v If one of the supplied schemas matches your requirements, you can use it without modification. Even so, depending on the deployment pattern, you might need to create or edit some of the other Enterprise Insight Analysis configuration files. v Alternatively, one of the supplied schemas might contain some of the entity and link types that you need. If you can meet your requirements by expanding or modifying the existing types, then you can edit the schema to make it fit for purpose. v If none of the supplied schemas is appropriate, then you can create your own schema that precisely models the data in your organization. You must also create one or more charting schemes to accompany your schema. These separate files specify how entities and links and their properties appear when they are visualized on charts. To provide users with more flexibility in their investigations, you can visualize data in different ways by creating multiple charting schemes. The i2 Analyze deployment toolkit includes charting schemes that match the example schemas. You can update these schemes to match any modifications you make to the example schemas; or else you can create charting schemes that match a custom schema. After you create a schema and its corresponding charting schemes, you can deploy it into a test environment for evaluation. Creating an effective schema involves several cycles of reviewing and testing before you use it in a production environment. 2 Configuring a deployment before going live

7 After a schema enters production, the changes that you can make to it are strictly limited. Therefore, it is important to ensure that the schema meets the requirements of the organization before it goes live, and to back up your schema and the production environment regularly. You can view, edit, create, and upload i2 Analyze schemas with Analysis Repository Schema Designer, which is a tool that IBM provides with i2 Analyze. Analysis Repository Schema Designer displays the structure of your schema, and ensures that the schema files that you create are compatible with i2 Analyze. For instructions to create and edit an i2 Analyze schema, see the Analysis Repository Schema Designer documentation. Specifying the i2 Analyze schema and the charting scheme Developing an i2 Analyze schema and a charting scheme for an Enterprise Insight Analysis deployment is an iterative process. You can expect to specify the schema several times as you build towards the production version. As you do so, you must change other parts of the system too. Before you begin Each time you come to this task, you have an i2 Analyze schema that is different from the one that currently applies to the deployment. Either you created a schema, or you edited an existing schema. Now you want to apply the schema to the deployment and test it. About this task This procedure contains an outline of the steps to follow as you develop a schema for your deployment of i2 Analyze. In reality, you are likely to follow some of the steps on each iteration of your design. At the beginning of the process, when you create or copy the schema and charting scheme files, you must specify the new files in the deployment toolkit. As you develop the schema, you might need to clear data from the system, or modify your sample data, or edit another part of the configuration that depends on the schema. Procedure Much of the work in developing the i2 Analyze schema and the other files that depend on it lies in making them consistent with each other. One approach is to start with a schema that contains only a few of the types that you plan to create. Then, get an i2 Analyze deployment working that uses those types. After that, you can add more types to a system that you know to be sound. 1. If you created an i2 Analyze schema and charting scheme, copy the files to the configuration\fragments\common\web-inf\classes directory of the deployment toolkit. 2. If you changed the file names of the i2 Analyze schema and charting scheme, set the i2 Analyze schema and charting scheme that the deployment uses. a. Using a text editor, open the ApolloServerSettingsMandatory.properties file in the same directory as the schema files. b. Set the values of the SchemaResource and ChartingSchemesResource properties to the names of your schema and charting scheme. c. Save and close the settings file. 3. If you made anything other than additive changes to the schema, then clear the data, the search index, and the database from the system. Going live to Enterprise Insight Analysis users 3

8 4. If your deployment includes the Opal services, create and configure facets to match the item and property types that you added or changed in the i2 Analyze schema. See Configuring quick search. 5. If your deployment includes the Onyx services and the Information Store, edit the Cognos mappings to match the schema. See Configuring Cognos. 6. If you have sample data that does not exercise or is no longer compatible with the new version of the schema, update it. 7. Redeploy i2 Analyze. What to do next Repeat the procedure until your i2 Analyze schema fulfills the needs of your organization, and the rest of the deployment works in harmony with it. When the schema reaches that point, you can go on to finalize the charting scheme and develop the security schema. Configuring the security schema and users Example deployments of i2 Analyze have security schemas that allow the software to work, but are not suitable for production purposes. Before you go live, you must develop a security schema that meets the needs of your organization. About this task An i2 Analyze security schema defines the security dimension values that you can assign to items and records in i2 data stores, and the security permissions that you assign to groups of users. The fact that the data stores contain dimension values means that significant changes to the security schema can require you to clear and reingest or repopulate data. This behavior is reasonable while you develop your deployment, but not after you go live with it. As a result, it is important to refine the security schema before you put it into production. After you go live, the changes that you can make are much more limited. The following diagram shows the workflow for configuring security during development of your i2 Analyze deployment: 4 Configuring a deployment before going live

9 Security schemas An i2 Analyze security schema defines the security dimensions that exist in a deployment, and the dimension values that can be assigned to items and records. A security schema also defines the permissions that i2 Analyze users can receive. Every deployment of i2 Analyze has a security schema whose contents reflect local requirements. It is the responsibility of the deployer to ensure that the security schema is appropriate for the environment where it is used. Often, the security dimensions map to security classifications that exist in the organization. Before you create a security schema, it is important to understand the relationship between the security model and the security schema. For more information, see IBM i2 Analyze security model. Security dimensions A security schema defines access security dimensions and grant security dimensions separately. Although they have the same structure, access and grant security dimensions are distinct from each other. In a security schema, dimensions and dimension values must have identifiers that are unique across the whole schema. Security permissions A security schema defines security permissions by user group, and then by dimension. For a particular user group, the schema identifies one or more dimensions for which membership of that group affects access rights. For each identified dimension, the schema contains a list of security permissions. It is not necessary for the security schema to define permissions for every user group in the organization. Similarly, it is not necessary for the permissions within any particular dimension or group to set a security level for every possible dimension value. The completeness of the schema is judged at run time when the security level of a particular user for a particular item or record is calculated. Security schema definitions An i2 Analyze security schema is an XML file with a relatively simple structure. Security dimensions and security permissions are defined in separate sections of the file. In outline, the <SecuritySchema> root element of a security schema contains child elements for the dimension and permission definitions: <SecuritySchema> <SecurityDimensions Id="" Version=""> <AccessSecurityDimensions> <Dimension...> <DimensionValue... />... </Dimension>... </AccessSecurityDimensions> <GrantSecurityDimensions> <Dimension...> <DimensionValue... />... </Dimension>... Going live to Enterprise Insight Analysis users 5

10 </GrantSecurityDimensions> </SecurityDimensions> <SecurityPermissions> <GroupPermissions...> <Permissions...> <Permission... />... </Permissions>... </GroupPermissions>... </SecurityPermissions> </SecuritySchema> The <SecurityDimensions> element has attributes for the Id and Version of the schema. If you modify any part of the security schema, retain the identifier but increment the version number. In this way, you ensure that all i2 data stores and services are informed of the changes. In a valid security schema, the <AccessSecurityDimensions> and <GrantSecurityDimensions> elements must be present, and there must be at least one <GroupPermissions> element inside <SecurityPermissions>. Security dimension definitions: Security dimensions are defined in an i2 Analyze security schema file as children of the mandatory <AccessSecurityDimensions> and <GrantSecurityDimensions> elements. A valid security schema defines at least one access and one grant security dimension. The syntax for defining a security dimension does not depend on whether it is an access or a grant dimension. The structure of the XML is always the same. The following example shows a simple, complete <Dimension> element: <Dimension Id="SD-SC" DisplayName="Security Classification" Description="The security classification of this information" Ordered="true"> <DimensionValue Id="TOP" DisplayName="Top Secret" Description="Top Secret" /> <DimensionValue Id="RES" DisplayName="Restricted" Description="Restricted" /> </Dimension> The attributes of the <Dimension> element affect how the values in the security dimension are interpreted. Attribute Id DisplayName Description Description A unique identifier that is used to distinguish this security dimension throughout the system. A name that identifies this dimension to the user in the Intelligence Portal, for example. A more detailed description of this security dimension that provides more information to the user. In the Intelligence Portal, the description is used as a tooltip. 6 Configuring a deployment before going live

11 Attribute Ordered Description Indicates whether the values in this dimension form a descending sequence in which each value supersedes the values below it. Marking this dimension as Ordered="true" means that a user who has access rights to "Top Secret" data implicitly has the same access rights to "Restricted" data as well. For a dimension in which Ordered="false", there is no such implication, and access rights must be assigned explicitly for each dimension value. The Id, DisplayName, and Description attributes of <DimensionValue> elements have the same purpose and meaning as the <Dimension> attributes with the same names. The identifiers of dimension values must be unique within the dimension that defines them. Important: After you deploy i2 Analyze, the changes that you can make to security dimensions are limited. You cannot add or remove dimensions, or remove dimension values. You can only add values to existing dimensions. For this reason, you must understand the requirements of your organization before you deploy i2 Analyze in a production environment. Security group permission definitions: In an i2 Analyze security schema, the mandatory <SecurityPermissions> element contains one or more <GroupPermissions> elements. Each <GroupPermissions> element defines the security levels that users in a particular group receive for item and records with particular dimension values in an i2 Analyze deployment. The syntax for defining the security permissions for user groups enables membership of one group to convey permissions across several dimensions, and allows different groups to convey different permissions for the same dimensions. The following example shows how to structure <GroupPermissions> elements inside the <SecurityPermissions> element: <SecurityPermissions> <GroupPermissions UserGroup="Clerk"> <Permissions Dimension="SD-SC"> <Permission... /> </Permissions>... </GroupPermissions> <GroupPermissions UserGroup="Manager"> <Permissions Dimension="SD-SC"> <Permission... />... </Permissions> <Permissions Dimension="SD-IT"> <Permission... />... </Permissions>... </GroupPermissions> <GroupPermissions UserGroup="Security Controller"> <Permissions Dimension="SD-GA"> <Permission... /> </Permissions> </GroupPermissions> </SecurityPermissions> Going live to Enterprise Insight Analysis users 7

12 The value of the UserGroup attribute of each <GroupPermissions> element must match the name of a group of i2 Analyze users. The value of the Dimension attribute of each <Permissions> element must match the identifier of one of the dimensions that is defined in the first part of the schema. It is normal for <Permissions> elements for the same dimension to appear in more than one <GroupPermissions> element: v Users who are members of one group but not the other can receive different access levels on items and records that have the same dimension values. v When users are members of more than one group, <Permissions> elements for the same dimension are combined before any access level calculation takes place. In many deployments of i2 Analyze, there is one grant security dimension that contains one dimension value. By referring to the grant security dimension from a single <GroupPermissions> element, you can arrange for grant access to be in the hands of users who are members of a dedicated group. Important: You can add and remove <GroupPermissions> elements from a deployed security schema, if the resulting system continues to obey the rules of i2 Analyze. In particular, it must remain possible for all users to get an access level that is not "none" for at least one value in every access dimension. Security permission definitions: The security permission definitions in an i2 Analyze security schema each associate a single dimension value with a single security level. The definitions can be simple because of the additional context that their location in the security schema file provides. The <Permission> elements that define security permissions always appear inside <Permissions> elements, which in turn always appear inside <GroupPermissions> elements. <GroupPermissions UserGroup="Manager"> <Permissions Dimension="SD-SC"> <Permission DimensionValue="TOP" Level="READ_CLOAKED" /> <Permission DimensionValue="RES" Level="UPDATE" /> </Permissions> <Permissions Dimension="SD-IT"> <Permission DimensionValue="HUMINT" Level="READ_ONLY" /> </Permissions> </GroupPermissions> It is possible, and often desirable, for identical <Permission> elements to appear in different locations in an i2 Analyze security schema. The effect of a security permission definition depends entirely on its position in the file. Important: Like the <GroupPermissions> elements that contain them, you can add and remove <Permissions> and <Permission> elements from a deployed security schema, if the resulting system does not break the rules of i2 Analyze. Creating a security schema Every deployment of i2 Analyze requires a security schema that encapsulates the security model for that deployment. The easiest way to create a security schema is to start from the example that IBM provides with the platform. 8 Configuring a deployment before going live

13 Before you begin Before you create the XML security schema file, you must design the security model for your deployment of i2 Analyze. In particular, you must identify or create the user groups to which security permissions are assigned. When you deploy i2 Analyze, the group names in your security schema must match the names of user groups in the user repository. About this task An i2 Analyze security schema contains definitions of security dimensions and security permissions. When you create a security schema, you define the dimensions and dimension values first, and then define the security permissions that refer to them. Procedure 1. Navigate to the directory in the deployment toolkit that contains the example security schema: toolkit\configuration\examples\security-schema\exampledynamic-security-schema.xml. 2. Make a copy of the example-dynamic-security-schema.xml file, give it an appropriate name, and then open it in an XML editor. 3. Edit the contents of the <AccessSecurityDimensions> element so that it contains a <Dimension> element for each category that your deployment uses to determine access rights to items and records in i2 data stores. 4. Edit the contents of the <GrantSecurityDimensions> element so that it contains a <Dimension> element whose value you can use to convey grant access rights. 5. Edit the contents of the <SecurityPermissions> element: a. Add or modify <GroupPermissions> elements so that they reflect all the user groups to which you assign security permissions. The group names in your security schema must match the names of user groups in the user repository. b. Within each <GroupPermissions> element, add or modify <Permissions> elements to indicate which dimensions are affected by membership of each user group. c. Within each <Permissions> element, add or modify <Permission> elements to assign security levels to items and records that have particular dimension values. If your deployment of i2 Analyze includes an Analysis Repository but no Information Store, there are four permitted values for the Level attribute of the <Permission> element: v NONE v READ_CLOAKED v READ_ONLY v UPDATE If your deployment includes an Information Store, then READ_CLOAKED is not a permitted value, and a security schema that contains it is invalid. Furthermore, since the Information Store is read-only to its users, the UPDATE and READ_ONLY permission levels are equivalent in that context. 6. Increment the value of the Version attribute of the <SecurityDimensions> element. Going live to Enterprise Insight Analysis users 9

14 7. Save the completed security schema to the configuration\fragments\common\ WEB-INF\classes directory in the deployment toolkit. What to do next Modify the deployment toolkit to specify that i2 Analyze uses the new security schema, and then redeploy the platform and conduct your tests. If necessary, iterate over these steps again until you have the security schema that you need. Specifying a security schema The security schema is a key component of an i2 Analyze deployment, and configuring it correctly is an important part of the development process. Replacing or making significant changes to the security schema requires you to clear and repopulate the data stores in your deployment. About this task One of the features of i2 Analyze security is that items in the Analysis Repository and records in the Information Store must have dimension values from every dimension in the security schema. As a result, it is not possible to add security dimensions or remove dimension values without invalidating the data in the data stores. IBM recommends that you build and refine the security schema before your deployment goes into production use. Note: The IBM i2 Analyze Security White Paper contains more information about the security model and the security schema. Procedure After you perform an example deployment of i2 Analyze, use the following procedure to replace the security schema with one that you created or modified. Note: For a description of how to make small modifications to the security schema in a production deployment of i2 Analyze, see Modifying the security schema. 1. In Windows Explorer, navigate to the configuration\fragments\common\web- INF\classes directory in the deployment toolkit. 2. Open the ApolloServerSettingsMandatory.properties file in a text editor. 3. Set the value of the DynamicSecuritySchemaResource property to the name of your new or modified security schema. 4. Save and close the properties file. 5. Follow the instructions in Clearing data from the system to remove all the data from the data stores in the i2 Analyze deployment. 6. Follow the instructions in Deploying i2 Analyze to deploy your new or modified security schema and restart the system. What to do next After you change the security schema, you might need to change the dimension values that records and items receive when they enter the system. After those changes, add some data to the system, and verify that users see the behavior that you intended. Iterate over the process of modifying and replacing the schema as many times as you need. 10 Configuring a deployment before going live

15 Setting default dimension values When a user creates an item in the Analysis Repository, i2 Analyze applies a default set of dimension values. Similarly, when the Information Store ingests data, the created records receive dimension values during the process. When you replace or modify the security schema, you must ensure that the mechanisms for setting dimension values reflect those changes. About this task Items and records in i2 Analyze data stores can receive dimension values in a number of different ways, but the rules are always the same. Each item and each record must have at least one dimension value from each security dimension. If you add or remove dimensions, or if you remove values from an existing dimension, you must make corresponding changes to any lists of dimension values that you use. Procedure 1. If you have an Analysis Repository, i2 Analyze assigns dimension values to items in several different circumstances. Items receive dimension values when Intelligence Portal users create them. Items also receive dimension values when users search for them through an ibase connector, or Connector Creator, or a custom data access on-demand solution. a. To change the set of security dimension values that items in the Analysis Repository receive by default: 1) In an XML editor, open the configuration\fragments\core\ ApolloClientSettings.xml file from the deployment toolkit. 2) Update the <DefaultItemSecurityTags> element with the identifiers of security dimension values from your updated security schema. As always, you must specify at least value from each security dimension. 3) Save and close the file. b. If your deployment of i2 Analyze includes an ibase connector, edit the configuration\environment\ibase\environment.properties file in the deployment toolkit. Modify the ibase.security.context setting so that it reflects the changes that you made to the security schema. c. If your deployment of i2 Analyze includes Connector Creator, change the contents of the <securitydimensionvalueids> element in the configuration file to reflect the security schema changes. d. If your deployment of i2 Analyze includes a custom data access on-demand solution, then you must amend its behavior too. The implementation must provide the items that it retrieves with valid combinations of security dimension values. 2. If you have an Information Store, the records that it contains receive their security dimension values during the ingestion process. You must modify the configuration of that process so that all records receive sets of dimension values that remain compatible with the security schema and the rules of i2 Analyze. v v To change the behavior of an ingestion process that uses staging tables and an XML mapping file, edit the contents of the <securitydimensionvalues> element in the mapping file. To change the behavior of an ingestion process that uses IBM DataStage, edit the parameters of the transformer stages that apply security settings to ingested records. Going live to Enterprise Insight Analysis users 11

16 Configuring Cognos 3. Redeploy and restart your deployment of i2 Analyze. Unlike modifications to the security schema itself, changing references to the security schema never requires you to clear the contents of your data stores. Cognos reports and i2 Analyze requests A deployment of IBM i2 Enterprise Insight Analysis that contains the Information Store with Onyx services depends on the exchange of information with IBM i2 Analyze and IBM Cognos Business Intelligence. Enterprise Insight Analysis must be able to run Cognos reports and present the results correctly to i2 Analyze. In a deployment, there are two points where Enterprise Insight Analysis passes information between i2 Analyze and Cognos: v The searches that users run in the Intelligence Portal must result in calls to specific Cognos reports. v The results that are returned by Cognos reports must be visualized to users as items in the Intelligence Portal. The results that are returned by Cognos reports can also be filtered by property values, reducing the amount of data that is returned. When data is exchanged in searches that users run in the Intelligence Portal, translations must be made between the different ways that i2 Analyze and Cognos represent information. These translations reflect the i2 Analyze schema, which defines the core data model in Enterprise Insight Analysis. In Enterprise Insight Analysis, the translations are defined in an XML file that you must update to reflect your deployment. The Enterprise Insight Analysis Integrated Components include tools that generate a template translation file from an i2 Analyze schema. i2 Analyze requests and Cognos reports In IBM i2 Enterprise Insight Analysis, the IBM Cognos Business Intelligence reports determine the requests that a user can make against the Information Store. Enterprise Insight Analysis must be able to convert user requests, which are formulated in terms of IBM i2 Analyze items, into calls to Cognos reports. Each item type in the i2 Analyze schema must correspond to a single Cognos item type for the data in the Information Store. The translation file defines the item types, and their property types, that visual query supports. The file also defines the visualization that is used when the visual query results are displayed. The file that translates from user requests into calls to Cognos reports must be able to associate those requests with the appropriate reports. The file lists, for each i2 Analyze item type, the property types on which users can constrain their searches. If a property type does not appear in the translation file, then users are not able to configure search conditions with that property type. 12 Configuring a deployment before going live

17 i2 Analyze to Cognos translation file Every deployment of IBM i2 Enterprise Insight Analysis with the Information Store Onyx services must include a translation file that translates requests from IBM i2 Analyze into a form that is compatible with IBM Cognos Business Intelligence. The contents of the file depend on the i2 Analyze schema and on the Cognos reports that are available in your deployment. In outline, the XML file that translates requests from i2 Analyze into calls to Cognos reports has the following structure: <ArgumentTranslation> <ItemTypes> <ItemType> <PropertyTypes> <PropertyType/>... </PropertyTypes> </ItemType>... </ItemTypes> <ReportCollections> <ReportCollection> <SummaryReport/> </ReportCollection>... </ReportCollections> <SupportedFilterOperators> <FilterOperator/>... </SupportedFilterOperators> </ArgumentTranslation> Inside the <ArgumentTranslation> root element, the XML file has three main sections: v The "item types" section contains an entry for every item type in the i2 Analyze schema for which Cognos reports can return information. Each entry contains a list of the property types that the reports make available for users to specify in searches. v The "report collections" section enumerates the different Cognos reports that can return information for each item type that is identified in the first section. When a link type supports different combinations of entity types at the ends of the link, there is a report collection for every combination. The item and property types that are associated with a report collection define which item and property types are available in visual query. For each item, the report collection specifies the analytic that is used for each link type and end combination. v The "supported filter operators" section lists the operators that users can specify against items when they create a visual query. Values in this list must match constants from the FilterOperator enumeration in the i2 Analyze API. Going live to Enterprise Insight Analysis users 13

18 Item type definitions The first section of the translation file defines the item and property types that can be included in a visual query. Cognos reports are run on the results that are returned from an Information Store query. The list of item types in the translation file can be a subset of the types that are available in the i2 Analyze schema. Enterprise Insight Analysis uses the information in the file to constrain the options that are available to users when they search the Information Store. In the translation file, the i2 Analyze item types that the Enterprise Insight Analysis deployment supports are described inside a parent <ItemTypes> element. Each <ItemType> child element defines a translation from an i2 Analyze item type to a specific Cognos item type. In turn, the <PropertyType> child elements list the i2 Analyze property types that are associated with the parent item type. Item types and Cognos types For an item of a particular type in the i2 Analyze schema, a search produces results that contain the corresponding Cognos item type. In the translation file, attributes of the <ItemType> element define this translation: <ItemTypes> <ItemType CognosItemType="..." Id="...">... </ItemTypes> Every <ItemType> element has two mandatory attributes: Attribute CognosItemType Id Description The internal database item type. This value is the Cognos type that corresponds to the i2 Analyze schema type that is defined in the Id attribute. The identifier in the i2 Analyze schema for the specified item type. Property types Inside an <ItemType> element, the mandatory <PropertyTypes> child element contains a list of the property types for that item type that are available for user searches. You do not have to list every property type that might be returned in the Cognos results. Only those property types that you want to make available for users to constrain and filter their searches must be specified. If an item type does not have any properties for which users can search, then the <PropertyTypes> element can be left empty. Otherwise, it contains <PropertyType> child elements. For example: 14 Configuring a deployment before going live

19 <ItemType CognosItemType="2" Id="LCO1"> <PropertyTypes> <PropertyType Name="Communication Type" Id="LCO3"/> <PropertyType Name="Communication Start Date" Id="LCO4"/> <PropertyType Name="Communication Start Time" Id="LCO5"/> <PropertyType Name="Communication Duration" Id="LCO6"/> <PropertyType Name="Location Data" Id="PT344" VisualQueryChain="ET8,LCO1,ET8" GeospatialId="CDR" /> </PropertyTypes> </ItemType> Every <PropertyType> element has at least one attribute and can have more: Attribute Name Id GeospatialId VisualQueryChain Description A name that describes the i2 Analyze property type. This optional attribute is provided to help you identify the property types more easily. Values do not need to correspond exactly to property type names defined in the schema or elsewhere. The identifier in the i2 Analyze schema for the specified property type. This attribute is mandatory. Indicates that users can search for items with property values that are in a defined geospatial area, rather than matching a specific set of coordinates. By default, the available values are CDR (call detail record) and NLD (network location data). These options and any others you add must correspond to key values in the ApolloEIAClientSettings.xml file in your i2 Analyze deployment toolkit. You can enable geospatial searches for only one item type per Cognos item type. When you specify the GeospatialId attribute, you must also include the VisualQueryChain attribute. A comma-separated list that represents the series of item types in the query that Enterprise Insight Analysis creates in the Intelligence Portal when a user defines a geospatial search area. You specify item types by using the identifiers in the i2 Analyze schema. The query structure that you define must be either a single entity or a linear chain of alternating entities and links, starting and ending with an entity. You must include in the query at least one instance of the item type that is specified in the parent <ItemType> element. The VisualQueryChain attribute is mandatory if you set the GeospatialId attribute for the specified property type. Geospatial search settings When you add the GeospatialId attribute to a <PropertyType> element, users can apply geospatial constraints when they search the values of the specified property type. The value of the GeospatialId attribute identifies the type of data that provides the location information. To search for items by their location, the user defines the search area on a map in IBM i2 Analyst's Notebook Connector for Esri, right-clicks, and selects the appropriate option. Then, Enterprise Insight Analysis creates a query in the Intelligence Portal with the appropriate item types added. You specify the structure of the query that Enterprise Insight Analysis creates in the Intelligence Portal by using the VisualQueryChain attribute. The geospatial constraint is applied to the first instance in the query chain, reading from left to Going live to Enterprise Insight Analysis users 15

20 right. Users can modify the query, but they cannot change the geospatial constraints or apply the constraints to a different item type. The default labels for the Analyst's Notebook Connector for Esri commands Search Call Detail Records and Search Network Location Data, are specified in the configuration\fragments\core\apolloeiaclientsettings.xml file in the Enterprise Insight Analysis toolkit on your i2 Analyze server. The labels and the corresponding keys that relate to the data types specified by the values of the GeospatialId attribute are defined in the <EIAEsriSearchCommands> element. You can edit the values in the element to modify the command labels or add new commands for more data types. Report collection definitions The "report collections" section enumerates the different Cognos reports that can return information for each item type that is identified in the first section. When a link type supports different combinations of entity types at the ends of the link, there is a report collection for every combination. The report collections define which analytic views correspond to an item type that is available in visual query. For each item type, the report collection specifies the analytic that is used for each link type and end combination. When a user searches the Information Store, Enterprise Insight Analysis responds by running a Cognos report. The choice of which report to run depends on the type and structure of the results that the user requires. In the translation file, the <ReportCollections> element contains information that enables Enterprise Insight Analysis to select and run the appropriate report. The contents of the <ReportCollections> element reflect the different ways that users can request data: v Users can search for entities or links in the terms that are encapsulated in the "item types" section of the XML file. That is, users can search for entities of particular types with specific property values, and they can search for linked entities with defined criteria. v Users can browse in the Intelligence Portal or add to an IBM i2 Analyst's Notebook Premium chart all of the items that are returned by a search. That is, users can request that every item in a set of search results is retrieved and displayed on a new Intelligence Portal tab or an Analyst's Notebook chart. v Users can refresh or update selected items in search results that are displayed in the Intelligence Portal or Analyst's Notebook. That is, users can request the latest versions of specific items that were returned by an earlier search. v When the results of a search are displayed in the Intelligence Portal or Analyst's Notebook, users can run the Expand and Find Path analytics on selected entities in those results. The translation file contains a <ReportCollection> element for each of the structures that an Enterprise Insight Analysis user can request. Report collections for entity searches When a user submits a search request, Enterprise Insight Analysis initially runs a summary report. 16 Configuring a deployment before going live

21 The translation file contains one <ReportCollection> element for each entity type that can appear in the Cognos results. For example: <ReportCollection xsi:type="ns3:entityreports" ItemTypeId="ET3"> <SummaryReport Name="VQ_Entity_Vehicle_sp1"/> </ReportCollection> The xsi:type attribute indicates the search structure for which the reports are intended. The ItemTypeId attribute specifies the item type identifier from the item type definition in the translation file. Each <SummaryReport> child element has a Name attribute that identifies the Cognos report. When it is appropriate to do so, you can use the same report for different purposes. Report collections for link searches The requirements on Cognos reports that run in response to searches for links are similar to the requirements on reports for entity searches. In the translation file, the <ReportCollection> elements for a link type contain more information than for a single entity type. The extra content is required to identify the entity types that are connected by links of a particular type in the Information Store. For example: <ReportCollection xsi:type="ns3:dumbbellreports" End2TypeCognosPromptName="p_pVal1_toEntityType" End2TypeId="ET4" LinkTypeId="LT4" End1TypeId="ET5"> <SummaryReport Name="VQ_Link_MemberOf_sp1"/> </ReportCollection> In comparison to the <ReportCollection> element for reports that return entities, the <ReportCollection> element for link reports has different features. The element itself contains extra attributes that precisely specify the items that the reports return: Attribute End1TypeId LinkTypeId End2TypeId End2TypeCognosPromptName Description The identifier from the i2 Analyze schema for the entity type at the "from" end of the link in the structure for which the report collection is intended. The identifier from the i2 Analyze schema for the link type in the structure for which the report collection is intended. The identifier from the i2 Analyze schema for the entity type at the "to" end of the link in the structure for which the report collection is intended. This value is used by analytics for conditional rendering of page objects. For example, if a link type can have more than one end type, the value for End2TypeCognosPromptName specifies the filter that is used to visualize the data for the specified end type. Going live to Enterprise Insight Analysis users 17

22 Supported filter operators The third section of the XML file that translates requests from i2 Analyze into a form that is compatible with Cognos is a list of operators for search conditions. The presence of an operator in the list determines whether users can specify that operator when they search the Information Store. The <SupportedFilterOperators> element has no attributes and the only child elements are <FilterOperator> elements that take values from the FilterOperator enumeration in the i2 Analyze API. In the translation file for most Enterprise Insight Analysis deployments, the <SupportedFilterOperators> element is similar to the following example: <SupportedFilterOperators> <FilterOperator>STARTS_WITH</FilterOperator> <FilterOperator>EQUAL_TO</FilterOperator> <FilterOperator>GREATER_THAN</FilterOperator> <FilterOperator>GREATER_THAN_OR_EQUAL_TO</FilterOperator> <FilterOperator>LESS_THAN</FilterOperator> <FilterOperator>LESS_THAN_OR_EQUAL_TO</FilterOperator> <FilterOperator>BETWEEN</FilterOperator> </SupportedFilterOperators> Although the "smart match" operator is included in the FilterOperator enumeration in the API, Enterprise Insight Analysis does not support this operator. If you remove a <FilterOperator> element, then users cannot select that operator in the conditions for all searches of the Information Store. You cannot enable and disable specific operators for individual item types. Report results translation file The report results translation file contains the grade information that can be assigned to properties. Grade information The <Grades> element specifies the grades that users can assign to properties. Each <Grade> child element has attributes that set the identifier and value of a grade to be assigned: <Grades> <Grade GradeTypeId="..." Value="..."/>... </Grades> If the i2 Analyze schema defines mandatory grades, then you must ensure that those grades receive values in the translation file. Otherwise, the grade information in the translation file is optional, just as it is for users of i2 Analyze. Creating a translation from i2 Analyze requests to Cognos reports After you create the IBM i2 Analyze schema and IBM Cognos Business Intelligence reports for your deployment of IBM i2 Enterprise Insight Analysis, then you can create the translation files. As you do so, you might discover that extra or modified Cognos reports are necessary. 18 Configuring a deployment before going live

23 Before you begin This procedure assumes that you have created all the Cognos reports that return data to IBM i2 Analyze from the Information Store. The translation file that you create here converts i2 Analyze requests into calls to Cognos reports. The Enterprise Insight Analysis Integrated Components include tools that generate template translation files from an i2 Analyze schema. The tools are supported on Windows operating systems only. Before you start creating your file, download Enterprise Insight Analysis Integrated Components and i2 Analyze Ensure that the i2 Analyze schema file you intend to use is available. The Enterprise Insight Analysis Integrated Components include example translation files that are named ELPQueryToReportTranslation.xml and ReportResultsToELPTranslation.xml. After you merge the toolkit files, the example translation files are in the i2analyze\toolkit\configuration\fragments\cognosconnector\web-inf\classes directory. About this task Use the translation file generation tool to generate template translation files for your i2 Analyze schema. Update the translation files with specific values for your deployment, then deploy the files. Procedure 1. Install IBM i2 Analyze. For more information, see Installing IBM i2 Analyze. 2. Install the IBM i2 Enterprise Insight Analysis Integrated Components. For more information, seeinstalling the IBM i2 Enterprise Insight Analysis Integrated Components. 3. Navigate to the utilities directory in the extracted contents of the Enterprise Insight Analysis Integrated Components. 4. Merge the contents of the utilities directory into the i2analyze/toolkit directory. Where duplicate files exist, overwrite the existing i2 Analyze files with the new Enterprise Insight Analysis files. 5. Using a text editor, open the i2analyze\toolkit\scripts\ TemplateGenerationTools.properties file. Populate the value of the SchemaFilePath property with the full path, including the file name, to the i2 Analyze schema file for which you want to generate a translation file. The Enterprise Insight Analysis Integrated Components include an example i2 Analyze schema named example-schema.xml. After you merge the toolkit files, the schema is located in the i2analyze\toolkit\configuration\fragments\ common\web-inf\classes directory. 6. Set the values of the ELPTranslationFilePath property to the full path, including the file name, for the translation file to generate. 7. Optional: If the i2 Analyze schema contains item types that are not present in your data and that you do not want to include in the translation files, populate the value of the ItemTypesToIgnore property with the item type IDs to exclude. 8. Open a command prompt with administrative privileges, navigate to the i2analyze\toolkit\scripts directory, and enter the following command to run the translation file generation tool: generatetranslationfiles.bat TemplateGenerationTools.properties Going live to Enterprise Insight Analysis users 19

IBM. IBM i2 Analyze Security White Paper. Version 4 Release 1

IBM. IBM i2 Analyze Security White Paper. Version 4 Release 1 IBM IBM i2 Analyze Security White Paper Version 4 Release 1 Note Before using this information and the product it supports, read the information in Notices on page 19. This edition applies to version 4,

More information

Version 2 Release 1. IBM i2 Enterprise Insight Analysis Maintaining a deployment IBM

Version 2 Release 1. IBM i2 Enterprise Insight Analysis Maintaining a deployment IBM Version 2 Release 1 IBM i2 Enterprise Insight Analysis Maintaining a deployment IBM Note Before using this information and the product it supports, read the information in Notices on page 13. This edition

More information

IBM. IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns. Version 2 Release 1 BA

IBM. IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns. Version 2 Release 1 BA IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns Version 2 Release 1 IBM BA21-8475-00 Note Before using this information and the product it supports, read the information in Notices

More information

Version 2 Release 1. IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns IBM BA

Version 2 Release 1. IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns IBM BA Version 2 Release 1 IBM i2 Enterprise Insight Analysis Understanding the Deployment Patterns IBM BA21-8475-00 Note Before using this information and the product it supports, read the information in Notices

More information

Version 2 Release 2. IBM i2 Enterprise Insight Analysis Upgrade Guide IBM SC

Version 2 Release 2. IBM i2 Enterprise Insight Analysis Upgrade Guide IBM SC Version 2 Release 2 IBM i2 Enterprise Insight Analysis Upgrade Guide IBM SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 35. This edition

More information

IBM. IBM i2 Analyze Linux Deployment Guide. Version 4 Release 1 SC

IBM. IBM i2 Analyze Linux Deployment Guide. Version 4 Release 1 SC IBM IBM i2 Analyze Linux Deployment Guide Version 4 Release 1 SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 63. This edition applies

More information

IBM i2 Intelligence Analysis Platform Windows Deployment Guide

IBM i2 Intelligence Analysis Platform Windows Deployment Guide IBM i2 Intelligence Analysis Platform Windows Deployment Guide Version 3 Release 0 SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 71.

More information

IBM. IBM i2 Enterprise Insight Analysis User Guide. Version 2 Release 1

IBM. IBM i2 Enterprise Insight Analysis User Guide. Version 2 Release 1 IBM IBM i2 Enterprise Insight Analysis User Guide Version 2 Release 1 Note Before using this information and the product it supports, read the information in Notices on page 19. This edition applies to

More information

IBM i2 Analyze ibase Connector Deployment Guide. Version 4 Release 1 IBM

IBM i2 Analyze ibase Connector Deployment Guide. Version 4 Release 1 IBM IBM i2 Analyze ibase Connector Deployment Guide Version 4 Release 1 IBM This edition applies to version 4, release 1, modification 4 of IBM i2 Analyze (product number 5725-G22) and to all subsequent releases

More information

Version 4 Release 1. IBM i2 Analyze Information Store Data Ingestion Guide IBM

Version 4 Release 1. IBM i2 Analyze Information Store Data Ingestion Guide IBM Version 4 Release 1 IBM i2 Analyze Information Store Data Ingestion Guide IBM Note Before you use this information and the product that it supports, read the information in Notices on page 41. This edition

More information

IBM i2 Analyze Information Store Data Ingestion Guide. Version 4 Release 1 IBM

IBM i2 Analyze Information Store Data Ingestion Guide. Version 4 Release 1 IBM IBM i2 Analyze Information Store Data Ingestion Guide Version 4 Release 1 IBM Note Before using this information and the product it supports, read the information in Notices on page 35. This edition applies

More information

IBM. IBM i2 Analyze Data Acquisition Guide. Version 4 Release 0

IBM. IBM i2 Analyze Data Acquisition Guide. Version 4 Release 0 IBM IBM i2 Analyze Data Acquisition Guide Version 4 Release 0 Note Before using this information and the product it supports, read the information in Notices on page 29. This edition applies to version

More information

Version 2 Release 2. IBM i2 Enterprise Insight Analysis Installing the components IBM SC

Version 2 Release 2. IBM i2 Enterprise Insight Analysis Installing the components IBM SC Version 2 Release 2 IBM i2 Enterprise Insight Analysis Installing the components IBM SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page

More information

Version 4 Release 1. IBM i2 Enterprise Insight Analysis Data Model White Paper IBM

Version 4 Release 1. IBM i2 Enterprise Insight Analysis Data Model White Paper IBM Version 4 Release 1 IBM i2 Enterprise Insight Analysis Data Model White Paper IBM Note Before using this information and the product it supports, read the information in Notices on page 11. This edition

More information

IBM. IBM i2 Analyze Deployment patterns and examples. Version 4 Release 1 SC

IBM. IBM i2 Analyze Deployment patterns and examples. Version 4 Release 1 SC IBM IBM i2 Analyze Deployment patterns and examples Version 4 Release 1 SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 25. This edition

More information

IBM Case Manager Version User's Guide IBM SC

IBM Case Manager Version User's Guide IBM SC IBM Case Manager Version 5.3.3 User's Guide IBM SC19-3274-10 IBM Case Manager Version 5.3.3 User's Guide IBM SC19-3274-10 This edition applies to Version 5 Release 3 Modification 3 of IBM Case Manager

More information

Version 9 Release 0. IBM i2 Analyst's Notebook Configuration IBM

Version 9 Release 0. IBM i2 Analyst's Notebook Configuration IBM Version 9 Release 0 IBM i2 Analyst's Notebook Configuration IBM Note Before using this information and the product it supports, read the information in Notices on page 11. This edition applies to version

More information

Oracle. Service Cloud Knowledge Advanced Implementation Guide

Oracle. Service Cloud Knowledge Advanced Implementation Guide Oracle Service Cloud Knowledge Advanced Implementation Guide Release November 2016 Oracle Service Cloud Part Number: E80590-02 Copyright 2015, 2016, Oracle and/or its affiliates. All rights reserved Authors:

More information

IBM. IBM i2 Enterprise Insight Analysis Advanced Edition Example Deployment. Version 2 Release 1

IBM. IBM i2 Enterprise Insight Analysis Advanced Edition Example Deployment. Version 2 Release 1 IBM IBM i2 Enterprise Insight Analysis Advanced Edition Example Deployment Version 2 Release 1 Note Before using this information and the product it supports, read the information in Notices on page 31.

More information

Version 9 Release 0. IBM i2 Analyst's Notebook Premium Configuration IBM

Version 9 Release 0. IBM i2 Analyst's Notebook Premium Configuration IBM Version 9 Release 0 IBM i2 Analyst's Notebook Premium Configuration IBM Note Before using this information and the product it supports, read the information in Notices on page 11. This edition applies

More information

IBM InfoSphere Information Server Version 8 Release 7. Reporting Guide SC

IBM InfoSphere Information Server Version 8 Release 7. Reporting Guide SC IBM InfoSphere Server Version 8 Release 7 Reporting Guide SC19-3472-00 IBM InfoSphere Server Version 8 Release 7 Reporting Guide SC19-3472-00 Note Before using this information and the product that it

More information

Talend Open Studio for MDM Web User Interface. User Guide 5.6.2

Talend Open Studio for MDM Web User Interface. User Guide 5.6.2 Talend Open Studio for MDM Web User Interface User Guide 5.6.2 Talend Open Studio for MDM Web User Interface Adapted for v5.6.2. Supersedes previous releases. Publication date: May 12, 2015 Copyleft This

More information

ER/Studio Enterprise Portal User Guide

ER/Studio Enterprise Portal User Guide ER/Studio Enterprise Portal 1.1.1 User Guide Copyright 1994-2009 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights

More information

IBM. IBM i2 Analyze Windows Upgrade Guide. Version 4 Release 1 SC

IBM. IBM i2 Analyze Windows Upgrade Guide. Version 4 Release 1 SC IBM IBM i2 Analyze Windows Upgrade Guide Version 4 Release 1 SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 19. This edition applies

More information

IBM FileNet Business Process Framework Version 4.1. Explorer Handbook GC

IBM FileNet Business Process Framework Version 4.1. Explorer Handbook GC IBM FileNet Business Process Framework Version 4.1 Explorer Handbook GC31-5515-06 IBM FileNet Business Process Framework Version 4.1 Explorer Handbook GC31-5515-06 Note Before using this information and

More information

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide IBM Internet Security Systems IBM Proventia Management SiteProtector Policies and Responses Configuration Guide Version2.0,ServicePack8.1 Note Before using this information and the product it supports,

More information

IBM Campaign Version-independent Integration with IBM Engage Version 1 Release 3.1 April 07, Integration Guide IBM

IBM Campaign Version-independent Integration with IBM Engage Version 1 Release 3.1 April 07, Integration Guide IBM IBM Campaign Version-independent Integration with IBM Engage Version 1 Release 3.1 April 07, 2017 Integration Guide IBM Note Before using this information and the product it supports, read the information

More information

IBM i2 Intelligence Analysis Platform Windows Deployment Guide

IBM i2 Intelligence Analysis Platform Windows Deployment Guide IBM i2 Intelligence Analysis Platform Windows Deployment Guide Version 3 Release 0 SC27-5091-00 Note Before using this information and the product it supports, read the information in Notices on page 69.

More information

Coveo Platform 7.0. Liferay Connector Guide

Coveo Platform 7.0. Liferay Connector Guide Coveo Platform 7.0 Liferay Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market

More information

Version 4 Release 1. IBM i2 Analyze Release Notes IBM

Version 4 Release 1. IBM i2 Analyze Release Notes IBM Version 4 Release 1 IBM i2 Analyze Release Notes IBM Note Before using this information and the product it supports, read the information in Notices on page 17. This edition applies to version 4, release

More information

Vector Issue Tracker and License Manager - Administrator s Guide. Configuring and Maintaining Vector Issue Tracker and License Manager

Vector Issue Tracker and License Manager - Administrator s Guide. Configuring and Maintaining Vector Issue Tracker and License Manager Vector Issue Tracker and License Manager - Administrator s Guide Configuring and Maintaining Vector Issue Tracker and License Manager Copyright Vector Networks Limited, MetaQuest Software Inc. and NetSupport

More information

Integrating Sintelix and ANB. Learn how to access and explore Sintelix networks in IBM i2 Analyst s Notebook

Integrating Sintelix and ANB. Learn how to access and explore Sintelix networks in IBM i2 Analyst s Notebook Integrating Sintelix and ANB Learn how to access and explore Sintelix networks in IBM i2 Analyst s Notebook 2 Integrating Sintelix and ANB By the end of this tutorial you will know how to: 1 2 3 Install

More information

Business Insight Authoring

Business Insight Authoring Business Insight Authoring Getting Started Guide ImageNow Version: 6.7.x Written by: Product Documentation, R&D Date: August 2016 2014 Perceptive Software. All rights reserved CaptureNow, ImageNow, Interact,

More information

THIS IS AN OBSOLETE COPYRIGHT PAGE. Use Common/Copyright/Copyright

THIS IS AN OBSOLETE COPYRIGHT PAGE. Use Common/Copyright/Copyright Unica Marketing Operations and Unica Campaign Version 8.2.0 Integration Guide Publication Date: September 20, 2010 Copyright THIS IS AN OBSOLETE COPYRIGHT PAGE. Use Common/Copyright/Copyright Table of

More information

IBM emessage Version 9 Release 1 February 13, User's Guide

IBM emessage Version 9 Release 1 February 13, User's Guide IBM emessage Version 9 Release 1 February 13, 2015 User's Guide Note Before using this information and the product it supports, read the information in Notices on page 471. This edition applies to version

More information

Coveo Platform 7.0. Yammer Connector Guide

Coveo Platform 7.0. Yammer Connector Guide Coveo Platform 7.0 Yammer Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market conditions,

More information

Central Administration Console Installation and User's Guide

Central Administration Console Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Central Administration Console Installation and User's Guide SC27-2808-03 IBM Tivoli Storage Manager FastBack for Workstations Version

More information

Composer Guide for JavaScript Development

Composer Guide for JavaScript Development IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development GI13-2630-00 IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development

More information

IBM BigFix Version 9.5. WebUI Administrators Guide IBM

IBM BigFix Version 9.5. WebUI Administrators Guide IBM IBM BigFix Version 9.5 WebUI Administrators Guide IBM IBM BigFix Version 9.5 WebUI Administrators Guide IBM Note Before using this information and the product it supports, read the information in Notices

More information

VMware AirWatch Database Migration Guide A sample procedure for migrating your AirWatch database

VMware AirWatch Database Migration Guide A sample procedure for migrating your AirWatch database VMware AirWatch Database Migration Guide A sample procedure for migrating your AirWatch database For multiple versions Have documentation feedback? Submit a Documentation Feedback support ticket using

More information

Coveo Platform 6.5. Liferay Connector Guide

Coveo Platform 6.5. Liferay Connector Guide Coveo Platform 6.5 Liferay Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market

More information

Service Cloud Knowledge Advanced Implementation Guide Release 17D

Service Cloud Knowledge Advanced Implementation Guide Release 17D Oracle Service Cloud Knowledge Advanced Implementation Guide Release 17D Oracle Service Cloud Part Number: E89237-01 Copyright 2015, 2016, 2017, Oracle and/or its affiliates. All rights reserved Authors:

More information

Coveo Platform 7.0. Atlassian Confluence Connector Guide

Coveo Platform 7.0. Atlassian Confluence Connector Guide Coveo Platform 7.0 Atlassian Confluence Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing

More information

ER/Studio Enterprise Portal User Guide

ER/Studio Enterprise Portal User Guide ER/Studio Enterprise Portal 1.0.3 User Guide Copyright 1994-2009 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights

More information

Geocortex Workflow Tutorial Create the Search Schools Workflow

Geocortex Workflow Tutorial Create the Search Schools Workflow Geocortex Workflow Tutorial Create the Search Schools Workflow July-2011 www.geocortex.com/essentials Latitude Geographics Group Ltd. 200-1117 Wharf St, Victoria, BC V8W 1T7 Canada Tel: (250) 381-8130

More information

IBM Operational Decision Manager Version 8 Release 5. Configuring Operational Decision Manager on WebLogic

IBM Operational Decision Manager Version 8 Release 5. Configuring Operational Decision Manager on WebLogic IBM Operational Decision Manager Version 8 Release 5 Configuring Operational Decision Manager on WebLogic Note Before using this information and the product it supports, read the information in Notices

More information

IBM Atlas Policy Distribution Administrators Guide: IER Connector. for IBM Atlas Suite v6

IBM Atlas Policy Distribution Administrators Guide: IER Connector. for IBM Atlas Suite v6 IBM Atlas Policy Distribution Administrators Guide: IER Connector for IBM Atlas Suite v6 IBM Atlas Policy Distribution: IER Connector This edition applies to version 6.0 of IBM Atlas Suite (product numbers

More information

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide Note Before using this information and the product it supports,

More information

Quark XML Author October 2017 Update for Platform with Business Documents

Quark XML Author October 2017 Update for Platform with Business Documents Quark XML Author 05 - October 07 Update for Platform with Business Documents Contents Getting started... About Quark XML Author... Working with the Platform repository...3 Creating a new document from

More information

IBM Operational Decision Manager Version 8 Release 5. Tutorial: Getting started with the Decision Center Enterprise console

IBM Operational Decision Manager Version 8 Release 5. Tutorial: Getting started with the Decision Center Enterprise console IBM Operational Decision Manager Version 8 Release 5 Tutorial: Getting started with the Decision Center Enterprise console Note Before using this information and the product it supports, read the information

More information

Version Installation and User Guide

Version Installation and User Guide IBM Cognos 8 Business Intelligence Map Manager Version 8.4.1 Installation and User Guide Product Information This document applies to IBM Cognos 8 Version 8.4.1 and may also apply to subsequent releases.

More information

User Guide Product Design Version 1.7

User Guide Product Design Version 1.7 User Guide Product Design Version 1.7 1 INTRODUCTION 3 Guide 3 USING THE SYSTEM 4 Accessing the System 5 Logging In Using an Access Email 5 Normal Login 6 Resetting a Password 6 Logging Off 6 Home Page

More information

Oracle. Service Cloud Configuring Knowledge Advanced

Oracle. Service Cloud Configuring Knowledge Advanced Oracle Service Cloud Release August 2016 Oracle Service Cloud Part Number: Part Number E77680-03 Copyright 2015, 2016, Oracle and/or its affiliates. All rights reserved Authors: The Knowledge Information

More information

IBM Optim. Compare Introduction. Version7Release3

IBM Optim. Compare Introduction. Version7Release3 IBM Optim Compare Introduction Version7Release3 IBM Optim Compare Introduction Version7Release3 Note Before using this information and the product it supports, read the information in Notices on page

More information

Coveo Platform 7.0. Oracle UCM Connector Guide

Coveo Platform 7.0. Oracle UCM Connector Guide Coveo Platform 7.0 Oracle UCM Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market

More information

Release Notes. IBM Tivoli Identity Manager Universal Provisioning Adapter. Version First Edition (June 14, 2010)

Release Notes. IBM Tivoli Identity Manager Universal Provisioning Adapter. Version First Edition (June 14, 2010) IBM Tivoli Identity Manager Version 5.1.2 First Edition (June 14, 2010) This edition applies to version 5.1 of Tivoli Identity Manager and to all subsequent releases and modifications until otherwise indicated

More information

Quark XML Author September 2016 Update for Platform with Business Documents

Quark XML Author September 2016 Update for Platform with Business Documents Quark XML Author 05 - September 06 Update for Platform with Business Documents Contents Getting started... About Quark XML Author... Working with the Platform repository... Creating a new document from

More information

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5

Guide to Migrating to IBM InfoSphere Information Server, Version 8.5 IBM InfoSphere Information Server Version 8 Release 5 Guide to Migrating to IBM InfoSphere Information Server, Version 8.5 SC19-2965-00 IBM InfoSphere Information Server Version 8 Release 5 Guide to Migrating

More information

One Identity Active Roles 7.2. Azure AD and Office 365 Management Administrator Guide

One Identity Active Roles 7.2. Azure AD and Office 365 Management Administrator Guide One Identity Active Roles 7.2 Azure AD and Office 365 Management Administrator Copyright 2017 One Identity LLC. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright.

More information

IBM Records Manager Version 8.5. Designing a DoD Compliant Solution

IBM Records Manager Version 8.5. Designing a DoD Compliant Solution IBM Records Manager Version 8.5 Designing a DoD 5015.02 Compliant Solution IBM Records Manager Version 8.5 Designing a DoD 5015.02 Compliant Solution Note Before using this information and the product

More information

CollabNet Desktop - Microsoft Windows Edition

CollabNet Desktop - Microsoft Windows Edition CollabNet Desktop - Microsoft Windows Edition User Guide 2009 CollabNet Inc. CollabNet Desktop - Microsoft Windows Edition TOC 3 Contents Legal fine print...7 CollabNet, Inc. Trademark and Logos...7 Chapter

More information

IBM Decision Server Insights. Installation Guide. Version 8 Release 6

IBM Decision Server Insights. Installation Guide. Version 8 Release 6 IBM Decision Server Insights Installation Guide Version 8 Release 6 IBM Decision Server Insights Installation Guide Version 8 Release 6 Note Before using this information and the product it supports,

More information

Coveo Platform 7.0. Alfresco One Connector Guide

Coveo Platform 7.0. Alfresco One Connector Guide Coveo Platform 7.0 Alfresco One Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market

More information

Guide to Managing Common Metadata

Guide to Managing Common Metadata IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01 IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01

More information

IBM BigFix Version 9.5. WebUI Administrators Guide IBM

IBM BigFix Version 9.5. WebUI Administrators Guide IBM IBM BigFix Version 9.5 WebUI Administrators Guide IBM IBM BigFix Version 9.5 WebUI Administrators Guide IBM Note Before using this information and the product it supports, read the information in Notices

More information

Coveo Platform 7.0. Atlassian Confluence V2 Connector Guide

Coveo Platform 7.0. Atlassian Confluence V2 Connector Guide Coveo Platform 7.0 Atlassian Confluence V2 Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to

More information

EnterpriseTrack Reporting Data Model Configuration Guide Version 17

EnterpriseTrack Reporting Data Model Configuration Guide Version 17 EnterpriseTrack EnterpriseTrack Reporting Data Model Configuration Guide Version 17 October 2018 Contents About This Guide... 5 Configuring EnterpriseTrack for Reporting... 7 Enabling the Reporting Data

More information

SDL Content Porter 2013 User Manual. Content Management Technologies Division of SDL

SDL Content Porter 2013 User Manual. Content Management Technologies Division of SDL SDL Content Porter 2013 User Manual Content Management Technologies Division of SDL Revision date: 28-03-2013 Copyright 1999-2013 SDL Tridion Development Lab B.V. All rights reserved. No part of this documentation

More information

Version 9 Release 0. IBM i2 Analyst's Notebook Premium Release Notes IBM

Version 9 Release 0. IBM i2 Analyst's Notebook Premium Release Notes IBM Version 9 Release 0 IBM i2 Analyst's Notebook Premium Release Notes IBM Note Before using this information and the product it supports, read the information in Notices on page 11. This edition applies

More information

The Connector Version 2.0 Microsoft Project to Atlassian JIRA Connectivity

The Connector Version 2.0 Microsoft Project to Atlassian JIRA Connectivity The Connector Version 2.0 Microsoft Project to Atlassian JIRA Connectivity User Manual Ecliptic Technologies, Inc. Copyright 2011 Page 1 of 99 What is The Connector? The Connector is a Microsoft Project

More information

User Scripting April 14, 2018

User Scripting April 14, 2018 April 14, 2018 Copyright 2013, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and

More information

IBM TRIRIGA Application Platform Version 3 Release 4.2. Object Migration User Guide

IBM TRIRIGA Application Platform Version 3 Release 4.2. Object Migration User Guide IBM TRIRIGA Application Platform Version 3 Release 4.2 Object Migration User Guide Note Before using this information and the product it supports, read the information in Notices on page 41. This edition

More information

Enterprise Data Catalog for Microsoft Azure Tutorial

Enterprise Data Catalog for Microsoft Azure Tutorial Enterprise Data Catalog for Microsoft Azure Tutorial VERSION 10.2 JANUARY 2018 Page 1 of 45 Contents Tutorial Objectives... 4 Enterprise Data Catalog Overview... 5 Overview... 5 Objectives... 5 Enterprise

More information

Extended Search Administration

Extended Search Administration IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 Note! Before using

More information

Quark XML Author for FileNet 2.8 with BusDocs Guide

Quark XML Author for FileNet 2.8 with BusDocs Guide Quark XML Author for FileNet.8 with BusDocs Guide Contents Getting started... About Quark XML Author... System setup and preferences... Logging on to the repository... Specifying the location of checked-out

More information

SAS Model Manager 2.2. Tutorials

SAS Model Manager 2.2. Tutorials SAS Model Manager 2.2 Tutorials The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009. SAS Model Manager 2.2: Tutorials. Cary, NC: SAS Institute Inc. SAS Model Manager

More information

Release Notes. IBM Tivoli Identity Manager GroupWise Adapter. Version First Edition (September 13, 2013)

Release Notes. IBM Tivoli Identity Manager GroupWise Adapter. Version First Edition (September 13, 2013) Release Notes IBM Tivoli Identity Manager GroupWise Adapter Version 5.1.5 First Edition (September 13, 2013) This edition applies to version 5.1 of Tivoli Identity Manager and to all subsequent releases

More information

Understanding Advanced Workflow

Understanding Advanced Workflow IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 Note Before

More information

ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE SERVICE PACK 1 PART NO. E

ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE SERVICE PACK 1 PART NO. E ORACLE USER PRODUCTIVITY KIT USAGE TRACKING ADMINISTRATION & REPORTING RELEASE 3.6.1 SERVICE PACK 1 PART NO. E17383-01 MARCH 2010 COPYRIGHT Copyright 1998, 2010, Oracle and/or its affiliates. All rights

More information

Workflow Templates in Compliance 360 Version 2018

Workflow Templates in Compliance 360 Version 2018 Workflow Templates in Compliance 360 Version 2018 Workflow Templates 5 Workflow Elements 6 Workflow Teams 6 Workflow Template Changes 6 Create or Edit a Workflow Template 8 Import and Export Workflow Templates

More information

IBM BigFix Compliance PCI Add-on Version 9.5. Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM

IBM BigFix Compliance PCI Add-on Version 9.5. Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM IBM BigFix Compliance PCI Add-on Version 9.5 Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM IBM BigFix Compliance PCI Add-on Version 9.5 Payment Card Industry Data Security Standard

More information

Information Catalog Center Administration Guide

Information Catalog Center Administration Guide IBM DB2 Warehouse Manager Information Catalog Center Administration Guide Version 8 SC27-1125-00 IBM DB2 Warehouse Manager Information Catalog Center Administration Guide Version 8 SC27-1125-00 Before

More information

CA GovernanceMinder. CA IdentityMinder Integration Guide

CA GovernanceMinder. CA IdentityMinder Integration Guide CA GovernanceMinder CA IdentityMinder Integration Guide 12.6.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation

More information

Understanding Modelpedia Authorization

Understanding Modelpedia Authorization With Holocentric Modeler and Modelpedia Understanding Modelpedia Authorization V1.0/HUG003 Table of Contents 1 Purpose 3 2 Introduction 4 3 Roles 4 3.1 System Authority Roles... 5 3.2 Role Inclusion...

More information

About the P6 EPPM Importing and Exporting Guide

About the P6 EPPM Importing and Exporting Guide P6 EPPM Importing and Exporting Guide October 2018 Contents About the P6 EPPM Importing and Exporting Guide Scope This guide contains information about import and export formats and the process of importing

More information

ForeScout Extended Module for IBM BigFix

ForeScout Extended Module for IBM BigFix ForeScout Extended Module for IBM BigFix Version 1.0.0 Table of Contents About this Integration... 4 Use Cases... 4 Additional BigFix Documentation... 4 About this Module... 4 Concepts, Components, Considerations...

More information

IBM Spectrum LSF Process Manager Version 10 Release 1. Release Notes IBM GI

IBM Spectrum LSF Process Manager Version 10 Release 1. Release Notes IBM GI IBM Spectrum LSF Process Manager Version 10 Release 1 Release Notes IBM GI13-1891-04 IBM Spectrum LSF Process Manager Version 10 Release 1 Release Notes IBM GI13-1891-04 Note Before using this information

More information

IBM Security Identity Manager Version Planning Topics IBM

IBM Security Identity Manager Version Planning Topics IBM IBM Security Identity Manager Version 7.0.1 Planning Topics IBM IBM Security Identity Manager Version 7.0.1 Planning Topics IBM ii IBM Security Identity Manager Version 7.0.1: Planning Topics Table of

More information

Workbench User's Guide

Workbench User's Guide IBM Initiate Workbench User's Guide Version9Release7 SC19-3167-06 IBM Initiate Workbench User's Guide Version9Release7 SC19-3167-06 Note Before using this information and the product that it supports,

More information

Teiid Designer User Guide 7.5.0

Teiid Designer User Guide 7.5.0 Teiid Designer User Guide 1 7.5.0 1. Introduction... 1 1.1. What is Teiid Designer?... 1 1.2. Why Use Teiid Designer?... 2 1.3. Metadata Overview... 2 1.3.1. What is Metadata... 2 1.3.2. Editing Metadata

More information

IBM i Version 7.2. Connecting to your system Connecting to Your system with IBM Navigator for i IBM

IBM i Version 7.2. Connecting to your system Connecting to Your system with IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to Your system with IBM Navigator for i IBM IBM i Version 7.2 Connecting to your system Connecting to Your system with IBM Navigator for i IBM Note

More information

Introduction to Security in Laserfiche 8.3 and later. White Paper

Introduction to Security in Laserfiche 8.3 and later. White Paper Introduction to Security in Laserfiche 8.3 and later White Paper November 2013 Table of Contents Authentication and Authorization... 4 Authentication... 4 Windows Accounts and LDAP... 5 Laserfiche Trustees...

More information

IBM Clinical Development

IBM Clinical Development IBM Clinical Development New User Help Effective: 26 January 2018 Copyright IBM corporation. 2017. IBM Clinical Development 2 TOPICS > > > Click the green icon to jump to the section or use the PDF page

More information

Coveo Platform 7.0. Microsoft Dynamics CRM Connector Guide

Coveo Platform 7.0. Microsoft Dynamics CRM Connector Guide Coveo Platform 7.0 Microsoft Dynamics CRM Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing

More information

cc: Discover QA Coaching Manual, v5.1 R1

cc: Discover QA Coaching Manual, v5.1 R1 cc: Discover QA Coaching Manual, v5.1 R1 March 2013 Reference Guide callcopy.com Security Classification: CallCopy Confidential. Distribution: Approved internal CallCopy staff only and licensed CallCopy

More information

IBM DB2 Query Patroller. Administration Guide. Version 7 SC

IBM DB2 Query Patroller. Administration Guide. Version 7 SC IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 Before using this information and the product it supports, be sure

More information

Connector for OpenText Content Server Setup and Reference Guide

Connector for OpenText Content Server Setup and Reference Guide Connector for OpenText Content Server Setup and Reference Guide Published: 2018-Oct-09 Contents 1 Content Server Connector Introduction 4 1.1 Products 4 1.2 Supported features 4 2 Content Server Setup

More information

Version 9 Release 1. IBM i2 Analyst's Notebook Premium Release Notes IBM

Version 9 Release 1. IBM i2 Analyst's Notebook Premium Release Notes IBM Version 9 Release 1 IBM i2 Analyst's Notebook Premium Release Notes IBM Note Before using this information and the product it supports, read the information in Notices on page 13. This edition applies

More information

IBM Campaign Version-independent Integration with IBM Watson Campaign Automation Version 1 Release 1.5 February, Integration Guide IBM

IBM Campaign Version-independent Integration with IBM Watson Campaign Automation Version 1 Release 1.5 February, Integration Guide IBM IBM Campaign Version-independent Integration with IBM Watson Campaign Automation Version 1 Release 1.5 February, 2018 Integration Guide IBM Note Before using this information and the product it supports,

More information

IBM i2 ibase 8 Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8 VERSION MAY 2012

IBM i2 ibase 8 Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8 VERSION MAY 2012 IBM i2 ibase 8 Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8 VERSION 8.9.1 MAY 2012 Note: Before using this information and the product it supports, read the information in Notices on page

More information