Client Application
Processor	Single Core	3.0 GHz or greater
	Multi Core	2.0 GHz or greater
Operating System	Microsoft Windows 2000/XP/2003 Platforms
Memory	2 GB or greater
Hard Disk Space	100 MB – if .NET Framework is already installed
	250 MB – if .NET Framework is not yet installed
Other	Requires Microsoft .NET Framework 2.0
Server Application
Processor	Dual Core Processor rated at 2.0 GHz or higher
	Quad Core Processor highly recommended
Operating System	Microsoft Windows 2000/XP/2003 Platforms
Memory	2 GB or greater
Hard Disk Space	100 MB – if .NET Framework is already installed
	250 MB – if .NET Framework is not yet installed
Other	Requires Microsoft .NET Framework 2.0
SQL Server 2000 (Database)
Processor	Intel or AMD Processor rated at 1.8 GHz or greater
Memory	Varies based on database performance
Hard Disk Space	95 – 270 MB for Server
	100 – 200 MB additional for application databases
Other	Service Pack 4 for SQL Server 2000
SQL Server 2005 (Database)
Processor	Intel or AMD Processor rated at 1.8 GHz or greater
Memory	Varies based on database performance
Hard Disk Space	95 – 270 MB for Server
	100 – 200 MB additional for application databases
Other	Service Pack 1 for SQL Server 2005

Centerprise Integration Studio is a multithreaded data integration tool that enables you to runs transfer jobs on your individual desktop or client. With Centerprise Integration Server, you can run the same data integration tasks on a registered server, which significantly boosts the performance of the transfer job. Because Centerprise Integration Server provides a multithreaded hyper-parallel data transformation and integration server, it takes advantage of multi-core and multiprocessor hardware to deliver exceptional performance and scalability. Centerprise Integration Server can only be used alongside an installed version of Centerprise Integration Studio. In addition, data integration tasks can only be scheduled with the Server edition of the application.

Yes, trial versions are free of charge and are available for all the products in the Centerprise Data Integrator, including Centerprise Integration Studio, Centerprise Integration Server and Centerprise DataMover. These trial versions are fully functional, so every feature and aspect of the product is available for you to try and evaluate. The trial period begins on the first day that you launch the software and continues for 15 days (a counter displaying the elapsed time appears anytime you launch the product). When the trial expires, you must purchase the software to continue using it.

You can download a free trial version of any of the Centerprise Data Integrator products directly from our website (link).

The trial period for the product is 15 days. It begins on the first day that you launch the software and continues for 15 days (a counter displaying the elapsed time appears anytime you launch the product). When the trial expires, you must purchase the software to continue using it.

To purchase a licensed version of the Centerprise Integration Studio edition, follow these steps: 1. Launch Centerprise Integration Studio from the start menu. 2. From the registration screen, click on the Buy button. This will take you to the website where you will be able to purchase the application. Follow the steps to buy the product. You will need to complete a form with some information?.more info 3. You will receive an email containing license keys/a serial number. Include these keys in?.

Centerprise Integration Studio currently supports five database types, namely: Microsoft SQL Server 2000 and 2005, Oracle, DB2, Sybase and Microsoft Access. Details on the different databases supported are below:

 

Databases Supported by Centerprise Integration Studio 2.0 The machine must have .NET Framework 2.0 or higher installed.*
Data Provider	Database
DB2	DB2 V9.1 for Linux, UNIX, and Windows
	DB2 UDB v7.1, v7.2, v8.1, v8.2 for Linux, UNIX, and Windows
	DB2 UDB v7.x, DB2 UDB v8.1 for z/OS via DRDA
	DB2 UDB V5R4 for iSeries
	DB2 UDB V5R1, V5R2, V5R3, V5R4 for iSeries
Oracle	Oracle 10g R1, R2 (10.1, 10.2)
	Oracle 9i R1, R2 (9.0.1, 9.2)
	Oracle 8i R2, R3 (8.1.6, 8.1.7)
SQL Server	MS SQL Server 2005
	MS SQL Server 2000 Enterprise Edition (64-bit)
	MS SQL Server 2000 Desktop Engine (MSDE 2000)
	MS SQL Server 2000
Sybase	Sybase Adaptive Server Enterprise 12.0, 12.5, 12.5.1, 12.5.2, 12.5.3, 12.5.4, 15.0
	Sybase Adaptive Server 11.5 and 11.9
MS Access	MS Access 97 and beyond

 

Centerprise Integration Studio currently supports three file types, namely: Fixed-length or Fixed-width, Delimited (comma-separated, semi-colon delimited, tab-delimited, or any other delimiter), and Microsoft Excel spreadsheets.

Once you install Centerprise Integration Studio, you need to create a repository in order to use the application. The repository will store all user-defined settings, definitions and metadata. This repository can be an SQL server or a Microsoft Access database. You can create multiple repositories, and select any one as the current database during the login process. The repository consists of the following user-defined data:

• Transfer settings including layouts, validation rules, and mapping options
• Metadata, such as data models, data formats and filters
• Personalized information such as Settings

The first time you log into Centerprise Integration Studio, you should use the following credentials to access the application: User ID: admin Password: admin Once you log in, you can create a new user and password from?.

No, Centerprise Integration Studio does not support spaces in the field names. However, field headers can contain spaces, and can be modified to suit your business naming conventions.

A filter, typically applied to the source file or database, is created to filter out data meeting specified criteria. You would use filters to rule out any data you are not interested in transferring to the destination. For example, if you are transferring customer orders to a database, and are not interested in transferring orders from Texas, you could create a source filter stating OrderState <> ?TX?. All orders coming from Texas will be filtered out during the reading process itself, meaning they will not go through the remaining stages of the transfer process. Unlike filters, validation rules can be applied to both, your source and destination file or database. These rules are written to validate that your data is in an expected format, and free from errors, either while being imported from the source, or while being written to the destination. For example, you may want to write a simple rule ensuring that order quantities being imported are greater than zero. You would apply a validation rule to your source, stating OrderQuantity >= 0. You can also decide whether to raise an error or a warning for the data that does not meet those criteria. The error or warning will show up in the log file once the transfer is complete. Validation rules therefore allow you to gain a better understanding of and gage the quality of your source and/or destination data.

To use filters or validations rules for more than one transfer setting, you can do one of the following: i. If the new setting has a source and destination layout similar to the old setting, create the new transfer setting by using ?New from Template.? Select the setting that contains the filters or validation rules you want to apply, and click OK. The setting will be loaded as a copy of the old setting. Type in a new unique name for your setting and save it. Then, change the source and destination file paths as needed and map the source and destination fields accordingly. The filters and validation rules specified in the old setting will apply to the new one as long as the source and destination layouts have not changed. ii. If the new setting has a source or destination layout different from the old setting containing the filters and validation rules, you can use the Shared Record Layout. This is especially helpful if you have a source or destination layout, along with filter or validation rules, that you use frequently. Access Shared Record Layouts from the Metadata menu option, and select New to create a new Shared Layout setting. Specify a layout, either source or destination, using the Build Layout option. Or, you can create the layout manually. If you plan to use this layout as a source, you can create filters from the Reader Options tab. If you plan to use this layout as a source OR destination, you can create validation rules in the Validations tab. You can then use this layout to create another transfer setting (Data>Transfer) and use the Build Layout>Use Shared Layout to apply the filters and validation rules you saved in that particular shared layout.

In Source or Destination Validations, the Active checkbox can be used to activate or deactivate the rule as and when it applies to the setting. This avoids having to delete the rule when it no longer applies, only to have to activate it a month later. When a rule is Active, you can specify whether or not to transfer a record that fails that rule. If you leave the Warning checkbox unchecked, the record will not be transferred, and the record log will display an error for that record. However, if you select the Warning checkbox, the record will be transferred, and the record log will display a warning for that record. If you choose a field name to associate with the error or warning message, the record log will also display that field name.

The ?Field? drop-down in the Validations tab allows you to select a field name to link with the validation rule you create. If there is an error or warning associated with that validation rule, it will appear in the log file as linked to the field name you select. This is especially helpful during reporting, to gain a better understanding of which fields contain erroneous data.

Yes, you can create multiple filters and validation rules for one setting by simply clicking on Add in the expression builder dialog.

?Enforce strict compliance? refers to a command in File Reader Options that can be used to ensure that the transfer only occurs if the source file?s layout exactly matches the source layout defined in the setting. This includes checking for the same number and order of fields and field names.

A shared record layout is a layout that can be used for your source or destination in different transfer settings. Here, you define a layout that you can use for a source or destination. You can even define Reader and Writer options, as well as Validation Rules. You can then load this layout by using the Build Layout > Use Shared Layout option. If you use the layout for your source, the Reader options and validation rules defined in the shared layout will be applied to the source layout. If you use the layout for your destination, the writer options and validation rules defined will be applied to the destination layout. This allows you to use existing layouts in a new setting without having to create layouts from scratch.

No. Currently, Centerprise Integration Studio is not designed to extract data from multiple databases, or merge data. You can only extract data from multiple tables within a database. To extract data from multiple databases, you can use Centerprise DataMover to merge multiple tables from multiple databases into one database, and then use Centerprise Integration Studio to create a data model by reverse engineering the tables from that database. You can then use that data model to create a Query Layout.

You cannot directly export the log file to an Excel spreadsheet. Exporting to Excel has its limitations because each record in a log consists of 7rows, and an Excel spreadsheet will only accept 65,536 rows. A transfer for a table containing 10,000 records would generate 70,000 rows in the log file, which cannot be transferred to Excel.  

 

A possible workaround is as follows. The log is generated as an XML file, which contains all the details seen in the Transfer Log Viewer UI. A program can be written to parse the information present in the XML file to an Excel spreadsheet or any other file or database format.