ATG Search Configurations for Commerce and BCC Module

-
Module to include in build & manifest files

Commerce Module

META-INF 
  
Manifest-Version: 1.0
ATG-Config-Path: config/
ATG-Required: DAF.Search.Query DafEar.Admin DCS.Search DCS.Search.CustomCatalogs.common DAF.Search.Query.Search DAF.Search.Routing DAF.Search.Base DAF.Search.common DAF.Search.Index DAF.Search.Topics PublishingAgent 

BCC_Module

Buld.xml    
      
<target name="create-search-ear">
 <delete dir="BCC_Module"/>
 <assemble-ear dynamoRoot="C:\ATG
 \ATGXXX "dynamoModules="DAS,DPS,DCS,DSS,DafEar.Admin,
 DCS-UI.management,DCSUI.Search,B2CCommerce.Versioned,PubPortlet,
 DCS.Search.Versioned,DAF.Search.Routing,SearchAdmin.AdminUI,
 DCS.Search.CustomCatalogs.Versioned,DAF.Search.Base,
 DAF.Search.Query,DAF.Search.common,DAF.Search.Index,
 DAF.Search.Topics,DAF.Search.Versioned,DataLoader,RL"
 overwrite="true" destinationFile="C:\jboss-X.X.X.GA\server
 \server_instance_folder\deploy\BCC_Module.ear" />
</target>

META-INF
    
Manifest-Version: 1.0
ATG-Config-Path: config/
ATG-Required: B2CCommerce.Versioned DCS.CustomCatalogs
ATG-J2EE: j2ee-apps/BCC_Module
ATG-EAR-Module: j2ee-apps/BCC_Module

See the Search Module Configurations also

Commerce Module
BCC Module

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>  ...
Read more

remote debug in eclipse with both Admin and Managed Servers running

-
For configuring Remote Debug in Managed Weblogic Server,the very first golden rule is,you should not specify any port number of  weblogic admin or  managed server which is running ,it has to be a free port(use this link to find the appropriate ports List of Ports ). How to create managed weblogic server and run multiple EAR's can be found in this link -> Run Multiple Ear in Managed Server Mode How to run remote debug in Admin server can be found in the link -> Remote Debugging Weblogic Admin Server The configuration  for remote debug is specified in the startup script 'setDomainEnv.cmd'. First Approach Here we need to  create three scripts corresponding to the orignial scritps,'startManagedWeblogic.cmd', 'startWeblogic.cmd' and 'setDomainEnv.cmd. For Eg: Create the scripts  startManagedATGProductionWeblogic.cmd, startWeblogicATGProduction.cmd, setDomainEnvATGProduction.cmd by copying fr...
Read more

Oracle Recommended Approach for ATG10.1.2 Siebel 8.1.1.10 Integration

-
Oracle has provided the code base for atg siebel integration, this code base is an enhanced version of the current CRS implementation we have for user registration,order capture and product configurator. Configuration Steps Extract the given integration code to your atg folder (eg:C:\ATG\ATG10.1.2) Set up the project in your eclipse,you can setup this as  an existing ATG Project Once you Run the siebelBuild.xml with the ant task "all-with-ws" a new Folder Siebel will be created in your atg root path (eg:C:\ATG\ATG10.1.2) There will also a SiebelWS folder created with a SiebelWS.ear file inside your newly created Siebel folder. Create an ear using runAssembler for the Siebel web application by specifying either the module -m Siebel.PublishingAgent or Siebel.Versioned based on whether running application in Production or Publishing Run the necessary scripts in production publishing and switching schemas. Define the Webservice endpoints. Run the Application !! See h...
Read more