Embed Size (px)
Citation preview
Informatica® Cloud Data IntegrationSummer 2018
Marketo Connector Guide
Informatica Cloud Data Integration Marketo Connector GuideSummer 2018October 2017
© Copyright Informatica LLC 2015, 2018
This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC.
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License.
Informatica, the Informatica logo, Informatica Cloud, and PowerCenter are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html. Other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product.
See patents at https://www.informatica.com/legal/patents.html.
DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at [email protected].
Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT.
Publication Date: 2018-10-24
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Informatica Intelligent Cloud Services Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Data Integration connector documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Intelligent Cloud Services trust site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2: Marketo Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 3: Supported Objects and Task Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . 9Rules and Guidelines for Using the Activity Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Rules and Guidelines for the Metadata JAR File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 4: Pre-requisites to Install Marketo Connector. . . . . . . . . . . . . . . . . . . . . . 11
Chapter 5: Enabling Marketo Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 6: Marketo connection properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 7: Creating a Marketo Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 8: Synchronization Task with Marketo Connector. . . . . . . . . . . . . . . . . . . . 16Marketo Sources in Synchronization Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Marketo Targets in Synchronization Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating a Synchronization Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Enabling the Dedup in Marketo Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 9: Data Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Advanced Data Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Lead Selector Filter – LeadKey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Lead Selector Filter – StaticList. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Lead Selector Filter – LastUpdatedAt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Understanding the Parameter File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table of Contents 3
Chapter 10: Understanding the Property File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Objects and Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Guidelines to Use Data Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 11: Working with Custom Objects and Custom Attributes in Marketo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Understanding Activity Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Handling and Configuring the Activity Attribute File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Adding New Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Adding Custom Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Creating the Schema File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Sample Marketo.tbl file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Sample Schema file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 12: Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Troubleshooting a Synchronization Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Increasing the Secure Agent Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 13: Known SDK Restrictions/Issues in tCurrent Release. . . . . . . . . . . . . 36
Chapter 14: New Stub Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4 Table of Contents
PrefaceThe Data Integration Marketo Connector Guide provides a brief introduction on Data Integration connectors and its features.
The guide provides detailed information on setting up the connector and running synchronization tasks. This guide provides a brief overview of supported features and task operations that you can perform using Marketo Connector.
Informatica Resources
Informatica DocumentationTo get the latest documentation for your product, browse the Informatica Knowledge Base at https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.
If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected].
Informatica Intelligent Cloud Services web siteYou can access the Informatica Intelligent Cloud Services web site at http://www.informatica.com/cloud. This site contains information about Data Integration editions and applications as well as information about other Informatica Cloud integration services.
Informatica Intelligent Cloud Services CommunitiesUse the Informatica Intelligent Cloud Services Community to discuss and resolve technical issues. You can also find technical tips, documentation updates, and answers to frequently asked questions.
Access the Informatica Intelligent Cloud Services Community at:
https://network.informatica.com/community/informatica-network/products/cloud-integration
To find resources on using Application Integration (the Informatica Cloud Real Time service), access the community at:
https://network.informatica.com/community/informatica-network/products/cloud-integration/cloud-application-integration/content
Developers can learn more and share tips at the Cloud Developer community:
5
https://network.informatica.com/community/informatica-network/products/cloud-integration/cloud-developers
Informatica Intelligent Cloud Services MarketplaceVisit the Informatica Marketplace to try and buy Data Integration Connectors, templates, and mapplets:
https://marketplace.informatica.com/community/collections/cloud_integration
Data Integration connector documentationYou can access documentation for Data Integration Connectors at the Informatica Cloud Community: https://network.informatica.com/cloud/index.htm
Informatica Knowledge BaseUse the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs.
To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at [email protected].
Informatica Intelligent Cloud Services trust siteSubscribe to the Informatica trust site for upgrade, maintenance, and incident notifications.
Status.Informatica.com displays the production status of all the Informatica cloud products. All maintenance updates are posted to this status page, and during an outage, it will have the most current information. To ensure you are notified of updates and outages, you can subscribe to a single component, a single incident, or the site as a whole. Subscribing to the site as a whole is the best way to be certain you never miss an update. To subscribe, go to http://status.informatica.com and click SUBSCRIBE TO UPDATES. You can then choose to receive notifications sent as emails, SMS text messages, webhooks, RSS feeds, or any combination of the four.
Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or online.
For online support, click Submit Support Request in Informatica Intelligent Cloud Services. You can also use Online Support to log a case. Online Support requires a login. You can request a login at https://network.informatica.com/welcome.
The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at https://www.informatica.com/services-and-training/support-services/contact-us.html.
6 Preface
C h a p t e r 1
OverviewData Integration connector developed using SDK framework are off-cycle, off release “add-ins” that facilitate data integration to SaaS and on-premise applications, which are not supported natively by Data Integration. The Data Integration connectors are specifically designed to address most common use cases such as moving data into cloud and retrieving data from Data Integration for individual applications.
Once the Marketo Connector is enabled for your Data Integration ORG Id, you need to create a connection in Data Integration to use the connector.
7
C h a p t e r 2
Marketo ConnectorYou can use Marketo Connector to integrate data with Marketo and other SaaS applications or on-premise applications.
Use the connector to perform the following operations:
• Integrate Marketo information such as leads and opportunities.
• Ability to bulk extract or bulk upload data with Marketo.
• Integrate custom objects from Marketo with other applications.
8
C h a p t e r 3
Supported Objects and Task Operations
The following table provides the list of objects and task operations supported by Marketo Connector:
Objects Read Insert Update Upsert Delete look up Data preview
Lead S NA NA S NA S S
MultiLead NA NA NA S NA NA NA
Activity S NA NA NA NA S S
Opportunity S NA NA S S S S
OpportunityPersonRole
S NA NA S S S S
CustomObject S NA NA S S S S
S Supported
NA Not Applicable
Note:
• Both LeadActivity and LeadChanges objects are merged to become the Activity object.
• For the Lead object, assign data filters using filter fields corresponding to SingleLead and MultiLead to perform single lead SOAP fetch and multiple lead SOAP fetch.
• MultipleLead object is only visible as the Target.
• For custom objects, you need to define the schema file. See “Creating the Schema File” on page 32.
• For custom objects, data preview displays zero rows while setting up a synchronization task.
9
Rules and Guidelines for Using the Activity ObjectWhen you use the Activity object in Marketo Connector tasks to retrieve lead activities or lead changes, Marketo returns the marketoGUID field in activities when you use WSDL version 31 or later. The ID element for activityRecord and LeadChangeRecord is replaced by the marketoGUID element as unique identifier.
Consider the following rules when you use the Activity object in existing or new Marketo Connector tasks:
• If you use Marketo WSDL version earlier than 31 and continue to use existing tasks, you do not need to make any changes.
• If you use Marketo WSDL version earlier than 31 and add a new task or edit an existing task, the marketoGUID field appears. However, you cannot populate data for this field.
• If you use Marketo WSDL version 31 and later, the marketoGUID field appears in the task properties and you can populate the data.
• When you run a task, ensure that the WSDL version in the Marketo connection properties complies with the WSDL version of the metadata JAR file that you generated.
For more information about the changes in the record types for the Activity object, see http://developers.marketo.com/blog/important-change-activity-records-marketo-apis/.
Rules and Guidelines for the Metadata JAR FileThe metadata JAR file installed with the latest version of Marketo Connector is of WSDL version 31. You must ensure that the WSDL version in the Marketo connection properties complies with the WSDL version of the metadata JAR file that you generate.
For any custom configurations in the metadata JAR file, perform the following tasks:
• If you want to use WSDL version earlier than 31, back up the metadata JAR file and then replace the current JAR file with the backed-up JAR file.
• If you want to use WSDL version 31, generate a metadata JAR file and replace the current JAR file with the generated JAR file. Update the Marketo connection details accordingly.For more information about generating a metadata jar file, see Chapter 14, “New Stub Generation” on page 37.
10 Chapter 3: Supported Objects and Task Operations
C h a p t e r 4
Pre-requisites to Install Marketo Connector
You need the Marketo sandbox or production account to successfully create a Marketo connection in Data Integration. A user with administrative privileges must fetch the Access and Encryption Key values from the Marketo portal. You require the Access and Encryption key when you create a connection.
Data Integration
Note: Marketo Connector is successfully tested for Marketo WSDL version 31. If you want to use the previous version, you must generate the stub. The connector might work for other similar versions of Marketo WSDL when you change the EndpointURL connection attribute on the Connections page.
11
C h a p t e r 5
Enabling Marketo ConnectorTo enable Marketo Connector, contact Informatica support or Informatica representative. It usually takes 15 minutes for the connector to download to the Secure Agent after it is enabled.
Note: To install the Secure Agent, see Installing Informatica Secure Agent.
12
C h a p t e r 6
Marketo connection propertiesWhen you set up a Marketo connection, you must configure the connection properties.
The following table describes the Marketo connection properties:
Connection property Description
Runtime Environment The name of the runtime environment where you want to run the tasks.
Access Key The access key obtained from Marketo.
Secret Key The encrypted secret key obtained from Marketo.
WSDL URL The Marketo WSDL URL.
Endpoint URL The Marketo endpoint URL.
Schema Path Optional. The schema file path with the file name. Schema file is used to specify custom objects.
UTC Offset The time offset to be appended with the datetime field.
Activity Attributes Config File Name
Optional. The activity attributes configuration file path with the file name.
Batch Size Specify the batch size.
Enable Debugger Enables logs for debugging.Select True to enable logs for debugging, otherwise select False.
13
C h a p t e r 7
Creating a Marketo ConnectionTo use Marketo Connector in a synchronization task, you must create a connection on the Connections page or in a wizard when you configure a task.
1. In Administrator, click Connections.
The Connections page appears.
2. Click New Connection to create a connection.
The New Connection page appears.
14
3. Specify the following details.
Connection Property Description
Access Key Enter the access key obtained from Marketo.
Secret Key Enter the encrypted secret key obtained from Marketo.
WSDL URL Enter the Marketo WSDL URL.
Endpoint URL Enter the Marketo endpoint URL.
Schema Path Optional. Enter the schema file path with the file name. Schema file is used to specify custom objects.
UTC Offset Select the time offset to be appended with the datetime field.
Activity Attributes Config File Name
Optional. Enter the activity attributes configuration file path with the file name. See .
Batch Size Specify the batch size.
Enable Debugger Select True to enable logs for debugging, otherwise select False.
4. Click Save to save the connection.
Note:
• It is recommended to test the connection before saving it. Click Test Connection to evaluate the connection.
• When you want to add custom objects, you must provide the folder path for the schema file that helps you to configure custom objects. See “Adding Custom Objects” on page 31.
• To add attributes to the Activity object, provide the folder path for the Activity Attributes Config File Name. See Chapter 11, “Working with Custom Objects and Custom Attributes in Marketo” on page 29.
15
C h a p t e r 8
Synchronization Task with Marketo Connector
This chapter includes the following topics:
• Marketo Sources in Synchronization Task, 16
• Marketo Targets in Synchronization Task, 17
• Creating a Synchronization Task, 17
Marketo Sources in Synchronization TaskWhen you configure a synchronization task to use a Marketo source, you can configure the source properties.
The following table describes the Marketo source properties:
Source Property Description
Connection Type Name of the source connection.
Source Type Select the source type for the task.
Source Object Select the source object for the task.
Display technical names instead of labels
Displays technical names instead of business names.
Display source fields in alphabetical order
Displays source fields in alphabetical order. By default, fields appear in the order returned by the source system.
16
Marketo Targets in Synchronization TaskWhen you configure a synchronization task to use a Marketo target, you can configure the target properties.
The following table describes the Marketo target properties:
Source Property Description
Connection Name of the target connection.
Target Object Name of the target object.
Display target fields in alphabetical order
Displays target fields in alphabetical order. By default, fields appear in the order returned by the target system.
Creating a Synchronization TaskNote: You need to create a connection before creating a synchronization task.
1. Click New > Tasks, select Synchronization Task, and then click Create.
The New Synchronization task page appears.
2. On the Definition tab, specify the Task Name, provide a Description, and then select the task operation Insert.
3. Click Next.
4. On the Source tab, select the source Connection, Source Type, and Source Object to use for the task.
Marketo Targets in Synchronization Task 17
5. Click Next.
6. On the Target tab, select the target Connection and Target Object required for the task.
7. Click Next.
8. On the Data Filters tab by default, Process all rows is chosen. To assign filters to fetch specific data, see Chapter 9, “Data Filters” on page 20.
9. Click Next.
10. On the Field Mapping tab, map source fields to target fields accordingly.
11. On the Schedule tab, you can schedule the task as per the requirement, and click Save.
12. Click Finish.
13. On the Explore page, select the task, click Actions and select Run.
Enabling the Dedup in Marketo ConnectorYou can use the DedupEnabled field in synchMultipleLeads to configure the Dedupe functionality.
• You can enter either of the two values, True and False, to this field.
• The dedup is enabled when the field is left unmapped or provided with the True value.
• The dedup gets disabled when you mention the False value in the field.
18 Chapter 8: Synchronization Task with Marketo Connector
• The DeDup functions as quoted to the Marketo community.
Note: Enter static value in the DedupEnabled field. It is recommended to not map it with the source field.
The following image shows the DedupeEnabled field:
Consider the following rules when you configure the True/ False value for the dedup functionality:
• When you enter True, it overwrites the previous values.
• When you leave the fields blank, previous values are retained as it is and new values are added to the respective fields.
Creating a Synchronization Task 19
C h a p t e r 9
Data FiltersUse data filters to fetch specific data of a particular object. The synchronization task processes data based on the filter field assigned to the object.
Note: For an Insert (Fetch) operation, it is mandatory to assign data filters. This is required by Marketo endpoint.
Configure the following steps to use data filters:
1. In the synchronization task, select the Data Filters tab.
2. Click New.
The following image shows the data filter:
3. The Data Filter dialog box appears.
4. Specify the following details.
Field Type Description
Object Select Object for which you want to assign filter fields.
Filter By Select the Filter Field.
Operator Select the corresponding operator.
Filter Value Enter the Filter value.
5. Click Ok.
20
Advanced Data FiltersUse the advanced data filter to run search queries that contain complex filter expressions.
The following features are added to the advanced filter in Marketo Connector:
• Lead Selector Filter – LeadKey
• Lead Selector Filter – StaticList
• Lead Selector Filter – LastUpdatedAt FilterThe only logical operator supported in Marketo advanced filter is AND. The only Comparison operator supported in Marketo advanced filter is = (equals).
Note: When you select a filter field that is not filterable, you will know the field is not filterable only after running the synchronization task.
Perform the following steps to access advanced filters:
1. In the Data Filter dialog box, click Advanced.The Advanced Data Filter dialog box appears.
2. Enter the Filter Expression, and click OK.The following image shows the Filter Expression field:
Lead Selector Filter – LeadKeyThe current feature in Marketo Connector supports one attribute for a LeadKey for a given synchronization task.
You can use the following filter fields:
• LeadSelector_LeadKey
Advanced Data Filters 21
• LeadSelector_LeadKey_ValuesSelect the advanced filter option and mention filter condition to make use of LeadSelector LeadKey filter option.
The following image displays an example of LeadSelector LeadKey filter:
Lead Selector Filter – StaticListYou can provide either LeadSelector_StaticListName or LeadSelector_StaticListId or both as input in advanced filter.
You can use the following filter field names:
• LeadSelector_StaticListName
• LeadSelector_StaticListIdSelect the advanced filter option and mention filter condition to make use of LeadSelector StaticList filter option.
The following image displays an example of LeadSelector StaticList filter:
Lead Selector Filter – LastUpdatedAtYou can provide either of the following filter fields:
• LeadSelector_OldestUpdatedAt and LeadSelector_LatestUpdatedAt
22 Chapter 9: Data Filters
• Only LeadSelector_OldestUpdatedAtIn the advanced filter section, for the first selection the connector fetches all lead data between oldest and latest date. If you mention LeadSelector_OldestUpdatedAt, the connector fetches all lead data between oldest and current timestamp of the system.
The following image displays an example of LeadSelector LastUpdatedAt filter:
Understanding the Parameter FileThe parameter file helps you to reuse an existing task. Assume that you have created a task, and now you want to run this task with different filter attributes. You can either edit the existing task or create a new task, but you cannot reuse the existing task.
You can however use the parameter file to reuse an existing task. This parameter file allows you to provide new filter values to the existing task.
1. Click New > Tasks, select Synchronization Tasks and click Create.
2. Specify the Task Name, provide a Description and select the Task Operation Insert.
3. Click Next.
The Source tab appears.
4. Select the source Connection, Source Type, and Source Object to use for the task.
5. Click Next.
The Target tab appears.
6. Select the target Connection and Target Object required for the task.
7. On the Data Filter tab, select the required object and filter field.
In the filter expression, specify the name of the filter field. The syntax is $$Filterfieldname. For example, the filter name is $$OldestUpdatedDate; where oldestupdatedDate is a filter field name.
8. Click OK
9. Open the parameter file present in the Secure Agent.
Understanding the Parameter File 23
The default path is <Secure Agent installation directory>\apps\Data_Integration_Server\data\userparameters
10. In the parameter file, provide the value to the filter fields:
The syntax is $$Fieldname = Filter Value. For example, [email protected]; where Email is the filter field and [email protected] is the filter expression.
11. After adding the values, save the file.
12. In the Synchronization task page, on the Field Mapping tab, map the fields.
13. Click Next.
14. On the Schedule tab, in the Parameter File Name field, provide the name of the parameter file with file extension.
24 Chapter 9: Data Filters
The following image shows the configured parameter file name:
Note: The file name can end with any extension. It is not mandatory that the file name should end with .param. The file name can end with .txt and so on.
15. Click Finish.
Understanding the Parameter File 25
C h a p t e r 1 0
Understanding the Property FileYou need to deploy the jar with a property file in the same path. The property file has few parameters that are used to control the SOAP service configuration and the LeadSelector (for lastestUpdatedAt) delta fetch duration.
You can control the LeadSelector fetch duration interval by changing the QRY_DELTA_DAYS, that is, if QRY_DELTA_DAYS=2.
The LeadSelector_LatestupdatedAt starts creating soap requests for an interval of 2 days and continues doing so until it reaches the LatestupdatedAt date.
You can control the read timeout interval by specifying the TIME_OUT value in milliseconds. The default value is 15 minutes.
The current version of Marketo Connector does not perform NULL field update unless you create a workaround in the expression field on the Field Mapping tab of a synchronizationtask.
By populating the parameter NULL_update= true, you can update the Marketo object fields with NULL for any null value in row-data coming from the source.
The READ_RETRY_COUNT field in the property file helps you rerun the task when Marketo fails to respond to a request within the given time out duration. When it fails, the tasks reruns according to the value assigned to this field.
26
Objects and OperatorsThe following table provides information on the various operators supported by the Lead object:
Filter Fields Data Type Operators Allowed Values
Email String Equals Any String
ForeignSysPersonId String Equals Any String
Id Integer Equals Any Integer
LastUpdatedAt DateTime Equals Any DateTime
The following table provides information on the various operators supported by the Activity object:
Filter Fields Data Type Operators Allowed Values
ActivityType String Equals Any String
Email String Equals
ExcludeActivityType String Equals Any String
ForeignSysPersonId String Equals Any String
Id Integer 1 Equals Any Integer
2
marketoGUID String Equals Any String
OldestCreatedAt DateTime Equals Any DateTime
1. Integer is replaced by Long in WSDL versions 27 and later.2. Any Integer is replaced by Any Long in WSDL versions 27 and later.
The following table provides information on the various operators supported by the Opportunity object:
Filter Fields Data Type Operators Allowed Values
All Supported Fields All Date Types Not Equals,Equals,Greater Than and Equals,Less Than and Equals,Greater ThanLess Than
All Date Types
Note: Boolean is also considered as Integer Data type and hence 0 indicates False and 1-to-Infinity indicates True. The connector supports particular sets of data types for selected operators.
Objects and Operators 27
The following table provides information on the various operators supported by the OpportunityPersonRole object:
Operators Supported Data Types
Not Equals String, Integer, DateTime, Double, Boolean
Equals String, Integer, DateTime, Double, Boolean
Greater Than and Equals Integer, DateTime, Double, Boolean
Less Than and Equals Integer, DateTime, Double, Boolean
Contains String
Greater Than Integer, DateTime, Double, Boolean
Less Than Integer, DateTime, Double, Boolean
Note: When you perform an insert (write) and update task operation, the Null value is not accepted by the Marketo endpoint. Only non-null values are accepted as updatable values. This occurs because of a technical limitation of Marketo Connector, which is xml-based data.
Guidelines to Use Data Filters
Objects Guidelines
LEAD When you perform single lead fetch, use ID/email/cookie filters.For multiple lead fetch, use LastUpdatedAt filter.
Activity For Lead Activity, select (ID or Email or Cookie) and (ActivityType or ExcludeActivityType).For Lead Changes, select OldestCreatedDate and (ActivityType or ExcludeActivityType).
28 Chapter 10: Understanding the Property File
C h a p t e r 1 1
Working with Custom Objects and Custom Attributes in Marketo
This chapter includes the following topics:
• Understanding Activity Attributes, 29
• Handling and Configuring the Activity Attribute File, 29
• Adding New Attributes, 30
• Adding Custom Objects, 31
• Creating the Schema File, 32
• Sample Marketo.tbl file, 33
• Sample Schema file, 33
Understanding Activity AttributesActivity attributes are additional references to existing data. Activity attributes can vary in size and value according to the ActivityType object for a given Marketo user account.
For example, an Activity row (with activitytype: Click Link) can have two activity attributes and on the other hand the next activity row (with activitytype: Visit Webpage) can have seven activity attributes.
Note: When you assign the Activity Attributes file to the connection, the attributes are reflected in the Source object file header name while you perform a synchronization task.
Handling and Configuring the Activity Attribute FileNote: When you assign activity attributes to an Activity object, you must specify the activity attributes file path in the Activity Attributes Config File Name field when you create a Marketo connection. See also: Chapter 7, “Creating a Marketo Connection” on page 14.
After you assign the activityattributes.CSV file while creating a connection, you can view the activity attributes in the Field Mapping tab of a synchronization task.
The Marketo Connector package comes along with an activityattributes.CSV file. You can customise the file according to your requirements.
29
The default activityattributes.CSV file is located in the following directories:
• <Secure Agent installation directory>\downloads\<latest connector zip package>\package\plugins\<Plugin ID>
• <Secure Agent installation directory>\downloads\<latest connector zip package>\package\rdtm\javalib\<Plugin ID>
The following image depicts a sample activityattributes.CSV file:
Adding New AttributesThe activity attribute file consists of two columns. When you want to add a new attribute, you must add a value to both the columns.
For example, add a simple attribute in the .CSV file.
30 Chapter 11: Working with Custom Objects and Custom Attributes in Marketo
The following table shows the attributes for the columns:
DisplayColumnName ActualColumnName
AA_Customer_Contact Customer Contact
AA_Customer_City Customer City
The value added under DisplayColumnName (Business Name) is displayed on the Field Mapping tab when you perform a synchronization task. You need to specify the actual activity attribute in ActualColumnName.
Adding Custom ObjectsTo add custom objects for a source or target in a Marketo synchronization task, perform the following tasks while Chapter 7, “Creating a Marketo Connection” on page 14:
In the Schema Path field, enter Marketo.tbl file. The default .tbl file is located in the following folder path: ..\..\..... \Marketo\Marketo.tbl
For example, C:\a_IOD\Files\Marketo\Marketo.tbl
The following image shows the format of Marketo.tbl file that you must use:
Create the Marketo.tbl file using the following table definitions:
Header Name Allowable Value Remarks
ISCUSTOMOBJ Y Only Y is supported in the current release.
OPR_READ Y, any character If you enter Y, the table is displayed on the Source tab. When you enter any other character, the table is not displayed on the Source tab.
OPR_CREATE N Insert (create) task operation is not supported for custom objects.
OPR_UPDATE N Update task operation is not supported for custom objects.
OPR_DELETE Y, any character Enter Y to support the delete task operation.
OPR_UPSERT Y, any character Enter Y to support the upsert task operation.
TABLE_NAME Any name Object name as shown in the Data Integrationuser interface.
Adding Custom Objects 31
Header Name Allowable Value Remarks
OBJECT_TYPE CUSTOMOBJECT Enter CUSTOMOBJECT as the static value
CUSTOMOBJ_NAME Any name Custom Webservice Object name as used in the RPC Call and as recommended by Marketo.
Y- Yes, N- NO
Creating the Schema FileYou must create the schema file to define each custom object added in the Marketo.tb file. The schema file helps you to configure each of the custom object parameters. The value of the schema file name must be the same as the value you specify in the TABLE_NAME field of the Marketo.tbl file.
For example, the schema file name is Responder.SCH.
The following image shows the format that you must use to create the schema file:
The following table shows the table definitions that you can use to create the schema file:
Header Name Allowable Value Remarks
ISKEY Y, any character If you enter Y, the Key field is active. Define the Key field when you want to configure an Upsert operation for a custom object.
ISNULLABLE Y, any character If you enter Y, the field is defined as mandatory or non-nullable in the synchronization task.
ISFILTERABLE Y, any character If you enter Y, the field is displayed in the Data Filters tab for the selected custom object.
DATATYPE Integer, string, date, boolean, long, float
Any data type specified in the Allowable Value is supported in the schema file. Any other custom data type is considered as String.
PRECISION Valid number Use this field to set the precision.Note: The precision for the String data type is variable, while for other data types it is constant.
SCALE Valid number The scale value must be the same as the precision value.
32 Chapter 11: Working with Custom Objects and Custom Attributes in Marketo
Header Name Allowable Value Remarks
FLD_DISPLAY_NAME Characters A to Z, a to z, and underscore special character
The field name that is visible in the Cloud user interface. You can specify alphabets, both caps and small. You can specify only the underscore ’_’ special character.
FLD_NAME Any MS Latin1 characters
The technical name used for the RPC call to the Web Service endpoint.
FLD_DESCRIPTION - The field description.
Y-Yes, N-No
Sample Marketo.tbl fileYou can create a sample Marketo.tbl file using the following data:
Note: You can copy and paste the sample data in any blank text file and save it as Marketo.tbl to create a file.
"ISCUSTOMOBJ","OPR_READ","OPR_CREATE","OPR_UPDATE","OPR_DELETE","OPR_UPSERT","TABLE_NAME","BUSINESS_TABLE_NAME","CUSTOMOBJ_NAME"
"Y","Y","N","N","Y","Y","Supplemental","CUSTOMOBJECT","Supplemental"
"Y","Y","N","N","Y","Y","Retail_Visit","CUSTOMOBJECT","Retail_Visit"
Sample Schema fileYou can create a sample schema file using the following data:
Note: You can copy and paste the sample data in any blank text file, and save it as .SCH to create a file. "ISKEY","ISNULLABLE","ISFILTERABLE","DATATYPE","PRECISION","SCALE","FLD_DISPLAY_NAME", "FLD_NAME","FLD_DESCRIPTION"
"Y","N","Y","integer",10,10,"IndIdNbr","IndIdNbr","Lead Id"
"N","Y","Y","string",256,256,"LetterType","LetterType","Typoe of Letter"
"Y","Y","Y","date",256,256,"LatestLtrDate","LatestLtrDate","Latest Letter Date"
"N","Y","Y","string",256,256,"ModelMatch","ModelMatch","Model Type"
"N","Y","Y","string",256,256,"CampaignName","CampaignName","Name of the Campaign"
"N","N","Y","date",256,256,"PromoDate","PromoDate","Date of Promotion"
"N","Y","Y","long", 15, 15,"TmOperatorId","TmOperatorId","Operator Id"
Sample Marketo.tbl file 33
C h a p t e r 1 2
TroubleshootingThe log and exception messages generated are captured in the log files. The log files are saved in specific location.
For example, <Secure Agent installation directory>\apps\Data_Integration_Server\<latest version of connector>\ICS\main\tomcat\log.
Troubleshooting a Synchronization TaskWhile creating a synchronization task, the NULL error message appears when the configurations are not valid.
The null error message files are saved in a specific location. For example, <Secure Agent installation directory>\apps\Data_Integration_Server\<latest version of connector>\ICS\main\tomcat\log.
The log and exception details of a failed synchronization task is captured under the Session Log. You require special permission privileges to run the application in debug mode.
Note: You can enable logs to verify request and SOAP response. For higher batch size (Fetch size) such as 5000 or more, the connector might throw a DTM termination error. In such a scenario, it is recommended to set Enable Debugger to False in the connection parameters.
Increasing the Secure Agent MemoryTo increase performance and avoid runtime environment memory issues, perform the following steps:
1. In Administrator, select Runtime Environments.
2. Select the Secure Agent for which you want to increase memory from the list of available Secure Agents.
3. In the upper-right corner, click Edit.
4. In the System Configuration Details section, select the Type as DTM for the Data Integration Service.
5. Edit JVMOption1 as -Xms4056m and JVMOption2 as -Xmx4056m.
34
The following image shows the Details page:
6. In the System Configuration Details section, select the Type as TomCatJRE
7. Edit INFA_memory as -Xms256m -Xmx512m.
The following image shows the Agent Details page:
Note: The minimum and maximum values for the Java heap size are given as an example. Specify the size according to your requirements.
8. Restart the Secure Agent.
Increasing the Secure Agent Memory 35
C h a p t e r 1 3
Known SDK Restrictions/Issues in tCurrent Release
• When you create a synchronization task with custom objects, data preview displays zero rows..
• For an Insert (Fetch) operation, it is mandatory to assign data filters, as it is required by the Marketo endpoint.
36
C h a p t e r 1 4
New Stub GenerationIf you want to use previous versions of Marketo other than version 31, you must generate the stub.
To generate the stub, perform the following tasks:
1. From the command prompt, navigate to C:\Test\metro\Marketo directory.
2. Run the following commands:set JAVA_HOME="C:\Program Files (x86)\Java\jdk1.7.0_25" set classpath=%JAVA_HOME%set PATH=%JAVA_HOME%;%PATH%mkdir C:\Test\metro\Marketo\classes%JAVA_HOME%\bin\wsimport.exe -b "C:\Test\metro\Marketo\marketo.jxb" -XadditionalHeaders -p "com.marketo.mktows18" -verbose -Xdebug -s "C:\Test\metro\Marketo\src" -d "C:\Test\metro\Marketo\classes" http://app.marketo.com/soap/mktows/2_3?WSDLwhere <http://app.marketo.com/soap/mktows/2_3?WSDL> is a sample URL for the WSDL. You must use the customer-specific SOAP endpoint to get the WSDL.
jar -cvf C:\Test\metro\Marketo\Marketo-metadata.jar -C C:\Test\metro\Marketo\classes com3. Enter C:\Test\metro\Marketo
This creates a new Jar file named Marketo-metadata.jar (new stub) for the required WSDL version.
37
I n d e x
CCloud Application Integration community
URL 5Cloud Developer community
URL 5connections
Marketo 13
DData Integration community
URL 5
IInformatica Global Customer Support
contact information 6Informatica Intelligent Cloud Services
web site 5
Mmaintenance outages 6
Marketo connection properties 13
SSecure Agent
increasing memory 34status
Informatica cloud services 6system status 6
Ttrust site
description 6
Uupgrade notifications 6
Wweb site 5
38
