Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Integration 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Back Next

Deployment to an Archive File

Deployment to an Archive File

An archive file stores application objects and metadata in an XML format.
You can create the following types of archive files:
Application archive file
An application archive file is an XML file that stores all of the information about application objects and metadata for an application. The file has an .iar extension.
Application patch archive file
An application patch archive file is an XML file that stores information about an application patch. The file stores information about the application objects in the patch, the patch description, the name of the corresponding incremental application, and whether the patch retains or discards state information. The file has a .piar extension.
You might want to create an archive file for any of the following reasons:
  • Deploy the application or application patch. If your organization restricts the ability to deploy applications or application patches to a Data Integration Service to administrators, an administrator can deploy an archive file to the Data Integration Service.
    To deploy an application, the administrator can use the Administrator tool, or infacmd dis deployApplication. To deploy an application patch, the administrator can use infacmd tools patchApplication.
  • Import the application or application patch to a Model repository. An administrator can import an archive file to a Model repository using infacmd tools importObjects.
    If you import an archive file that contains objects that are already in the Model repository, the Developer tool creates a new project folder.
    The release version of the Model repository where you import the application must be compatible with the version from which you exported the application to an archive file.
  • Archive the file in another system. For example, if the Model repository is not integrated with a version control system, an administrator can check the archive file into a version control system for project auditing or object recovery.
0 COMMENTS
We’d like to hear from you!