Dashboards are configurable pages that contain information useful to groups of users who fill various roles within your company. The components that make up dashboards are called portlets. Dashboards can contain pre-defined portlets or portlets that you create.
Topics in this section describe how to create and use custom portlets.
HCL® Marketing Platform provides security, configuration, notification, and dashboard features for IBM EMM products.
You can manage the attributes of user accounts created using HCL® Marketing Platform user interface, which we refer to as internal accounts. This is in contrast to external user accounts, which are imported from an external system such as an LDAP server or web access control system.
HCL® Marketing Platform supports roles and permissions to control user access to objects and features in IBM EMM applications.
When IBM® EMM is first installed, the Configuration page shows only the properties used to configure HCL Marketing Platform and some global configuration properties. When you install additional IBM EMM applications, the properties used to configure these applications are registered with Marketing Platform. These properties are then shown on the Configuration page, where you can set or modify their values.
To plan how your organization uses the dashboard feature, you should work with your marketing management team to decide the following details.
You can control who views your dashboards by associating them with groups or by assigning individual users to them. Members of a group can access the dashboard or dashboards associated with that group, while non-members cannot view these dashboards.
Dashboards allow IBM® EMM users to view pages from multiple products (such as Marketing Operations and Campaign) in a single page, regardless of the permissions that are configured for them within those products.
IBM® EMM provides two types of pre-defined dashboard portlets, which you can enable and then add to any dashboard you create.
IBM® EMM provides pre-assembled dashboards that include portlets appropriate for various audiences.
Reports are desirable components to add to dashboards because they add a visual element that makes it easy to scan large amounts of data. However, because reports require additional processing resources, performance can become an issue when many users access dashboards that contain many reports on a regular basis.
Topics in this section describe how to set up dashboards.
Quick links are pre-defined links to IBM® EMM products. Some quick links enable users to perform basic actions in the IBM EMM product within the dashboard, without navigating to the product. You can configure portlets that contain a set of quick links that you choose.
You can create portlets from the following types of IBM® EMM pages.
When you are planning to create portlets, you should keep in mind the following authentication considerations.
This section provides an overview of the steps for creating a portlet, which are described in detail elsewhere in this guide.
Use this procedure for reports in a Digital Analytics for On Premises installation.
The format of an IBM® Cognos® dashboard portlet URL is as follows.
Use this procedure for Digital Analytics reports.
Use this procedure for intranet or internet pages, including Digital Analytics for On Premises pages.
Before performing this procedure, you should have prepared a URL as described elsewhere in this section.
Refer to this table if you need help completing the fields on the Custom Portlet page.
Topics in this section describe how to manage dashboard membership.
The IBM® EMM Scheduler enables you to configure a process to run at intervals that you define.
HCL® Marketing Platform implements a SAML 2.0 based Identity Provider (IdP) that enables a single sign-on federation among HCL ExperienceOne products or between IBM ExperienceOne products and third party applications.
If your organization uses IBM® Digital Analytics, you can enable single sign-on between Digital Analytics and IBM EMM.
Marketing Platform can be configured to integrate with Windows™ Active Directory server or another LDAP (Lightweight Directory Access Protocol) server. By integrating IBM® EMM with a directory server, you can maintain users and groups in one centralized location. Integration provides a flexible model for extending the enterprise authorization policies into IBM EMM applications. Integration reduces support costs and the time needed to deploy an application in production.
Organizations use web access control platforms to consolidate their security systems, which provide a portal that regulates user access to web sites. This section provides an overview of IBM® EMM integration with web access control platforms.
HCL® Marketing Platform provides support for system alerts and user notifications sent by IBM EMM products.
This section describes one-way SSL in IBM® EMM.
Data filters make it possible to restrict the customer data that an IBM® EMM user can view and work with in IBM EMM applications. You can think of the data you secure with a data filter as a data set defined by the fields in your customer tables that you specify.
You can configure which audit events are tracked and assign a severity level to each tracked event.
You should check the system log first if the Marketing Platform application malfunctions. The system log is independent of the security audit information, which is stored in the system tables. While the system log tracks some of the same information contained in the security audit reports, it also contains information useful in troubleshooting Marketing Platform.
This section provides an overview of the Marketing Platform utilities, including some details that apply to all of the utilities and which are not included in the individual utility descriptions.
This section describes the configuration properties found on the Settings & Configuration page.
You can customize the appearance of the user interface where most IBM® EMM product pages appear. By editing a cascading style sheet and providing your own graphics, you can change many of the images, fonts, and colors in the user interface.
Use this procedure to add internal user accounts.
Use this procedure to delete internal user accounts.
Use this procedure to change password expiration dates for internal users.
Use this procedure to reset internal user passwords.
Use this procedure to add data sources for internal users.
Use this procedure to change data source passwords or login names.
Use this procedure to change the properties of internal user account.
Use this procedure to change the system status of internal users.
Use this procedure to delete internal user data sources.
Refer to this table if you need help completing the fields on the Users page.
You can set the locale for both internal and external users. This setting affects the display of language, time, numbers, and dates in IBM® EMM applications.
Marketing Platform contains a default locale attribute that applies to all IBM® EMM applications that implement it.
The restoreAccess utility allows you to restore access to Marketing Platform if all users with PlatformAdminRole privileges have been inadvertently locked out or if all ability to log in to the Marketing Platform has been lost.
In a multi-partition environment, at least one user account with the PlatformAdminRole role in Marketing Platform is required, to enable you to administer security for IBM® EMM users across all partitions.
When IBM® EMM is integrated with an external server (such as a supported LDAP server or a web access control system), it supports two types of groups: internal and external.
Partitions in Campaign and related products provide a way to secure the data associated with different groups of users. With partitioning, a user's partition appears as if it were a separate running instance of Campaign, with no indication that other partitions are running on the same system. This section describes special security management considerations in a multi-partition environment.
When IBM® EMM is first installed, three users are pre-configured and are assigned system-defined roles in Marketing Platform and Campaign, as described in this section.
Using Marketing Platform security administration features to manage user application access is a multi-step process. The following procedure provides an overview of the basic process, which is described in detail in the remainder of this guide.
Use this procedure to add an internal group.
Use this procedure to add an internal subgroup.
Remember, when you delete a group or subgroup, members of the group lose the roles assigned to that group, and any parents of that group also lose those role assignments, unless the roles are also explicitly assigned to the parents.
This procedure is necessary only if multiple partitions are configured for Campaign. Only an account with the PlatformAdminRole role, such as the platform_admin user, can perform this task.
Use this procedure to add a user to a group or subgroup.
Use this procedure to remove a user from a group or subgroup.
Use this procedure to change a group or subgroup description.
These are the fields you use to configure user groups.
You should create new roles only for products that have detailed permissions. The reporting function and some IBM® EMM products have only basic permissions available, so there is no need to create additional roles for these products.
Use this procedure to modify role premissions.
Use this procedure to remove a role from IBM® EMM.
If you add a role to a group or remove a role from a group, members of that group acquire or lose that role.
Use the Edit Roles window to assign a role to or to remove a role from a user.
For each role, you can specify which permissions are granted, not granted, or denied. You set these permissions on the Settings > User Roles & Permissions page.
The following table describes the functional definitions of the roles available for the IBM® EMM products that use only the basic roles. See the product documentation for additional information.
The following table describes the permissions you can assign to roles in Marketing Platform.
The following table describes permissions that you can assign to roles in Opportunity Detect.
The properties for an IBM® EMM application are registered with Marketing Platform when the application is installed. When an application requires users to create duplicate categories for configuration purposes, a category template is provided.
Use this procedure to create a category from a template on the Configuration page.
Use this procedure to navigate to a category on the Configuration page.
Use this procedure to modify a property value on the Configuration page.
Use this procedure to assign or change a dashboard administrator.
If you have been designated a dashboard administrator, you are responsible for managing the membership, layout, and content of that dashboard. This section describes how to manage dashboard membership.
Use this procedure to add a pre-defined portlet to a dashboard.
To schedule a dashboard report (either a pre-defined or user-created portlet), you must first create a view and schedule it, and then configure the portlet as described here.
If you are administering dashboards in a multi-partition environment, read this section to understand how multiple partitions affect dashboards.
Perform this task before you begin to create dashboards. You should enable only those portlets that reference IBM® EMM products that you have installed.
Use this procedure to create a pre-assembled dashboard.
Use this procedure to grant or remove dashboard membership.
Refer to this table if you need help completing the fields in the Manage Portlets page.
Use this procedure to create a dashboard that is not pre-assembled
When you have multiple partitions configured, follow these guidelines when you set up dashboards.
Use this procedure create a quick link portlet.
Starting with the 8.0 release of Marketing Platform, the IBM® EMM Scheduler is intended to replace the Campaign Schedule process for scheduling runs of an entire flowchart. The IBM EMM Scheduler is more efficient, as it does not consume any server system resources when the flowchart is not actually running.
The IBM® EMM Scheduler can respond to triggers sent by an external application. The scheduler_console_client utility enables this feature. This utility issues triggers that can launch one or more schedules set up to listen for that trigger.
Jobs configured in the IBM® EMM Scheduler can be listed and kicked off by this utility, if they are set up to listen for a trigger.
Throttling is used to manage performance when a large number of processes are likely to place high demands on the system. Throttling is based on scheduler groups that you set up on the Settings > Configuration page. You assign a throttling threshold to a group, and associate schedules with that group.
You must set up a throttling group for each type of object being scheduled.
You can schedule runs to occur in the context of any one of a large number of worldwide time zones.
You can configure a schedule to run only when multiple other schedules have finished their runs by using the On Completion of Other Tasks option in the When to Start drop down list.
This section describes in detail the page you use when you create or edit a schedule.
You access the scheduler management pages by selecting Settings > Scheduled Tasks or by selecting View when Scheduled from a flowchart's Run menu.
You can manage all schedules from pages you can access by selecting Settings > Scheduled Tasks. You must have the Scheduler Tasks View permission in Marketing Platform to manage schedules.
Set configuration properties on the Settings > Configuration page to configure federated authentication in IBM® EMM.
The properties in this category are used in implementing SAML (Security Assertion Markup Language) 2.0 based federated authentication, which enables single sign-on among diverse applications.
The properties in this category are used in implementing SAML (Security Assertion Markup Language) 2.0 based federated authentication between IBM® EMM applications and other HCL and third party applications.
Use this procedure to set up single sign-on between IBM® EMM and Digital Analytics using automatic user account creation.
Perform the procedure below in the WebLogic domain where Marketing Platform is deployed to ensure that users can view Digital Analytics reports in dashboards without having to log in.
Perform the procedure below in WebSphere® cell and node where Marketing Platform is deployed to ensure that users can view Digital Analytics reports in dashboards without having to log in.
Use this procedure to set up single sign-on between IBM® EMM and Digital Analytics using manual user account creation.
To enable directory server integration in IBM® EMM, you must determine the Distinguished Name (DN) for a user and for groups. The DN of an object on the directory server is the complete path through the directory server tree structure to that object.
Obtain the required information about the directory server with which you want to integrate. You use this information during the configuration process, to store directory server credentials and to set configuration property values.
Use this configuration process roadmap to scan the tasks required to integrate IBM® EMM with Windows™ Active Directory. The Topic column provides links to the topics that describe the tasks in detail.
Use this procedure to force synchronization of users when IBM® EMM is integrated with an LDAP server or web access control system.
Marketing Platform integration with Windows™ Active Directory provides the features described in this section.
Use this configuration process roadmap to scan the tasks required to integrate IBM® EMM with LDAP. The Topic column provides links to the topics that describe the tasks in detail.
Marketing Platform integration with LDAP provides the features described in this section.
If your directory server does not allow anonymous access, you must configure an IBM® EMM user account to hold the user name and password of a directory server user, as described in the following procedure.
Properties in this category are used to configure LDAP integration.
LDAP login method properties specify connection details the system uses to connect to the directory server.
LDAP synchronization properties specify details that the system uses to log into the directory server and identify users to import. Some of these properties also control the frequency and other details of the automatic synchronization process.
These properties specify the user attributes that the system imports from the directory server.
Users who belong to the directory server groups you map here are imported and made members of the Marketing Platform group or groups specified here.
When Windows™ integrated login is enabled, you can not log in to IBM® EMM as platform_admin, so you must perform the following procedure in order to have administrator access to Marketing Platform.
The property in this category specifies the login mode for IBM® EMM products.
Set security mode properties to allow Active Directory users to access IBM® EMM applications based on their Windows™ login, bypassing the IBM EMM login screen.
Properties in this category are used to configure integration with web access control software.
Properties in this category specify values that are used internally to navigate among IBM® EMM products.
To configure web access control integration, you set some configuration properties.
Marketing Platform provides a utility, datafilteringScriptTool, that processes XML to create the data filters in the Marketing Platform system tables. Depending on how you write the XML, you can use this utility in two ways: automatic generation and manual specification.
Jim needs to create a set of data filters based on sales territories.
Jim needs to create a set of data filters based on countries, cities, and states.
The datafilteringScriptTool utility reads an XML file to populate the data filtering tables in the Marketing Platform system table database.
The ManagerSchema_PurgeDataFiltering.sql script removes all data filtering data from the Marketing Platform system tables without removing the data filter tables themselves. This script removes all data filters, data filter configurations, audiences, and data filter assignments from Marketing Platform.
Run the datafilteringScriptTool utility, which uses your XML to populate the data filter system tables.
Create the XML file that specifies the customer data used as criteria in each data filter. In the next step you will run a utility that populates the system tables with these specifications.
This section describes the XML elements for which you must provide values.
Set required configuration properties to enable data filtering.
You can turn the data filter cache on for better performance.
Properties in this category specify values used when data filtering is implemented.
You have two options for assigning users and groups to data filters: through the user interface or in the XML you use to create the data filters. Assigning users in the XML is a useful method when you have many users, each of whom requires a separate filter.
If you do not assign users or groups within the XML that you create, use the IBM® EMM data filter user interface to perform searches for users, groups, and data filters and then select items from the search results and assign them.
You can assign users or groups to data filters in the XML, as an alternative to doing this through the user interface. Assigning users and groups to data filters in the XML is available only when you use manual specification to create the data filters.
You can assign users and groups to data filters on the Settings > Data Filters pages.
You can set up notifications for any schedule, to alert you to the status of scheduled runs. In addition, users with Administrator permissions in Marketing Platform can set up groups to which notifications are sent.
Follow this procedure to configure the Marketing Platform to send system alert and notification emails to users. You must have an email server set up before you start.
Properties in this category are used to configure the Marketing Platform to send emails to users for system alerts and notifications.
Properties in this category control system behavior for notifications that IBM® EMM products can send to users.
On every application server on which an IBM® EMM application is deployed, configure the web application server to use the certificates you have decided to employ.
Many HCL® application components can act as both server and client during normal operations, and some HCL components are written in Java™ and some in C++. These facts determine the format of the certificates you use. You specify the format when you create a self-signed certificate of purchase one from a CA.
Follow this procedure to configure SSL in Marketing Platform.
When Marketing Platform is deployed with SSL and you plan to use the data filtering feature, you must perform this procedure to add the SSL options that perform hand shaking.
To specify the audit events that are available in the audit report and their severity, you set properties on the Settings > Configuration page.
The property on this page determines whether audit events are tracked.
The events you select on this page are available in the security audit reports.
The severity level you specify for each event on this page appears in the Audit Events report. You can use the severity level to sort and filter the report data. The events are identical to those in the IBM Marketing Platform | Audit Events | Audit Events Configuration category.
You can configure backups of audit events by setting the value of configuration properties in the IBM Marketing Platform | Audit Events | Audit Events Configuration category on the Settings > Configuration page.
To notify users of the status of audit event backup, make them members of a group that you specify in a configuration property.
You can add and remove events and columns, rearrange and sort the columns, set the time span, specify which tracked events are shown in the report, and filter the information.
Use the fields on the Report Parameters page to configure the way the audit report is displayed.
The properties and values on the Configuration page are stored in the Marketing Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.
The Configuration page provides access to the central configuration properties for IBM® EMM applications.
The encryptPasswords utility is used to encrypt and store either of two passwords that Marketing Platform uses internally.
Partitions are associated with Campaign policies and roles. These policies and roles and their partition associations are stored in the Marketing Platform system tables. The partitionTool utility seeds the Marketing Platform system tables with basic policy and role information for partitions.
The populateDb utility inserts default (seed) data in the Marketing Platform system tables.
The Manager_Schema_DeleteAll.sql script removes all data from the Marketing Platform system tables without removing the tables themselves. This script removes all users, groups, security credentials, data filters, and configuration settings from Marketing Platform.
Use the scripts described in the following table to create Marketing Platform system tables manually, when your company policy does not allow you to use the installer to create them automatically.
The ManagerSchema_DropAll.sql script removes all Marketing Platform system tables from a database. This script removes all tables, users, groups, security credentials, and configuration settings from Marketing Platform.
Follow these guidelines to create your corporate theme for the IBM® EMM frameset.
Follow this procedure to apply your corporate theme to the IBM® EMM user interface.