Create Endeca App:
1. Go To => C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin
2. Open Command Prompt from the above location,
3. Note: deploy.bat file will call deploy.pl file from ToolAndFrameworks lib folder
4. Note: deploy.pl file will allow the system to call respective variable for creating new app
5. Follow the below steps:
C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>deploy.bat --app C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\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/01/2015 00:50:05 [deploy.pl] INFO: Starting deployment template
installation.
------------------------------------------------------------------------------
The following app modules were specified on the command line argument:
C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\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/01/2015 00:50:09 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml.
05/01/2015 00:50:09 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.1\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: CRS]
Choosing a different application name may require additional configuration on
your web application.
Application name: MyNewApp
------------------------------------------------------------------------------
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\MyNewApp, 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/01/2015 00:50:38 [deploy.pl] INFO: Deploying application into
C:\Endeca\Apps\MyNewApp
------------------------------------------------------------------------------
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.1
------------------------------------------------------------------------------
Please enter the version for CAS jar files (or hit 'enter' to use the
default). [Default: 3.1.1]
3.1.1
------------------------------------------------------------------------------
Please enter the hostname where CAS is running (or hit 'enter' to use the
default). [Default: localhost]
localhost
------------------------------------------------------------------------------
Please enter the port where CAS is running (or hit 'enter' to use the
default). [Default: 8500]
8500
------------------------------------------------------------------------------
Please enter the language code to use (or hit 'enter' to use the default).
[Default: en]
en
------------------------------------------------------------------------------
Please enter the hostname of the Workbench.
localhost
------------------------------------------------------------------------------
Please enter the preview host name. [Default: localhost]
localhost
------------------------------------------------------------------------------
Please enter the preview port number. Typical values are 7003 for WebLogic,
8080 for JBoss and Tomcat, and 9080 for WebSphere.
7003
------------------------------------------------------------------------------
Please enter the context root of the preview application. [Default: crs]
MyNewApp
------------------------------------------------------------------------------
What port is the Workbench running? [Default: 8006]
8006
------------------------------------------------------------------------------
What port should be used for the Live Dgraph? [Default: 15000]
15000
------------------------------------------------------------------------------
What port should be used for the Authoring Dgraph? [Default: 15002]
15002
------------------------------------------------------------------------------
What port should be used for LogServer? [Default: 15010]
15010
05/01/2015 00:51:35 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\app-templates\base_descriptor.xml.
05/01/2015 00:51:36 [deploy.pl] INFO: Processing install with id 'Dgraph'
05/01/2015 00:51:37 [AppDescriptorReader] INFO: Parsing application descriptor
file
C:\ATG\ATG10.1.2\CommerceReferenceStore\Store\Storefront\deploy\deploy.xml.
05/01/2015 00:51:37 [deploy.pl] INFO: Processing install with id 'CRSApp'
05/01/2015 00:51:38 [deploy.pl] INFO: Application successfully deployed.
C:\Endeca\ToolsAndFrameworks\3.1.1\deployment_template\bin>
Note: Verify our new app will be created under C:/Endeca/Apps folder. if it is created. then we are successfully created the new app.
Run Initial_Services.bat
After Completion of new app creation. We must run initial_services,bat file to initialize all the services for the newly created app. Follow the below steps,
1. Go To => C:\Endeca\Apps\MyNewApp\control folder
2. Open the Command Prompt
3. Enter C:\Endeca\Apps\MyNewApp\control\initialize_services.bat
4. Check the Command Prompt log whether agraph, dgraph are created or not.
5. Find below the log details
C:\Endeca\Apps\MyNewApp\control> initialize_services.bat
Setting EAC provisioning and performing initial setup...
[05.01.15 01:30:28] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.01.15 01:30:28] INFO: Setting definition for application 'MyNewApp'.
[05.01.15 01:30:30] INFO: Setting definition for host 'AuthoringMDEXHost'.
[05.01.15 01:30:30] INFO: Setting definition for host 'LiveMDEXHostA'.
[05.01.15 01:30:30] INFO: Setting definition for host 'ReportGenerationHost'.
[05.01.15 01:30:30] INFO: Setting definition for host 'WorkbenchHost'.
[05.01.15 01:30:31] INFO: Setting definition for host 'ITLHost'.
[05.01.15 01:30:31] INFO: Setting definition for component 'AuthoringDgraph'.
[05.01.15 01:30:33] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgidx-output'.
[05.01.15 01:30:35] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-forge-output'.
[05.01.15 01:30:36] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-cumulative-partials'.
[05.01.15 01:30:37] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-workbench-dgraph-config'.
[05.01.15 01:30:38] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-input'.
[05.01.15 01:30:39] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-cumulative-partials'.
[05.01.15 01:30:41] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgraph-config'.
[05.01.15 01:30:42] INFO: Setting definition for component 'DgraphA1'.
[05.01.15 01:30:42] INFO: Setting definition for script 'PromoteAuthoringToLive'.
[05.01.15 01:30:42] INFO: Setting definition for custom component 'WorkbenchManager'.
[05.01.15 01:30:43] INFO: Updating provisioning for host 'ITLHost'.
[05.01.15 01:30:43] INFO: Updating definition for host 'ITLHost'.
[05.01.15 01:30:43] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.01.15 01:30:44] INFO: [ITLHost] Starting shell utility 'mkpath_-data-workbench-temp'.
[05.01.15 01:30:45] INFO: [ITLHost] Starting shell utility 'mkpath_-data-processing'.
[05.01.15 01:30:47] INFO: Setting definition for custom component 'IFCR'.
[05.01.15 01:30:47] INFO: Updating provisioning for host 'ITLHost'.
[05.01.15 01:30:47] INFO: Updating definition for host 'ITLHost'.
[05.01.15 01:30:47] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.01.15 01:30:49] INFO: [ITLHost] Starting shell utility 'mkpath_-'.
[05.01.15 01:30:50] INFO: Setting definition for component 'LogServer'.
[05.01.15 01:30:50] INFO: [ReportGenerationHost] Starting shell utility 'mkpath_-reports-input'.
[05.01.15 01:30:51] INFO: Setting definition for script 'DaySoFarReports'.
[05.01.15 01:30:51] INFO: Setting definition for script 'DailyReports'.
[05.01.15 01:30:52] INFO: Setting definition for script 'WeeklyReports'.
[05.01.15 01:30:52] INFO: Setting definition for script 'DaySoFarHtmlReports'.
[05.01.15 01:30:52] INFO: Setting definition for script 'DailyHtmlReports'.
[05.01.15 01:30:52] INFO: Setting definition for script 'WeeklyHtmlReports'.
[05.01.15 01:30:52] INFO: Setting definition for component 'WeeklyReportGenerator'.
[05.01.15 01:30:52] INFO: Setting definition for component 'DailyReportGenerator'.
[05.01.15 01:30:53] INFO: Setting definition for component 'DaySoFarReportGenerator'.
[05.01.15 01:30:53] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.
[05.01.15 01:30:53] INFO: Setting definition for component 'DailyHtmlReportGenerator'.
[05.01.15 01:30:54] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'.
[05.01.15 01:30:54] INFO: Setting definition for script 'BaselineUpdate'.
[05.01.15 01:30:54] INFO: Setting definition for script 'PartialUpdate'.
[05.01.15 01:30:54] INFO: Setting definition for component 'ConfigurationGeneratorForge'.
[05.01.15 01:30:54] INFO: Setting definition for component 'Forge'.
[05.01.15 01:30:55] INFO: [ITLHost] Starting shell utility 'mkpath_-data-incoming'.
[05.01.15 01:30:56] INFO: Setting definition for component 'PartialForge'.
[05.01.15 01:30:57] INFO: [ITLHost] Starting shell utility 'mkpath_-data-partials-incoming'.
[05.01.15 01:30:59] INFO: Setting definition for component 'Dgidx'.
[05.01.15 01:30:59] INFO: Definition updated.
[05.01.15 01:30:59] INFO: Provisioning site from prototype...
[05.01.15 01:31:02] 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: MyNewApp_en_schema
Error during execution (check log for more info): Component instance not found: MyNewApp_en_dimvals
Error during execution (check log for more info): Component instance not found: MyNewApp_en_prules
Error during execution (check log for more info): Component instance not found: MyNewApp_en_data
==================================================
Creating fresh record stores:
Successfully created component: MyNewApp_en_schema
Successfully created component: MyNewApp_en_dimvals
Successfully created component: MyNewApp_en_prules
Successfully created component: MyNewApp_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.01.15 01:31:52] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.01.15 01:31:53] INFO: Definition has not changed.
[05.01.15 01:31:53] INFO: Packaging contents for upload...
[05.01.15 01:31:53] INFO: Finished packaging contents.
[05.01.15 01:31:53] INFO: Uploading contents to: http://localhost:8006/ifcr/sites/MyNewApp/
[05.01.15 01:31:54] INFO: Finished uploading contents.
Finished importing sample content
Importing media...
Finished importing media
Importing editors configuration...
[05.01.15 01:31:56] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[05.01.15 01:31:57] INFO: Definition has not changed.
[05.01.15 01:31:57] INFO: Packaging contents for upload...
[05.01.15 01:31:57] INFO: Finished packaging contents.
[05.01.15 01:31:57] INFO: Uploading contents to: http://localhost:8006/ifcr/sites/MyNewApp/configuration/tools/xmgr
[05.01.15 01:31:57] INFO: Finished uploading contents.
Finished importing editors configuration
Importing templates...
Removing existing cartridge templates for MyNewApp
Setting new cartridge templates for MyNewApp
Finished setting templates
Finished importing templates
Final Step:
Verify MyNewApp in Endeca Workbench by accessing below URL
http://localhost:8006
 |
| Endeca Workbench |
Thats it: Endeca App Created successfully, Follow these methods for any new app
