[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"howto:ear:linux:en":3},{"resolvedFromAlias":4,"canonicalExt":5,"ext":5,"name":6,"category":7,"categoryName":8,"updatedAt":9,"os":10,"osLabel":11,"quickSolution":12,"stepByStep":13,"recommendedSoftware":16,"alternativeMethods":17,"commonIssues":18,"securityNote":37,"extensionPath":38,"extensionLabel":39,"breadcrumbs":40,"metaDescription":50},false,"ear","Jakarta EE Enterprise Archive (EAR)","archives","Archives","2026-06-12T09:14:21.028Z","linux","Linux","To open .EAR files on Linux, to inspect contents: use an archive tool that can open ZIP/JAR (for example, open it in your desktop archive manager or extract it with a JAR/ZIP-capable utility; EAR is a standard JAR/ZIP-based archive).",[14,15],"To inspect contents: use an archive tool that can open ZIP/JAR (for example, open it in your desktop archive manager or extract it with a JAR/ZIP-capable utility; EAR is a standard JAR/ZIP-based archive).","To run it: deploy the .ear to a Jakarta EE application server environment.",[],[],[19,25,31],{"title":20,"description":21,"steps":22},"It won’t open in my archive tool","Although an EAR is a JAR/ZIP-based archive, some tools rely on file associations or don’t recognize .ear by default.",[23,24],"Use “Open with…” and explicitly choose an archive program that supports ZIP/JAR archives.","If your tool supports it, try opening it as a JAR/ZIP archive (EAR is a standard JAR file with a different extension).",{"title":26,"description":27,"steps":28},"The server rejects the EAR or deployment fails","EARs are meant for Jakarta EE application servers; deployment can fail if the archive structure/descriptors are not what the target server expects (for example, missing or incorrect META-INF descriptors or incompatible packaging).",[29,30],"Inspect the EAR contents after extracting it and verify it includes expected modules and META-INF deployment descriptors.","Rebuild the EAR using your project’s build tooling (commonly via Maven’s EAR packaging support) and redeploy according to your application server’s guidance.",{"title":32,"description":33,"steps":34},"I extracted it but don’t know what to edit","EARs often contain multiple modules (like .war and .jar). Configuration and deployment metadata is commonly under META-INF, while application code/resources are inside embedded modules.",[35,36],"Look for META-INF in the EAR for deployment descriptors (and for embedded .war/.jar files).","If you need to change the application, update the source project and rebuild the EAR rather than manually editing extracted files.","An EAR is an archive container and can bundle executable server-side components (for example, Java classes and libraries). Treat EARs from untrusted sources as potentially harmful when deployed to an application server.","/file-extension/ear",".EAR",[41,44,47],{"label":42,"to":43},"Home","/",{"label":45,"to":46},"How To","/file-extension",{"label":48,"to":49},"Open .EAR on Linux","/how-to/open-ear-on-linux","Learn how to open .EAR files on Linux with step-by-step instructions, recommended software, and troubleshooting tips."]