no installed platform or application package containing an AppModule which matches your Module

-
The one common cause for this exception is generally beginners in ATG will start creating a Java project in Eclipse workspace(workspace location is not same as ATG installation directory) and try to deploy that project in some Application Server and end up in getting this Exception.The solution is to create the Module/Project inside the ATG installation directory for eg:Eclipse-New Java Project, you need to choose the path of the New Module/Project to C:\ATG\ATG10.2\,so that the new Module comes under the installation directory, or if its an existing ATG Module/Project,copy that Module/Project to ATG installation directory and import the project into Eclipse workspace.

Error #1

I got this error, when i moved my application EAR which was working perfectly in windows to Unix environment.In our Unix box we are using exactly the same software/versions which we used for local windows machine,but still getting the error.

I verified the ATG Root directory to check the module
DafEar.base is present,i am able to find the module since this is defaultly shipped as part of ATG Installation.But the root cause was i need to modify the ATG Server,Dynamo Home and Dynamo Root Path in dynamo.env file with respect to Unix environment

FIX

Modify the dynamo.env file(path->xxx.EAR-atg_bootstrap.war-WEB-INF-dynamo.env)to correct the environment properties specific for unix environment.This solved the issue !!!!,For your reference see the  dynamo.env file for unix env below.



Unix

#Dynamo environment properties

atg.dynamo.modules=DSS,DafEar
atg.dynamo.server.home=/app/atguser/product/ATG/home/servers
atg.dynamo.use-install=true
atg.dynamo.platformversion=10.0.3
atg.dynamo.home=/app/atguser/product/ATG/home
atg.dynamo.versioninfo=ATGPlatform/10.0.3
atg.dynamo.display=\:0.0
atg.dynamo.root=/app/atguser/product/ATG

Error #2

The other time got this error while creating ATG application Module without ATG Plugin,the MANIFEST.MF file will not get created in this case.Your module need to have this file,otherwise you will get this exception while invoking runAssembler.You will not able to pack your module into an EAR and run the Application.

FIX

You need to create a folder META-INF,inside that create the MANIFEST.MF file,Add the required entries,Manifest-Version,ATG-Config-Path,ATG-Required,ATG-J2EE,ATG-EAR-Module,ATG-Class-Path.Here ATG-J2EE and ATG-EAR-Module are optional,we can add this if you have a front end GUI running in ATG application

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more