In the case you want to integrate Endeca with ATG. You must have Endeca application which can be integrate with ATG. Here I am going to explain how to create Endeca application which can be integrated with product catalog systems like ATG.
For product catalog applications Endeca utilizes the Product Catalog Deployment Template from Discover reference application. This is available after installing ToolsAndFramwork.
This is located at : \ToolsAndFrameworks\<version>\reference\discover-data-catalog-integration
There are two ways to deploy Product Catalog application.
- Interactive Deployment : Here you need to respond command prompt during deployment process.
- Automated Deployment : Here you can specify command prompt values in file. Then no need to interact with command prompt.
Here I am going to use interactive mode.
- Navigate to C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin.
- Invoke deploy script as follows.
Accept most defaults. Choose “Y” to install a base deployment. Specify Store (You can choose name)as the application name. Specify the path to CAS path using forward slashes (UNIX style). Specify the appropriate ISO language code, for example, en for English. Here is command line out put for this script.
=============================================================================
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin>deploy.bat --app C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml
------------------------------------------------------------------------------
Found version 6.1 of the Endeca IAP installed in directory
C:\Endeca\PlatformServices\6.1.3. If either the version or location are
incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.
Press enter to continue with these settings.
Continue?
------------------------------------------------------------------------------
Deployment Template installation script.
This script creates the directory structure for your
deployment and installs configuration files and scripts
into the directory structure.
05/24/2015 13:36:18 [deploy.pl] INFO: Starting deployment template
installation.
------------------------------------------------------------------------------
The following app modules were specified on the command line argument:
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml
Modules may be deployed standalone or on top of a base deployment type. Do
you want to install a base deployment with the specified module(s)?
Install base deployment? [Y/N]:
Y
05/24/2015 13:36:22 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml.
05/24/2015 13:36:22 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml.
------------------------------------------------------------------------------
Enter a short name for your application.
Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$
[default: Discover]
Choosing a different application name may require additional configuration on
your web application.
Application name:
Store
------------------------------------------------------------------------------
Specify the path into which the application will be deployed. The specified
directory must exist and cannot contain spaces.
For example, to deploy into c:\apps\Store, specify the path as c:\apps.
Deployment directory:
C:\Endeca\apps
------------------------------------------------------------------------------
Specify the port on which the Endeca Application Controller is running. This
is configured in the server.xml file in the workspace of the Endeca software
install and should be the same for all applications deployed in this
environment. Ports must be in the range 1024-65535 [default: 8888].
EAC port:
8888
05/24/2015 13:36:55 [deploy.pl] INFO: Deploying application into
C:\Endeca\apps\Store
------------------------------------------------------------------------------
Please enter the CAS install directory using Unix-style forward slashes,
including the version number (e.g. C:/Endeca/CAS/3.1.1).
C:/Endeca/CAS/3.1.2
------------------------------------------------------------------------------
Please enter the version for CAS jar files (or hit 'enter' to use the
default). [Default: 3.1.1]
------------------------------------------------------------------------------
Please enter the hostname where CAS is running (or hit 'enter' to use the
default). [Default: localhost]
------------------------------------------------------------------------------
Please enter the port where CAS is running (or hit 'enter' to use the
default). [Default: 8500]
------------------------------------------------------------------------------
Please enter the language code to use (or hit 'enter' to use the default).
[Default: en]
------------------------------------------------------------------------------
What port is the Workbench running? [Default: 8006]
------------------------------------------------------------------------------
What port should be used for the Live Dgraph? [Default: 15000]
------------------------------------------------------------------------------
What port should be used for the Authoring Dgraph? [Default: 15002]
------------------------------------------------------------------------------
What port should be used for LogServer? [Default: 15010]
05/24/2015 13:37:33 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml.
05/24/2015 13:37:33 [deploy.pl] INFO: Processing install with id 'Dgraph'
05/24/2015 13:37:34 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml.
05/24/2015 13:37:34 [deploy.pl] INFO: Processing install with id
'DefaultTemplateManagerApp'
05/24/2015 13:37:35 [deploy.pl] INFO: Application successfully deployed.
------------------------------------------------------------------------------
Found version 6.1 of the Endeca IAP installed in directory
C:\Endeca\PlatformServices\6.1.3. If either the version or location are
incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.
Press enter to continue with these settings.
Continue?
------------------------------------------------------------------------------
Deployment Template installation script.
This script creates the directory structure for your
deployment and installs configuration files and scripts
into the directory structure.
05/24/2015 13:36:18 [deploy.pl] INFO: Starting deployment template
installation.
------------------------------------------------------------------------------
The following app modules were specified on the command line argument:
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml
Modules may be deployed standalone or on top of a base deployment type. Do
you want to install a base deployment with the specified module(s)?
Install base deployment? [Y/N]:
Y
05/24/2015 13:36:22 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml.
05/24/2015 13:36:22 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml.
------------------------------------------------------------------------------
Enter a short name for your application.
Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$
[default: Discover]
Choosing a different application name may require additional configuration on
your web application.
Application name:
Store
------------------------------------------------------------------------------
Specify the path into which the application will be deployed. The specified
directory must exist and cannot contain spaces.
For example, to deploy into c:\apps\Store, specify the path as c:\apps.
Deployment directory:
C:\Endeca\apps
------------------------------------------------------------------------------
Specify the port on which the Endeca Application Controller is running. This
is configured in the server.xml file in the workspace of the Endeca software
install and should be the same for all applications deployed in this
environment. Ports must be in the range 1024-65535 [default: 8888].
EAC port:
8888
05/24/2015 13:36:55 [deploy.pl] INFO: Deploying application into
C:\Endeca\apps\Store
------------------------------------------------------------------------------
Please enter the CAS install directory using Unix-style forward slashes,
including the version number (e.g. C:/Endeca/CAS/3.1.1).
C:/Endeca/CAS/3.1.2
------------------------------------------------------------------------------
Please enter the version for CAS jar files (or hit 'enter' to use the
default). [Default: 3.1.1]
------------------------------------------------------------------------------
Please enter the hostname where CAS is running (or hit 'enter' to use the
default). [Default: localhost]
------------------------------------------------------------------------------
Please enter the port where CAS is running (or hit 'enter' to use the
default). [Default: 8500]
------------------------------------------------------------------------------
Please enter the language code to use (or hit 'enter' to use the default).
[Default: en]
------------------------------------------------------------------------------
What port is the Workbench running? [Default: 8006]
------------------------------------------------------------------------------
What port should be used for the Live Dgraph? [Default: 15000]
------------------------------------------------------------------------------
What port should be used for the Authoring Dgraph? [Default: 15002]
------------------------------------------------------------------------------
What port should be used for LogServer? [Default: 15010]
05/24/2015 13:37:33 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml.
05/24/2015 13:37:33 [deploy.pl] INFO: Processing install with id 'Dgraph'
05/24/2015 13:37:34 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data-catalog-integration\deploy.xml.
05/24/2015 13:37:34 [deploy.pl] INFO: Processing install with id
'DefaultTemplateManagerApp'
05/24/2015 13:37:35 [deploy.pl] INFO: Application successfully deployed.
=============================================================================
3. Navigate to control directory of the newly created application.Then run initialize_services script.
This will create required record stores and provision this application. Below is the command line output of this script.
=============================================================================
C:\Endeca\apps\Store\control>initialize_services.bat
Setting EAC provisioning and performing initial setup...
[05.24.15 13:47:12] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:47:12] INFO: Setting definition for application 'Store'.
[05.24.15 13:47:13] INFO: Setting definition for host 'AuthoringMDEXHost'.
[05.24.15 13:47:13] INFO: Setting definition for host 'LiveMDEXHostA'.
[05.24.15 13:47:13] INFO: Setting definition for host 'ReportGenerationHost'.
[05.24.15 13:47:13] INFO: Setting definition for host 'WorkbenchHost'.
[05.24.15 13:47:13] INFO: Setting definition for host 'ITLHost'.
[05.24.15 13:47:13] INFO: Setting definition for component 'AuthoringDgraph'.
[05.24.15 13:47:13] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgidx-output'.
[05.24.15 13:47:14] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-forge-output'.
[05.24.15 13:47:16] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-cumulative-partials'.
[05.24.15 13:47:17] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-workbench-dgraph-config'.
[05.24.15 13:47:18] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-input'.
[05.24.15 13:47:19] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-cumulative-partials'.
[05.24.15 13:47:20] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-config'.
[05.24.15 13:47:22] INFO: Setting definition for component 'DgraphA1'.
[05.24.15 13:47:22] INFO: Setting definition for script 'PromoteAuthoringToLive'.
[05.24.15 13:47:22] INFO: Setting definition for custom component 'WorkbenchManager'.
[05.24.15 13:47:22] INFO: Updating provisioning for host 'ITLHost'.
[05.24.15 13:47:22] INFO: Updating definition for host 'ITLHost'.
[05.24.15 13:47:22] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.24.15 13:47:23] INFO: [ITLHost] Starting shell utility 'mkpath_-data-workbench-temp'.
[05.24.15 13:47:24] INFO: [ITLHost] Starting shell utility 'mkpath_-data-processing'.
[05.24.15 13:47:26] INFO: Setting definition for custom component 'IFCR'.
[05.24.15 13:47:26] INFO: Updating provisioning for host 'ITLHost'.
[05.24.15 13:47:26] INFO: Updating definition for host 'ITLHost'.
[05.24.15 13:47:26] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.24.15 13:47:27] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.24.15 13:47:28] INFO: Setting definition for component 'LogServer'.
[05.24.15 13:47:28] INFO: [ReportGenerationHost] Starting shell utility 'mkpath_-reports-input'.
[05.24.15 13:47:30] INFO: Setting definition for script 'DaySoFarReports'.
[05.24.15 13:47:30] INFO: Setting definition for script 'DailyReports'.
[05.24.15 13:47:30] INFO: Setting definition for script 'WeeklyReports'.
[05.24.15 13:47:30] INFO: Setting definition for script 'DaySoFarHtmlReports'.
[05.24.15 13:47:30] INFO: Setting definition for script 'DailyHtmlReports'.
[05.24.15 13:47:30] INFO: Setting definition for script 'WeeklyHtmlReports'.
[05.24.15 13:47:31] INFO: Setting definition for component 'WeeklyReportGenerator'.
[05.24.15 13:47:31] INFO: Setting definition for component 'DailyReportGenerator'.
[05.24.15 13:47:31] INFO: Setting definition for component 'DaySoFarReportGenerator'.
[05.24.15 13:47:31] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.
[05.24.15 13:47:31] INFO: Setting definition for component 'DailyHtmlReportGenerator'.
[05.24.15 13:47:32] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'.
[05.24.15 13:47:32] INFO: Setting definition for script 'BaselineUpdate'.
[05.24.15 13:47:32] INFO: Setting definition for script 'PartialUpdate'.
[05.24.15 13:47:32] INFO: Setting definition for component 'ConfigurationGeneratorForge'.
[05.24.15 13:47:32] INFO: Setting definition for component 'Forge'.
[05.24.15 13:47:33] INFO: [ITLHost] Starting shell utility 'mkpath_-data-incoming'.
[05.24.15 13:47:34] INFO: Setting definition for component 'PartialForge'.
[05.24.15 13:47:34] INFO: [ITLHost] Starting shell utility 'mkpath_-data-partials-incoming'.
[05.24.15 13:47:35] INFO: Setting definition for component 'Dgidx'.
[05.24.15 13:47:36] INFO: Definition updated.
[05.24.15 13:47:36] INFO: Provisioning site from prototype...
[05.24.15 13:47:36] INFO: Finished provisioning site from prototype.
Finished updating EAC.
Initializing record stores...
These record stores exist:
NAME TYPE STATUS
CRS_en_schema RecordStore RUNNING
CRS_en_dimvals RecordStore RUNNING
CRS_en_prules RecordStore RUNNING
CRS_en_data RecordStore RUNNING
==================================================
Dropping old record stores (errors will occur on non-existent rs):
Error during execution (check log for more info): Component instance not found: Store_en_schema
Error during execution (check log for more info): Component instance not found: Store_en_dimvals
Error during execution (check log for more info): Component instance not found: Store_en_prules
Error during execution (check log for more info): Component instance not found: Store_en_data
==================================================
Creating fresh record stores:
Successfully created component: Store_en_schema
Successfully created component: Store_en_dimvals
Successfully created component: Store_en_prules
Successfully created component: Store_en_data
==================================================
Deploying rs configs:
Successfully set recordstore configuration.
Successfully set recordstore configuration.
Successfully set recordstore configuration.
Successfully set recordstore configuration.
==================================================
Finished initializing record stores
Importing sample content...
[05.24.15 13:48:33] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:48:33] INFO: Definition has not changed.
[05.24.15 13:48:33] INFO: Packaging contents for upload...
[05.24.15 13:48:34] INFO: Finished packaging contents.
[05.24.15 13:48:34] INFO: Uploading contents to: http://JagdevSingh-PC:8006/ifcr/sites/Store/
[05.24.15 13:48:35] INFO: Finished uploading contents.
[05.24.15 13:48:37] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:48:38] INFO: Definition has not changed.
[05.24.15 13:48:38] INFO: Packaging contents for upload...
[05.24.15 13:48:38] INFO: Finished packaging contents.
[05.24.15 13:48:38] INFO: Uploading contents to: http://JagdevSingh-PC:8006/ifcr/sites/Store/content
[05.24.15 13:48:39] INFO: Finished uploading contents.
[05.24.15 13:48:41] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:48:42] INFO: Definition has not changed.
[05.24.15 13:48:42] INFO: Packaging contents for upload...
[05.24.15 13:48:42] INFO: Finished packaging contents.
[05.24.15 13:48:42] INFO: Uploading contents to: http://JagdevSingh-PC:8006/ifcr/sites/Store/pages
[05.24.15 13:48:43] INFO: Finished uploading contents.
Finished importing sample content
Importing media...
[05.24.15 13:48:45] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:48:46] INFO: Definition has not changed.
[05.24.15 13:48:46] INFO: Packaging contents for upload...
[05.24.15 13:48:46] INFO: Finished packaging contents.
[05.24.15 13:48:46] INFO: Uploading contents to: http://JagdevSingh-PC:8006/ifcr/sites/Store/media
[05.24.15 13:48:49] INFO: Finished uploading contents.
Finished importing media
Importing editors configuration...
[05.24.15 13:48:51] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.24.15 13:48:52] INFO: Definition has not changed.
[05.24.15 13:48:52] INFO: Packaging contents for upload...
[05.24.15 13:48:52] INFO: Finished packaging contents.
[05.24.15 13:48:52] INFO: Uploading contents to: http://JagdevSingh-PC:8006/ifcr/sites/Store/configuration/tools/xmgr
[05.24.15 13:48:52] INFO: Finished uploading contents.
Finished importing editors configuration
Importing templates...
Removing existing cartridge templates for Store
Setting new cartridge templates for Store
Finished setting templates
Finished importing templates
C:\Endeca\apps\Store\control>
=============================================================================
At this phase your Endeca application is ready. Next you need to configure ATG application to use this application.
Great thoughts you got there, believe I may possibly try just some of it throughout my daily life.
ReplyDeleteGoogle App Integration Chennai