Following Best Practices
Overview
Architect the Solution
Business Requirements
Technical Requirements
Design for Reuse
Set Up Collaborative Workspaces
Use DataConnect Templates
Use Orchestration
Use Naming Conventions
Translate Business Processes to DataConnect
Data Governance
Processes
Transformation Maps
Schema
Determine Infrastructure Requirements
Identify Connectivity Requirements
Message Component Framework SDK
Saving and Reusing a Connection
Develop Your Templates
Leverage In-line Documentation
Process Designs
Artifact Properties
Script Comments
Search and Replace
Secure Your Integrations
Common Integration Techniques
Macros
Reusable Scripts
Constants
djMessage Objects
Parallelism and Concurrency
Data Validation
Event Condition Action rules
Data Enrichment
Temporary Targets
Lookups
Aggregating Data
Transformation and Process Objects
Web Service APIs
Custom Java objects
Time Zone Considerations
Important Date Functions
Localization Issues
Scripting Tips, Tricks, and Techniques
Performance
Accuracy
ECA Loops
Complex Text Parsing
Plan for Customization
Bulk or Batch Pattern Integrations
Files vs. Message Objects
Large File Splitting
Wide Files
Concurrency
RDBMS Transformation Maps
Source Data
Target Data
RDBMS Process Designs
SQL step
Application Step
Sessions
Message Pattern Integrations
Actian DataConnect Studio API Invoker
Payload Size
Compressing Files
Orchestration
RDBMS Considerations
API Limitations
Batch Size
Call Allocation
Concurrency
Optimize and Harden the Solution
Optimize
Use Sample Data
Manage Log Files
Analyze with Engine Execution Profiler
Test
Package and Deploy
Execute
Debug
Iterate
Customize DataConnect
Limiting Workspace Refresh
Using Actian Warehouse as an Integration Source and Target
Connecting and Deploying to Actian Warehouse
SQL Sessions
EZScript
Troubleshooting
DriverOpJons
Macros
DJImport and DJExport Connection Wizard
Deploy Map source files to Actian Warehouse
Following Best Practices
Deploy Map source files to Actian Warehouse