Showing posts with label Deployment Template. Show all posts
Showing posts with label Deployment Template. Show all posts

How to remove Endeca application entry from Workbench when user deleted complete project folder from the Endeca box without following clean removal steps and application entry is still registered with IFCR?

Problem Statement:  How to remove Endeca application entry from Workbench when user deleted complete project folder from the Endeca box without following clean removal steps and application entry is still registered with IFCR?

 ERROR Message: 05.26.16 09:16:24] SEVERE: Caught an exception while invoking method 'run' on object 'InitialSetup'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.utility.IFCRUtility$HttpStatusException
com.endeca.soleng.eac.toolkit.utility.IFCRUtility execute - Precondition Failed (412): Cannot copy JcrNodeResource, type=endeca/site, superType=null, path=/prototype/default to /sites/CRSen: destination exists

 Solution: 
1) Create the new Endeca application [ex: CRSen] with the same name using deployment template
/opt/app/endeca/ToolsAndFrameworks/3.1.2/deployment_template/bin]$ ./deploy.sh --app ../../reference/discover-data/deploy.xml 

2) Run Application provision command   
/opt/app/endeca/apps/CRSen/control$]./initialize_services.sh

3) Use runcommand.sh|bat to remove app
/opt/app/endeca/apps/CRSen/control$]./runcommand.sh --remove-app

 How to create new application using deployment template?

/opt/app/endeca/ToolsAndFrameworks/3.1.2/deployment_template/bin]$ ./deploy.sh --app ../../reference/discover-data/deploy.xml

 ------------------------------------------------------------------------------
   Found version 6.1 of the Endeca IAP installed in directory
   /opt/app/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?
>Hit Enter

 ------------------------------------------------------------------------------
     Deployment Template installation script.

     This script creates the directory structure for your
     deployment and installs configuration files and scripts
     into the directory structure.
  
05/26/2016 09:14:19 [deploy.pl] INFO:  Starting deployment template
   installation.

 ------------------------------------------------------------------------------
   The following app modules were specified on the command line argument:

   ../../reference/discover-data/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/26/2016 09:14:22 [AppDescriptorReader] INFO:  Parsing application descriptor
   file ../../reference/discover-data/deploy.xml.
05/26/2016 09:14:22 [AppDescriptorReader] INFO:  Parsing application descriptor
   file
   /opt/app/endeca/ToolsAndFrameworks/3.1.2/deployment_template/lib/../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:
CRSen

 ------------------------------------------------------------------------------
   Specify the path into which the application will be deployed. The specified
   directory must exist and cannot contain spaces.

   For example, to deploy into /localdisk/apps/CRSen, specify the path as
   /localdisk/apps.

   Deployment directory:
/opt/app/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/26/2016 09:14:40 [deploy.pl] INFO:  Deploying application into
   /opt/app/endeca/apps/CRSen

 ------------------------------------------------------------------------------
   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/26/2016 09:14:54 [AppDescriptorReader] INFO:  Parsing application descriptor
   file
   /opt/app/endeca/ToolsAndFrameworks/3.1.2/deployment_template/lib/../app-templates/base_descriptor.xml.
05/26/2016 09:14:54 [deploy.pl] INFO:  Processing install with id 'Dgraph'
05/26/2016 09:14:54 [AppDescriptorReader] INFO:  Parsing application descriptor
   file ../../reference/discover-data/deploy.xml.
05/26/2016 09:14:54 [deploy.pl] INFO:  Processing install with id
   'DefaultTemplateManagerApp'
05/26/2016 09:14:54 [deploy.pl] INFO:  Application successfully deployed.
Posted by 3 comments:
Labels: , ,

Endeca Scripts: Initialize_services.sh Fails With HTTP 404 Error

Problem Statement:

When trying to run initialize services in a newly deployed application the following error is returned
INFO: Provisioning site from prototype...
Jan 11, 2016 3:15:20 PM com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript
SEVERE: Not Found (404):
Occurred while executing line 3 of valid BeanShell script:
[[

1|
2|
3| IFCR.provisionSite();
4| WorkbenchManager.updateWsConfig();
5|
6|
]]

Solution:
This error is thrown when the version of the Deployment Template being used is incompatible with the workbench version. Download the correct version of the deployment template for your version of workbench and redeploy the application.
Posted by 2 comments:
Labels: ,

How to create Endeca Discover Electronics Reference Application using Deployment Template? - Deployment Template

To deploy the Discover Electronics reference application:

1. Ensure that the Endeca Tools Service is running.

2. If you haven't already, create a directory for deployed Endeca applications, such as C:\Endeca\apps on Windows, or /usr/local/endeca/apps on UNIX.

3. Run the Deployment Template to deploy the application:

    a) Open a command prompt or command shell.

    b) Navigate to the \ToolsAndFrameworks\\deployment_template\bin
       directory on Windows, or /ToolsAndFrameworks/deployment_template/bin on UNIX.

    c) Run the deploy script with the --app flag and an argument that specifies the path to the deploy.xml descriptor file for Discover Electronics:For example:
      C:\Endeca\ToolsAndFrameworks\3.1.0\deployment_template\bin>deploy --app C:\Endeca\ToolsAndFrameworks\3.1.0\reference\discover-data\deploy.xml

    d) Confirm the Platform Services installation directory.

    e) Select y to install a base application.

    f) Specify Discover as the application name.
      Note:The application configuration depends on this name and case sensitivity is important.

    g) Specify the application directory previously created for Endeca applications.This is typically a directory, such as C:\Endeca\apps on Windows or /usr/local/endeca/apps on UNIX.

    h) Oracle recommends using the default options for subsequent prompts.

4. Navigate to the control directory of your new deployed application.
  This is located under your application directory,
  for example:C:\Endeca\apps\Discover\control on Windows.

5. Initialize the application and load the baseline data and templates:
    a) Run the initialize_services script.
      This script does the following:
        • Provisions the application in the Endeca Application Controller.
        • Uploads sample templates and configuration to the application.
        • Uploads sample content and media to the application. (This action occurs only if you are using Experience Manager.)

 b) Run the load_baseline_test_data script.

c) Run the baseline_update script.

d) Run the promote_content script.

6. Confirm that the Discover Electronics reference applications are running:
    • Navigate to http://localhost:8006/discover-authoring to view the authoring version of the Discover application.
    • Navigate to http://localhost:8006/discover to view the live version of the Discover application.

 For more details refer below Oracle  documentation:

 https://docs.oracle.com/cd/E35827_01/ToolsAndFrameworks.310/pdf/TFInstallGuide.pdf
Page #20 & 21
Posted by 1 comment:
Labels: ,

How to find Endeca component versions Ex: Dgraphs, Deployment template, Forge, CAS and Tools & Framework? - Endeca component versions

MDEX: 

Use below command
C:\Endeca\MDEX\6.5.1\bin>dgraph.exe --version
Endeca dgraph version 6.5.1.829811
Supports opti-XML version : 2.00
Supports binary IR version: 640
Interface specification :
  READS:dgidx=6.3.0a WRITES:dgraph=IR640
ICU version 51.2
OLT version OLT 1.4 140319
OpenSSL 1.0.0k 5 Feb 2013 

Deployment Template:

Use below command
C:\Endeca\apps\Discover\control>runcommand.bat --version
Deployment Template: 11.1.0

Platform Services: 

Use below command
C:\Endeca\PlatformServices\11.1.0\bin>forge.exe --version
INFO    01/19/16 03:14:25.991 UTC (1453173265991)       FORGE   {config}: forge 4.1-Internal-foo@bar-baz-beetle ("i86pc-MINGW32_NT-6.1")
INFO    01/19/16 03:14:25.996 UTC (1453173265995)       FORGE   {config}: Copyright 2001-2012 Oracle Endeca Technologies, Inc.
INFO    01/19/16 03:14:26.000 UTC (1453173265999)       FORGE   {config}: Command Line: forge.exe --version
forge 4.1-Internal-foo@bar-baz-beetle ("i86pc-MINGW32_NT-6.1")
Copyright 2001-2012 Oracle Endeca Technologies, Inc.
INFO    01/19/16 03:14:26.041 UTC (1453173266040)       FORGE   {config}: Initialized cURL, version: libcurl/7.16.4 OpenSSL/0.9.8 zlib/1.2.3
INFO    01/19/16 03:14:26.045 UTC (1453173266044)       FORGE   {config}: Forge completed successfully.

CAS:

Use below jar to find the version: 
C:\Endeca\CAS\11.1.0\lib\cas-cmd>cas-cmd-11.1.0.jar

Tools and Framework: 

Version is displayed on the login screen

Posted by No comments:
Labels: , , , ,

Creating the Endeca EAC Application via Scripts - Deployment Template

How to create the Endeca EAC application?
  1. On the machine where Oracle Commerce Guided Search with Experience Manager is installed, create the directory where the EAC application will reside
    Example: /opt/app/endeca/apps 

  2. Copy the <ATG11dir>/CommerceReferenceStore/Store/Storefront/deploy directory to a temporary location on the machine where Oracle Commerce Guided Search with Experience Manager is installed.
    Example: /opt/app/ATGtemp

  3. Execute the deploy script. 
    Example:
    /opt/app/endeca/ToolsAndFrameworks/11.1.0/deployment_template/bin >./deploy.sh --app /opt/app/ATGtemp/deploy/deploy.xml

  4. Press Enter to continue with the install
  5. Enter the following information for the script prompts:
    • Enter N to install a base deployment.

    • Enter CRS for the name of the application.

    • Enter the full path to the Apps directory, 
      Example: /opt/app/endeca/apps 
    • Enter the EAC port (default is 8888)

    • Workbench port number [8006]

    • Dgraph1 (Live Dgraph) port (default is 15000)

    • Authoring Dgraph port (default is 15002)

    • LogServer port (default is 15010)

    • Enter the CAS install directory using UNIX-style forward slashes, even if on Windows. 
      Example:/opt/app/endeca/CAS/11.1.0

    • Enter the CAS version number (default is 11.1.0).

    • Enter the CAS hostname (default is localhost).

    • Enter the CAS port (default is 8500).

    • Enter the language code (default is en).

    • Enter the fully-qualified Workbench hostname (localhost)

    • Production application server host name. This is the host where the ATGProduction server will be running. [localhost]

    • Production application server HTTP port number. 
      IMPORTANT: If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.

    • Preview host name [localhost]

    • Preview port number.

      If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere.

    • Context root of the preview application [crs]

    • Host name of the user segment server. This is the server that will respond to Experience Manager requests for Business Control Center user segment data. Oracle recommends using the Content Adminstration server (also called the ATGPublishing server in this guide). [localhost]

    • HTTP port of the user segment server.  
      IMPORTANT: If you are following the instructions in this guide, these values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and 9081 for WebSphere. 

    • Path for the Oracle Wallet jps-config.xml file
      Example:  /opt/app/endeca/ToolsAndFrameworks/11.1.0/server/workspace/credential_store/jps-config.xml
    • Application configuration archive path. This is the location where content promoted using the file-based method is stored,
      Example, /opt/app/endeca/apps/CRS/data/workbench/application_export_archive 
    You see a message that says “Application successfully deployed” when the deployment is finished. 

  6. Change directories to the EAC applications directory, 
    Example: /opt/app/endeca/apps 
    The CRS application directory is added as child of the /apps directory.

How to provision the EAC application?
  1. In a UNIX shell, change directories to your EAC application’s /control directory,
    Example: /opt/app/endeca/apps/CRS/control

  2. Execute the initialize_services.sh script.
    ./initialize_services.sh

Posted by 4 comments:
Labels: , ,

Endeca Deployment Template Module for Product Catalog Integration - Usage Guide

Posted by 1 comment:
Labels: ,

Endeca Guided Search and Endeca deployment template ports - Endeca Ports


Service Ports:



Ports used during Endeca application creation using deployment template:

FYI:

Default ports can be replaced with any other port numbers but Port numbers can be no larger than 32767.
Posted by No comments:
Labels: ,
Subscribe to: Posts (Atom)