Configure Endeca in Linux with Multiple Instances

-
While integrating ATG and Endeca in Linux with Multiple Instances ,we need to be really careful of the ports ATG, weblogic server and Endeca Services use.

Here are few tips on the how can we configure ATG,Weblogic and Endeca Application without conflicting ports.

First of all lets start with the Compatibility Matrix for ATG10.2.

ATG Compatibility
CRS10.2
CRS10.2 Mobile Web Application

Endeca Compatibility
Oracle Endeca Commerce 3.1.2
Oracle Endeca MDEX Engine 6.4.1
Oracle Endeca Platform Services 6.1.3
Oracle Endeca Tools and Frameworks with Experience Manager 3.1.2
Oracle Endeca Content Acquisition System 3.1.2

Application Server Compatibility
Weblogic 10.3.5 or Weblogic Server 10.3.6 or JBoss 5.1.2 EAP
Weblogic Server ports

ATG Configuring Admin Server, select 7003 as Admin port
In the WEBLOGIC ONLINE PORT BINDING menu, select [C] Choose Custom Port Binding.

In the CHOOSE CUSTOM WEBLOGIC ONLINE PORT BINDING menu, select [3] ports-02: http port is 7203 for Production and select [4] ports-03:http port is 7303 for Publishing.

Endeca Ports
MDEX Port: 15001
DGRAPH Port:15001, AGRAPH Port: 15003
WORKBENCH Port:8282
EAC Port: 8889
JCD Port:: 8098
CAS server Port: 8501

Comments

Post a Comment

Popular posts from this blog

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

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

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