Oracle Endeca Commerce 2.1.2 Installation And Configuration

Posted by in Uncategorized

Oracle Endeca Commerce 2.1.2

Introduction

Endeca was founded on the simple idea that users want to explore data interactively in real time relying on a friendly, intuitive interface, regardless of the scale and complexity of the underlying data. Users need to search, navigate, and analyse all of their data, often in large and multiple data sources, “slicing and dicing” across any dimension, and drilling down to the finest grain of detail or zooming out to an aggregate view. At the same time, users need an application that responds intelligently to their current navigation state, guiding them along valid paths and eliminating invalid choices, or “dead ends.” Users should experience simple, intuitive navigation even as they perform the equivalent of extremely complex, multi-dimensional database intersection queries.

Oracle Endeca Commerce, based on the Endeca MDEX Engine, is a powerful technology designed to help you build intuitive Guided Navigation applications. Guided Navigation not only tells users the results of their query, it also tells them all the valid “next-step questions” they can ask to refine and explore further, while eliminating the frustrating reply of “No Results Found”. These next-steps are re-ranked and re-organized with each click, creating a much more productive and satisfying navigation experience for your users.

Oracle Endeca Commerce is comprised of three major components.

• Endeca Information Transformation Layer (ITL)

• Endeca MDEX Engine

• Endeca Application Tier

The components interact with your data sources and application as shown in the figure:

The Endeca Information Transformation Layer (ITL) reads your raw source data and manipulates it into a set of Oracle Endeca MDEX Engine indices. The ITL consists of the Content Acquisition System (which includes the Endeca CAS Server and Console, the CAS API and the Endeca Web Crawler), and the Data Foundry (which includes data-manipulation programs such as Forge).The Endeca ITL components are run offline at intervals that are appropriate for your business requirements.

The Oracle Endeca MDEX Engine is the query engine that is the core of Oracle Endeca Commerce. The MDEX Engine consists of the Indexer (Dgidx), the Dgraph, and the Agraph. The MDEX Engine loads the indices generated by the indexing component of the Endeca Information Transformation Layer. Although the Indexer (also known as Dgidx) is installed as part of the MDEX Engine package, in effect it is part of the ITL process. After the indices are loaded, the MDEX Engine receives queries from the Endeca Application Tier, executes them against the loaded indices, and returns the results to the client application. The Application Tier provides an interface to the MDEX Engine via the Endeca Assembler. The Assembler acts as a language-agnostic interface for aggregating and sending queries to the MDEX Engine, and executing any necessary post-processing on the results. The Endeca MDEX Engine and Endeca Application Tier are both online processes, meaning they must remain running as long as you want clients to have access to your data set.

Installing Oracle Endeca Commerce and Deploying the WineApp Reference Application

This install is aimed at installing the Oracle endeca Commerce with all the required componnets and Deploying the WineApp Reference Application to examine a test data set in a full-featured application. We also aim at launching the mobile application for Endeca.

Installation packages for Endeca Web Commerce

Oracle Endeca Commerce Version 2.1.2 is made up of the installation packages listed below.

• MDEX Engine 6.2.2.

• Platform Services 6.1.3.

• Experience Managaer 2.1.2.

• Endeca Presentation API 6.2.2.

• Contnet Assembler APIs for java 2.1.2.

• Content Acquisition System (CAS) 3.0.2.

• Deployment Template 3.2.2

• Endeca for Mobile 1.2.2.

• Endeca for Social 1.2.2.

• Developer Studio 6.1.3. (Optional.)

MDEX Engine overview

The Endeca MDEX Engine is the indexing and query engine that provides the backbone for all Endeca solutions.

The MDEX Engine uses proprietary data structures and algorithms that allow it to provide real-time

responses to client requests. The MDEX Engine stores the indices that were created by the Endeca

Information Transformation Layer (ITL). After the indices are stored, the MDEX Engine receives client requests via the application tier, queries the indices, and then returns the results.

The MDEX Engine is designed to be stateless. This design requires that a complete query be sent to

the MDEX Engine for each request. The stateless design of the MDEX Engine facilitates the addition

of MDEX Engine servers for load balancing and redundancy. Because the MDEX Engine is stateless, any replica of an MDEX Engine on one server can reply to queries independently of a replica on other MDEX Engine servers.

Platform Services overview

The Endeca Platform Services package consists of a number of components that are used to build

Endeca applications in support of the Endeca MDEX Engine.

Two of the major components of the Endeca Platform Services package are the Endeca Information

Transformation Layer (which includes Forge and other Data Foundry components) and the Endeca

Application Controller (EAC).

Presentation API overview

The Endeca Presentation API provides interfaces to the Endeca MDEX Engine and Log Server. The

Endeca Presentation API must be installed on the machine that hosts the Web application server.

The Presentation API package includes the Java version of the API only (JAR files, Javadoc,

and Installation and Release Notes file.)

Endeca Workbench overview

Endeca Workbench is a suite of tools that brings together best-in-class Web-site management

capabilities including merchandising, Content Spotlighting, search configuration, and usage reporting.

In addition to these powerful tools for business users, Endeca Workbench provides features for system administrators to configure the resources used by an Endeca implementation, monitor its status, start and stop system processes, and download an implementation’s instance configuration for debugging and troubleshooting purposes.

The Endeca Workbench package contains the following components:

• Endeca Tools Service

• The appropriate edition of Endeca Workbench for the product you purchased.

In addition, the installation includes a version of the Endeca JSP reference application, which serves

as the default preview application in Endeca Workbench.

About the Deployment Template

The Deployment Template provides a collection of operational components that serve as a starting

point for development and application deployment.

The template includes the complete directory structure required for deployment, including Endeca

Application Controller (EAC) scripts, configuration files, and batch files or shell scripts that wrap common script functionality.

The Deployment Template is the recommended method for building your application deployment

environment.

ENVIRONMENT

For simplicity and ease of testing, the implementation is done on a single node.

Host Name: atg.ibizsoft.com

Machine: 192.455.23.61

OS: Oracle Enterprise Linux 5.5 x86_64

Installing the MDEX Engine 6.2.2

The MDEX Engine software is distributed as a self-extracting TAR file and install script.

Our Endeca Installation will be done under the installation target directory /d03/endeca.

1. Download the MDEX Engine package “V31176-01” from the Oracle Software Delivery Cloud.

2. Extract the Endeca Platform Services package to the directory /d03.

The name of the extracted installation file is “mdex_6.2.2.621294_x86_64pc-linux.sh”.

$cd /d03

$ ls

mdex_6.2.2.621294_x86_64pc-linux.sh

3. Run the installation script with the following command:

$ ./ mdex_6.2.2.621294_x86_64pc-linux.sh –target /d03

MDEX 6.2.2 install for x86_64pc-linux

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are âcommercial computer softwareâupplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.

No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

About to extract 461188 KB in /d03.

Available disk space in /d03: 352419756 KB.

Uncompressing MDEX 6.2.2 for x86_64pc-linux…………………………………………………….

Configuring Endeca MDEX 6.2.2 for x86_64pc-linux …..

Configuration of Endeca MDEX 6.2.2 for x86_64pc-linux done

Please run the following command to set your environment variables:

Boure, Bash or Korn:

source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

csh or tcsh:

source /d03/endeca/MDEX/6.2.2/mdex_setup_csh.ini

4. After installation, the installer prompts you to run the mdex_setup script that sets the

ENDECA_MDEX_ROOT environment variable.

Run mdex_setup.

# This file was created by the MDEX install.

# It is to be used to setup the required

# environment variables.

# Usage:

# source mdex_setup_sh.ini

###############################################################

# Local variables used by the MDEX Install program.

ENDECA_MDEX_ROOT=/d03/endeca/MDEX/6.2.2

export ENDECA_MDEX_ROOT

PATH=$ENDECA_MDEX_ROOT/bin:$PATH

export PATH

$ source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

The mdex_setup script sets up the environment variable ENDECA_MDEX_ROOT that points to

MDEX/6.2.2. The script also adds the utilities directory and the MDEX Engine binaries to the

search path.

$ echo $ENDECA_MDEX_ROOT

/d03/endeca/MDEX/6.2.2

5. Check the ENDECA_MDEX_ROOT directory for the contents created.

$ cd /d03/endeca/MDEX/6.2.2

$ ls -l

total 48

drwxr-xr-x 3 endeca dba 4096 Mar 1 21:08 bin

drwxr-xr-x 6 endeca dba 4096 Mar 1 20:59 conf

drwxr-xr-x 3 endeca dba 4096 Mar 1 20:58 data

drwxr-xr-x 2 endeca dba 4096 Mar 1 21:08 doc

drwxr-xr-x 4 endeca dba 4096 Mar 1 21:08 lib

drwxr-xr-x 2 endeca dba 4096 Mar 1 21:08 lib64

-rw-r–r– 1 endeca dba 508 Jul 18 00:33 mdex_setup_csh.ini

-rw-r–r– 1 endeca dba 529 Jul 18 00:33 mdex_setup_sh.ini

-rw-r–r– 1 endeca dba 9652 Mar 1 21:08 README.txt

drwxr-xr-x 4 endeca dba 4096 Mar 1 21:08 xquery

oS?)n ?EPErgin-top:0in;margin-right:-1.15pt;margin-bottom: 0in;margin-left:21.3pt;margin-bottom:.0001pt’>

Uncompressing MDEX 6.2.2 for x86_64pc-linux……………………………………………………. …………………………………………………………………………………………………………………………………….. …………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………….

Configuring Endeca MDEX 6.2.2 for x86_64pc-linux …..

Configuration of Endeca MDEX 6.2.2 for x86_64pc-linux done

Please run the following command to set your environment variables:

Bourne, Bash or Korn:

source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

csh or tcsh:

source /d03/endeca/MDEX/6.2.2/mdex_setup_csh.ini

4. After installation, the installer prompts you to run the mdex_setup script that sets the

ENDECA_MDEX_ROOT environment variable.

Run mdex_setup.

cat /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

###############################################################

# Endeca MDEX Environment Settings

cat /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

###############################################################

# Endeca MDEX Environment Settings

Installing the MDEX Engine 6.2.2

# This file was created by the MDEX install.

# It is to be used to setup the required

# environment variables.

# Usage:

# source mdex_setup_sh.ini

###############################################################

# Local variables used by the MDEX Install program.

ENDECA_MDEX_ROOT=/d03/endeca/MDEX/6.2.2

export ENDECA_MDEX_ROOT

PATH=$ENDECA_MDEX_ROOT/bin:$PATH

export PATH

$ source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

The mdex_setup script sets up the environment variable ENDECA_MDEX_ROOT that points to

MDEX/6.2.2. The script also adds the utilities directory and the MDEX Engine binaries to the

search path.

$ echo $ENDECA_MDEX_ROOT

/d03/endeca/MDEX/6.2.2

5. Check the ENDECA_MDEX_ROOT directory for the contents created.

$ cd /d03/endeca/MDEX/6.2.2

$ ls -l

total 48

drwxr-xr-x 3 endeca dba 4096 Mar 1 21:08 bin

drwxr-xr-x 6 endeca dba 4096 Mar 1 20:59 conf

drwxr-xr-x 3 endeca dba 4096 Mar 1 20:58 data

drwxr-xr-x 2 endeca dba 4096 Mar 1 21:08 doc

drwxr-xr-x 4 endeca dba 4096 Mar 1 21:08 lib

drwxr-xr-x 2 endeca dba 4096 Mar 1 21:08 lib64

-rw-r–r– 1 endeca dba 508 Jul 18 00:33 mdex_setup_csh.ini

-rw-r–r– 1 endeca dba 529 Jul 18 00:33 mdex_setup_sh.ini

-rw-r–r– 1 endeca dba 9652 Mar 1 21:08 README.txt

drwxr-xr-x 4 endeca dba 4096 Mar 1 21:08 xquery

Installing Platform Services 6.1.3

The software is distributed as a self-extracting TAR file and install script.

1. Download the Endeca Platform Services 6.1.3 package “V33316-01” from the Oracle Software

Delivery Cloud.

2. Extract the Endeca Platform Services package to the /d03 directory.

The name of the extracted installation file is “platformservices_613654721_x86_64pc-linux.sh”

$ cd /d03/

$ ls

endeca platformservices_613654721_x86_64pc-linux.sh

3. Run the install script with the –target flag, which specifies the absolute path of the target

installation directory.

$ ./platformservices_613654721_x86_64pc-linux.sh –target /d03

Endeca Platform Services 6.1.3 install for x86_64pc-linux

Oracle and Java are registered trademarks of Oracle and/or itsaffiliates. Other names may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group.This software and related documentation are provided under a license

agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted

in your license agreement or allowed by law, you may not use, copy,reproduce, translate, broadcast, modify, license, transmit, distribute,

exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this

software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice

and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Acquisition Regulation and agency-specific supplemental regulations.As such, use, duplication, disclosure, modification, and adaptation

of the programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, shall be

subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or

intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use

this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy,

and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this

software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties.

Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to

third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages

incurred due to your access to or use of third-party content, products, or services.Verifying archive integrity…All good.

Uncompressing Endeca Platform Services 6.1.3 for x86_64pc-linux………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………

Configuring Endeca Platform Services 6.1.3 for x86_64pc-linux ….

Configuring the Endeca installed Perl 5.8.3 on your environment.

Configure the ports your Endeca Instance will utilize.

Please enter the port number of the Endeca HTTP service. The typical default is 8888.

Please enter a value: 5555

Please enter the shutdown port number of the Endeca HTTP service. The typical default is 8090.

: 5090

Please enter the port number of the Endeca Control System JCD, or nothing if you do not plan to use a Control System environment. The typical default is 8088.

: 5088

Would you like this installation configured to run the Endeca Application Controller (EAC)? (Y/N)?

(Please note: this will also install the EAC Agent)

: Y

Please enter the root of your Endeca MDEX Engine installation. The root directory path typically includes the version number. Leave blank if there is no Endeca MDEX Engine installed. (default: /d03/endeca/MDEX/6.2.2)

: /d03/endeca/MDEX/6.2.2

Would you like to install the reference implementations? (Y/N)?

: Y

Please run the following command to set your environment variables:

Bourne, Bash or Korn:

source /d03/endeca/PlatformServices/workspace/setup/installer_sh.ini

csh or tcsh:

source /d03/endeca/PlatformServices/workspace/setup/installer_csh.ini

4. Values entered for the different services:

? Port number of the Endeca HTTP service: 5555.

? Shutdown port number of the Endeca HTTP service: 5090.

? Port number of the Endeca Control System: 5088

? Would you like this installation configured to run the Endeca Application Controller (EAC): Y

? The root directory path of your Endeca MDEX Engine installation: /d03/endeca/MDEX/6.2.2

? Would you like to install the reference implementations: Y

5. The installation is complete when the screen displays a reminder message about setting the

environment variables.

6.Check the install directory for contents created under the PlatformServices installation.

$ cd /d03/endeca/PlatformServices/6.1.3

bin cadk conf doc j2sdk lib lib64 perl README.txt setup tools utilities version.txt workspace_template

7. Source the environment. After the installation is finished, run an installer script to set the Platform Services environment variables such as ENDECA_ROOT, as well as additional variables that are used internally.

$ cat /d03/endeca/PlatformServices/workspace/setup/installer_sh.ini

###############################################################

# Endeca Platform Services Environment Settings

# This file was created by the Endeca install.

# It is to be used to setup the required

# environment variables.

# Usage:

# source installer_sh.ini

###############################################################

# Local variables used by the Endeca Install program.

VERSION=6.1.3

BUILD_VERSION=6.1.3.654721

ARCH_OS=x86_64pc-linux

PRODUCT=IAP

ENDECA_INSTALL_BASE=/d03

# Environment variables required to run the Endeca Platform Services software.

ENDECA_ROOT=/d03/endeca/PlatformServices/6.1.3

export ENDECA_ROOT

PERLLIB=$ENDECA_ROOT/lib/perl:$ENDECA_ROOT/lib/perl/Control:$ENDECA_ROOT/perl/lib:$ENDECA_ROOT/perl/lib/site_perl:$PERLLIB

export PERLLIB

PERL5LIB=$ENDECA_ROOT/lib/perl:$ENDECA_ROOT/lib/perl/Control:$ENDECA_ROOT/perl/lib:$ENDECA_ROOT/perl/lib/site_perl:$PERL5LIB

export PERL5LIB

PATH=$ENDECA_ROOT/bin:$ENDECA_ROOT/perl/bin:$ENDECA_ROOT/utilities:$PATH

export PATH

ENDECA_CONF=/d03/endeca/PlatformServices/workspace

export ENDECA_CONF

# ENDECA_REFERENCE_DIR points to the directory the reference implementations

# are installed in. It is not required to run any Endeca software.

ENDECA_REFERENCE_DIR=/d03/endeca/PlatformServices/reference

export ENDECA_REFERENCE_DIR

$ source /d03/endeca/PlatformServices/workspace/setup/installer_sh.ini

$ echo $ENDECA_ROOT

/d03/endeca/PlatformServices/6.1.3

8. After installation, setting environment variables, start the Endeca HTTP Service.

Change to the endeca/PlatformServices/6.1.3/tools/server/bin directory and run

the startup.sh script.

Start the Endeca HTTP Service “ENDECA_ROOT”

$cd /d03/endeca/PlatformServices/6.1.3/tools/server/bin

$./startup.sh

Using ENDECA_ROOT: /d03/endeca/PlatformServices/6.1.3

Using ENDECA_CONF: /d03/endeca/PlatformServices/workspace

Using CATALINA_BASE: /d03/endeca/PlatformServices/workspace

Using CATALINA_HOME: /d03/endeca/PlatformServices/6.1.3/tools/server

Using CATALINA_TMPDIR: /d03/endeca/PlatformServices/workspace/temp

Using JRE_HOME: /d03/endeca/PlatformServices/6.1.3/j2sdk

Using CLASSPATH: /d03/endeca/PlatformServices/6.1.3/tools/server/bin/bootstrap.jar

Installing Endeca Experience Manager 2.1.2(Workbench)

1. Download the Tools and Frameworks package “V3386-01” from the Oracle Software Delivery Cloud.

Oracle Endeca Commerce 3.1.0 Media Pack v1 for Linux x86-64

2. Extract the Experience Managaer package.

$ unzip V33386-01.zip

$ ls

xmgrworkbench_x86_64pc-linux_2.1.2.sh

3. Create a Directory for Experience Manager. This will be our Workbench install directory.

$ mkdir –p /d03/endeca/XMGR

4. Run the install script with the –target flag, which specifies the absolute path of the target

installation directory.

$ ./xmgrworkbench_x86_64pc-linux_2.1.2.sh –target /d03/endeca/XMGRWorkbench 2.1.2 install for x86_64pc-linux

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group.This software and related documentation are provided under a license

agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted

in your license agreement or allowed by law, you may not use, copy,reproduce, translate, broadcast, modify, license, transmit, distribute,

exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this

software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice

and is not warranted to be error-free. If you find any errors, please report them to us in writing.

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal. Acquisition Regulation and agency-specific supplemental regulations.As such, use, duplication, disclosure, modification, and adaptation

of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be

subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or

intended for use in any inherently dangerous applications, including that may create a risk of personal injury. If you use

this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy,

and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this

software or hardware in dangerous applications. This software or hardware and documentation may provide access to or

information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and

expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and

its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products,

or services.

Verifying archive integrity…

All good.

Uncompressing Workbench 2.1.2 for x86_64pc-linux……………………………………………………………

……………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………..

Please enter the fully qualified name, including domain information, of this host machine (atg.ibizsoft.com).

: atg.ibizsoft.com

Configure the ports your Endeca Instance will utilize.

Please enter the port number of the Oracle Endeca Tools Service. The typical default is 8006.

: 5006

Please enter the shutdown port number of the Oracle Endeca Tools Service. The typical default is 8084.

: 5084

Please enter the fully qualified host name, including domain information of the Oracle Endeca Application Controller.

: atg.ibizsoft.com

Please enter the port number of the Oracle Endeca Application Controller. The typical default is 8888.

: 5555

Please run the following command to set your environment variables:

Bourne, Bash or Korn:

source /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_sh.ini

csh or tcsh:

source /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_csh.ini

4. Values entered for the different services:

? Fully qualified name of the host machine: atg.ibizsoft.com

? Port number of the Oracle Endeca Tools Service: 5006

? Shutdown port number of the Oracle Endeca Tools Service: 5084

? Fully qualified host name the Oracle Endeca Application Controller: atg.ibizsoft.com

? Port number of the Oracle Endeca Application Controller: 5555

5. The installation is complete when the screen displays a reminder message about setting the

environment variables.

6.Check the install directory for contents created under the Experience Manager installation.

$ cd /d03/endeca/XMGR/endeca/Workbench

2.1.2 workspace

$ cd 2.1.2/

conf doc j2sdk README.txt reference server setup workspace_template

$ cd ../workspace/

conf logs reports setup state temp work

$ cat /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_sh.ini

# Environment variables required to run the Oracle Endeca Workbench software.

ENDECA_TOOLS_ROOT=/d03/endeca/XMGR/endeca/Workbench/2.1.2

export ENDECA_TOOLS_ROOT

PATH=$ENDECA_TOOLS_ROOT/bin:$PATH

export PATH

ENDECA_TOOLS_CONF=/d03/endeca/XMGR/endeca/Workbench/workspace

export ENDECA_TOOLS_CONF

Note : CATALINA_HOME=/d03/endeca/XMGR/endeca/Workbench/2.1.2/server must be set Workbench HOME.

$ /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_sh.ini

Start the Endeca Tools Service (workbench)

$ cd /d03/endeca/XMGR/endeca/Workbench/2.1.2 /server/bin

$ ./startup.sh

Checking Workbench Environment Settings

Using ENDECA_TOOLS_ROOT:

Verify the XMGR Workbench Installation:

Load Oracle Endeca Workbench in a Web browser.

This indicates the Endeca Tools service is running and that Workbench is available.

1. Start a Web browser.

2. In the URL, specify the machine name and default port of Workbench (8006).

http://atg.ibizsoft.com:5006/

To manage the Endeca Tools Service after installation: (i.e. To Start/Stop the Workbench process)

• Start the Endeca Tools Service(workbench) with the following command:

/d03/endeca/XMGR/endeca/Workbench/2.1.2/server/bin/startup.sh ($ENDECA_TOOLS_ROOT/server/bin/startup.sh)

• Stop the Endeca Tools Service(workbench) with the following command:

/d03/endeca/XMGR/endeca/Workbench/2.1.2/server/bin/shutdown.sh ($ENDECA_TOOLS_ROOT/server/bin/shutdown.sh)

Installing Endeca Presentation API 6.2.2

Pre-Requisites: -Sun JDK 1.4.2, 5.0 (1.5), and 6.0 (1.6)

-The Presentation API is supported on 64-bit operating systems.

- Ensure that the Endeca MDEX Engine is installed.

1. The Presentation API is packaged as an archive an is installed just by unarchiving it.

The software is packaged along with the Endeca MDEX Engine package.

presAPI_6.2.2.621294_x86_64pc-linux.tgz

2. Extract the file to the root drive of your Endeca installation directory.

$ cp presAPI_6.2.2.621294_x86_64pc-linux.tgz /d03/

$ tar -xvzf presAPI_6.2.2.621294_x86_64pc-linux.tgz

That extracts to create: /d03/endeca/PresentationAPI.

3. Check the install directory for contents created under the presentationAPI installation.

$ cd /d03/endeca/PresentationAPI/6.2.2

4. Copy the following Endeca files from the PresentationAPI to avoid Navigation Errors in Workbench

i) endeca_navigation.jar((Endeca Presentation API) ,

ii) endeca_logging.jar (Endeca Logging API)

iii) bcprov-jdk-version.jar (Bouncy Castle encryption implementation)

Under the PresentationAPI/6.2.2 directory, locate the appropriate APIs, and copy the APIs to the lib directory of your Web application.

On Java platforms, copy the JAR files from PresentationAPI\6.2.2\java\lib to the WEB-INF\lib directory of your Web application.

$ cd /d03/endeca/PresentationAPI/6.2.2/java/lib

bcprov-jdk14-121.jar endeca_logging.jar endeca_navigation.jar

$ cp *.jar /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps/endeca_jspref/WEB-INF/lib/

Installing Content Assembler API for Java

The Content Assembler API provides a simple interface to access template-driven content for renderingin Web-based applications.

The Content Assembler API enables a Web application to query the MDEX Engine and retrieve the

appropriate dynamic content based on a user’s navigation state or other triggers.The Content Assembler returns both Endeca query results familiar from the Presentation API or RAD API as well as a content item object that encapsulates the page configuration specified by the content administrator. All the content for a page, including the results of any additional queries needed for spotlighting or merchandising, are wrapped in the content item object, simplifying the logic in the front-end application by reducing the need to manage sub-queries in the application layer.

Pre-Requisites: The Content Assembler API requires the following components installed

- Endeca Presentation API for Java

- Endeca Workbench, if you wish to run the Content Assembler reference application in the Endeca Tools service (i.e, to run the WinApp in the Experience Manager Workbech)

1. Download the Contnet Assembler API Package “V31155-01” from the Oracle Software Delivery Cloud.

Oracle Endeca Commerce 3.1.0 Media Pack v1 for Linux x86-64

2. The Content assembler software is packaged as an archive that’s installed by extracting it.

Copy the archive file to the root drive of your Endeca installation directory.

$ cp V31155-01.zip /d03/endeca/

3. Extract the archive

$ unzip V31155-01.zip

That extracts to create: /d03/endeca/ContentAssemblerAPIs

4. Check the install directory for contents created under the ContentAssemblerAPIs

$ cd /d03/endeca/ContentAssemblerAPIs/Java/2.1.2/

doc/ lib/ README_CAJ.txt reference/ “

Before writing applications using the Content Assembler API, you must place the endeca-content-version.jar file in your application’s classpath.

After you have installed the Content Assembler API, you can deploy the reference application.

“ (source: workbench install guide)

Installing Endeca Content Acquisition System 3.0.2 on XMGR Workbench

The Endeca Content Acquisition System is a set of components that add, configure, and crawl data

sources for use in an Endeca application. Data sources include file systems, Content Management

System crawls, Web servers, and custom data sources. The Endeca Content Acquisition System

crawls data sources, converts documents and files to Endeca records and stores them for use in a

Forge pipeline.

Pre-Requisites:

CAS Console depends on Oracle Endeca Workbench.

Workbench must be installed on the machine where you install the CAS Console for Oracle Endeca Workbench.

If you are installing CAS Console, the ENDECA_TOOLS_ROOT and ENDECA_TOOLS_CONF

environment variables must be set on the machine running Oracle Endeca Workbench before

running the CAS installation program. Setting these variables happens automatically when you

restart the machine that has Oracle Endeca Workbench installed.

Version Compatability:

CAS 3.0.2 is compatible with Our installed version of MDEX Engine(6.2.2), Platform Services(6.1.3) and Experience Manager(2.1.2).

Included Components:

In this version of CAS (3.0.2), the CAS Document Conversion Module is installed and enabled as part of the CAS installation.

In CAS 3.0.1 and later, all CMS connectors are installed and enabled as part of the CAS installation.

To run a crawl against a specific CMS data source, the Content Acquisition System requires a CMS

connector.

As of this release, the Content Acquisition System supports the following CMS connectors:

• Documentum Content Server

• Documentum eRoom

• FileNet Document and Image Services

• FileNet P8

• Interwoven TeamSite

• JSR-170 compliant repositories

• Lotus Notes (Domino)

• Microsoft SharePoint (supports 2003 and 2007 repositories)

• OpenText LiveLink

1. Download the CAS installation package from the Oracle Software Delivery Cloud

2. Extract the archive

$ unzip V31482-01.zip

Locate the CAS installation file that you extracted. The name of the installation file is “cas-3.0.2-x86_64pc-linux.sh”

3. Determine an installation location for the Endeca Content Acquisition System. (/d03)

Run the CAS installation script with the –target flag, which specifies the absolute path of the target installation directory.

$ ./cas-3.0.2-x86_64pc-linux.sh –target /d03

Content Acquisition System 3.0.2 install for x86_64pc-linux

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property

laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, dist

ribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless requir

ed by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered

to U.S. Government end users are âcommercial computer softwareâ

As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the

hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently da

ngerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall b

e responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liabi

lity for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affil

iates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its

affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Verifying archive integrity…

All good.

Uncompressing Content Acquisition System 3.0.2 for x86_64pc-linux ……………………………………… ……………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………

…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………….

Please enter the port for the CAS service. The typical default is 8500.

:6500

Please enter the shutdown port for the CAS service. The typical default is 8506.

:6506

Creating the CAS service workspace.

Configuring the CAS host and port in the workspace located at /d03/endeca/CAS/3.0.2/../workspace

ENDECA_TOOLS_ROOT is set to: /d03/endeca/XMGR/endeca/Workbench/2.1.2.

ENDECA_TOOLS_CONF is set to: /d03/endeca/XMGR/endeca/Workbench/workspace.

Please enter the fully qualified name, including domain information, of the CAS server.

:atg.ibizsoft.com

Installing casconsole.xml into /d03/endeca/XMGR/endeca/Workbench/workspace/conf/Standalone/localhost.

Installing casconsole-infocenter.xml into /d03/endeca/XMGR/endeca/Workbench/workspace/conf/Standalone/localhost.

Installing war files into /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps.

Installing casconsole.properties into /d03/endeca/XMGR/endeca/Workbench/workspace/conf.

Installing CAS console into /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-extensions.xml

Backing up file /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-extensions.xml to /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-extensions.xml.07-18-2012-02-45

Installing CAS console into /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-mainMenu.xml

Backing up file /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-mainMenu.xml to /d03/endeca/XMGR/endeca/Workbench/workspace/conf/ws-mainMenu.xml.07-18-2012-02-45

CAS Console configuration with Workbench is complete. Please restart Oracle Endeca Workbench for the CAS Console to appear in Workbench.

4. Values entered for the different services:

? CAS service port: 6500

? CAS service Shutdown port: 6506

? Fully qualified name of the CAS server: atg.ibizsoft.com

5. The installation is complete when the script asks us to restart the Oracle Endeca Workbench for the CAS Console to appear in Workbench.

6. Check the install directory for contents created under the Experience Manager installation.

$ cd /d03/endeca/CAS/

3.0.2 workspace

$ cd 3.0.2/

bin cms components console doc java lib README.txt sample temp webapps workspace_template

$ cd ../workspace/

conf logs state temp

7. Restart the Workbench

$ /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/bin/startup.sh

$ /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/bin/shutdown.sh

Start the CAS Service

Navigate to /bin directory of the CAS Installation and run the script ‘cas-service.sh’

$ cd /d03/endeca/CAS/3.0.2/bin

$ nohup ./cas-service.sh &

Verify the CAS install.

Go to the Workbench URL http://atg.ibizsoft.com:5006/

You can observe the component “Data Sources” that has just been incorporated in to the workbench configuration.

Installing Endeca Deployment Template 3.2.2

1. Download the Deployment Template installation package from the Oracle Software Delivery Cloud

2. The Deployment Template software is packaged as an archive that’s installed by extracting it.

Copy the archive file to the root drive of your Endeca installation directory.

$ cp V31182-01.zip /d03/endeca/

3. Extract the archive

$ unzip V31825-01.zip

That extracts to create: /d03/endeca/ Endeca/Solutions/deploymentTemplate-3.2.2/

4. Check the install directory for contents created under the deploymentTemplate-3.2.2.

$ cd /d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/

bin/ CHANGES conf/ data/ doc/ lib/ README VERSION

2. The Deployment Template software is packaged as an archive that’s installed by extracting it.

Copy the archive file to the root drive of your Endeca installation directory.

$ cp V31182-01.zip /d03/endeca/

3. Extract the archive

$ unzip V31825-01.zip

That extracts to create: /d03/endeca/ Endeca/Solutions/deploymentTemplate-3.2.2/

4. Check the install directory for contents created under the deploymentTemplate-3.2.2.

$ cd /d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/

bin/ CHANGES conf/ data/ doc/ lib/ README VERSION

Now, You have installed the Deployment Template and are prepared to run it. Next, you run the Deployment Template to establish the Endeca project based on the sample wine Application.

Deploying the Sample application (WineApp)

The Content Assembler APIs Package provides a sample application called the Page Builder Wine App.

We deploy the Wine App application using the Deployment Template, then provision the application, run a baseline update, and view the data set in the front-end application.

As part of the deployment process the source data in

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app is copied to the /d03/endeca/apps/ContentAssemblerRefApp, and Forge processes the source data as part of the baseline update.

Setting up a directory for your deployment

Create a directory for deploying your project, /d03/endeca/apps

$ mkdir –p /d03/endeca/apps

Setting the Endeca environment variables

Set the environment variables properly to ensure that the different Endeca components can communicate with each other.

To set the Endeca environment variables:

$ source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

$ source /d03/endeca/PlatformServices/workspace/setup/installer_sh.ini

$ source /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_sh.ini

Starting the different Endeca services

Start the Endeca HTTP Service “ENDECA_ROOT”

$ cd /d03/endeca/PlatformServices/6.1.3/tools/server/bin

$ ./startup.sh

Start the Endeca Tools Service “ENDECA_TOOLS_ROOT”

$ cd /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/bin

$ ./startup.sh

Run the Deployment Template Script to deploy the sample Wine Application on XMGR Workbench

Navigate to the /deployment_template/bin directory of the Endeca installation.

Run the deploy.sh script with the –-app flag and an argument that points to deploy.xml descriptor file for the Wine application.

(with the Content Assembler API for Java installed, specify the full path to the sample application’s deploy.xml)

$ cd /d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/bin

$ ./deploy.sh –app /d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app/deploy.xml

——————————————————————————

Found version 6.1 of Platform Services installed in directory

/d03/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.

07/18/2012 03:17:31 [deploy.pl] INFO: Starting deployment template

installation.

——————————————————————————

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

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app/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]:

——————————————————————————

Enter a short name for your application.

Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$

Application name:

ContentAssemblerRefApp

——————————————————————————

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/ContentAssemblerRefApp, specify

the path as /localdisk/apps.

Deployment directory:

/d03/endeca/apps

——————————————————————————

Specify the port on which the Oracle 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:

5555

——————————————————————————

Do you want to enable integration with the Oracle Endeca Workbench?

Enable Oracle Endeca Workbench integration? [Y/N]:

——————————————————————————

Specify the port on which the Oracle Endeca Workbench is running. This is

configured in the server.xml file in the Oracle Endeca Workbench workspace

directory. Ports must be in the range 1024-65535 [default: 8006].

Oracle Endeca Workbench port:

5006

07/18/2012 03:24:23 [deploy.pl] INFO: Deploying application into

/d03/endeca/apps/ContentAssemblerRefApp

07/18/2012 03:24:23 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app/deploy.xml.

07/18/2012 03:24:23 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/lib/../conf/dgraph_eac_java_app_descriptor.xml.

——————————————————————————

The Page Builder sample templates refer to image locations within the Content

Assembler reference application. Specify the hostname of the Content

Assembler reference application. [Default: localhost]

atg.ibizsoft.com

—————————————————————————–

If you have installed the .NET Content Assembler reference application,

specify the port that IIS is listening on, which is normally port 80. If you

have installed the Java Content Assembler reference application, specify the

port that the Endeca Tools Service is listening on, which is normally port 8006.

5006

——————————————————————————

What port should be used for Dgraph1? [Default: 15000]

25000

—————————————————————————-

What port should be used for Dgraph2? [Default: 15001]

25001

——————————————————————————

What port should be used for LogServer? [Default: 15010]

25010

07/18/2012 03:26:23 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/lib/../conf/dgraph_eac_java_app_descriptor.xml.

07/18/2012 03:26:23 [deploy.pl] INFO: Processing install with id ‘Dgraph’

07/18/2012 03:26:24 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app/deploy.xml.

07/18/2012 03:26:24 [deploy.pl] INFO: Processing install with id

’DefaultTemplateManagerApp’

07/18/2012 03:26:24 [deploy.pl] INFO: Application successfully deployed.

Values entered for the different services:

? Application name: ContentAssemblerRefApp.

? Deployment directory: /d03/endeca/apps.

? EAC port: 5555

? Enable Oracle Endeca Workbench integration? [Y/N]: Y

? Oracle Endeca Workbench port: 5006

? Specify the hostname of the Content Assembler reference application: atg.ibizsoft.com

? Endeca Tools Service Port: 5006

? Dgraph1 Port: 25000

? Dgraph2 Port: 25001

? LogServer Port: 25010

Check the Contnets of the Application directory created.

$ cd /d03/endeca/apps/ContentAssemblerRefApp

$ ls

config control data dgraph.pid logs persist reports test_data

The Application successfully deployed and Deployment Template deploy script has successfully created the directory structure, configuration files and scripts for the application.

Now that we have provisioned the directories for the application, we need to initialize it.

Initializing the application and loading baseline data:

Now that the ContnetAssemblerRefApp (sample Wine App) is successfully deployed, we need to initialize the application and load the baseline data and templates.

Navigate to the control directory of the newly deployed application and run the required scripts.

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.

$cd /d03/endeca/apps/ContentAssemblerRefApp/control/

$ ./initialize_services.sh

Removing existing application provisioning…

[07.18.12 03:29:14] INFO: Removing application. Any active components will be forced to stop.

[07.18.12 03:29:15] INFO: Application ‘ContentAssemblerRefApp’ is not defined.

Setting EAC provisioning and performing initial setup…

[07.18.12 03:29:15] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 03:29:16] INFO: Setting definition for application ‘ContentAssemblerRefApp’.

[07.18.12 03:29:17] INFO: Setting definition for host ‘ITLHost’.

[07.18.12 03:29:18] INFO: Setting definition for host ‘MDEXHost’.

[07.18.12 03:29:18] INFO: Setting definition for host ‘webstudio’.

[07.18.12 03:29:18] INFO: Setting definition for script ‘BaselineUpdate’.

[07.18.12 03:29:18] INFO: Setting definition for script ‘PartialUpdate’.

[07.18.12 03:29:18] INFO: Setting definition for script ‘ConfigUpdate’.

[07.18.12 03:29:18] INFO: Setting definition for custom component ‘ConfigManager’.

[07.18.12 03:29:18] INFO: Updating provisioning for host ‘ITLHost’.

[07.18.12 03:29:18] INFO: Updating definition for host ‘ITLHost’.

[07.18.12 03:29:19] INFO: [ITLHost] Starting shell utility ‘mkpath_dgraph-config’.

[07.18.12 03:29:20] INFO: [ITLHost] Starting shell utility ‘mkpath_temp’.

[07.18.12 03:29:20] INFO: [ITLHost] Starting shell utility ‘mkpath_complete-index-config’.

[07.18.12 03:29:22] INFO: [ITLHost] Starting shell utility ‘mkpath_config’.

[07.18.12 03:29:22] INFO: Setting definition for component ‘Forge’.

[07.18.12 03:29:22] INFO: [ITLHost] Starting shell utility ‘mkpath_incoming’.

[07.18.12 03:29:23] INFO: Setting definition for component ‘PartialForge’.

[07.18.12 03:29:23] INFO: [ITLHost] Starting shell utility ‘mkpath_incoming’.

[07.18.12 03:29:25] INFO: [ITLHost] Starting shell utility ‘mkpath_cumulative-partials’.

[07.18.12 03:29:26] INFO: Setting definition for component ‘Dgidx’.

[07.18.12 03:29:26] INFO: Setting definition for component ‘Dgraph1′.

[07.18.12 03:29:27] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-dgraph-input’.

[07.18.12 03:29:28] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-cumulative-partials’.

[07.18.12 03:29:28] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-dgraph-config’.

[07.18.12 03:29:29] INFO: Setting definition for component ‘LogServer’.

[07.18.12 03:29:30] INFO: [ITLHost] Starting shell utility ‘mkpath_input’.

[07.18.12 03:29:31] INFO: Setting definition for script ‘DailyReports’.

[07.18.12 03:29:31] INFO: Setting definition for script ‘WeeklyReports’.

[07.18.12 03:29:31] INFO: Setting definition for script ‘DailyHtmlReports’.

[07.18.12 03:29:31] INFO: Setting definition for script ‘WeeklyHtmlReports’.

[07.18.12 03:29:32] INFO: Setting definition for component ‘WeeklyReportGenerator’.

[07.18.12 03:29:32] INFO: Setting definition for component ‘DailyReportGenerator’.

[07.18.12 03:29:32] INFO: Setting definition for component ‘WeeklyHtmlReportGenerator’.

[07.18.12 03:29:32] INFO: Setting definition for component ‘DailyHtmlReportGenerator’.

[07.18.12 03:29:33] INFO: Definition updated.

[07.18.12 03:29:33] INFO: Updating IAP Workbench configuration…

[07.18.12 03:29:33] INFO: Downloading config files from Web Studio.

[07.18.12 03:29:33] INFO: [ITLHost] Starting shell utility ‘emgr_update_get_ws_settings’.

[07.18.12 03:29:34] INFO: Retrieving Dev Studio configuration.

[07.18.12 03:29:34] INFO: [ITLHost] Starting copy utility ‘fetch_dev_studio_config’.

[07.18.12 03:29:35] INFO: Retrieving Web Studio configuration.

[07.18.12 03:29:35] INFO: Uploading config files to Web Studio.

[07.18.12 03:29:35] INFO: [ITLHost] Starting shell utility ‘emgr_update_update_mgr_settings’.

[07.18.12 03:29:38] INFO: Finished updating IAP Workbench.

Finished updating EAC.

Nowthat we have provisioned(the sample wine reference implementation with the Deployment Template) and initialized the application, we can run the baseline update script using

the Deployment Template and also access Endeca Workbench to check the status of the running components.

b) Run the baseline update scripts

The baseline update script runs the MDEX Engine (the indexer and the Dgraph) to index the records

and to update the MDEX Engine with the indexed data.

To run a baseline update script on the Data Processing (ITL) server:

- Run [appDir]/control/load_baseline_test_data.sh

? This script uploads the reference implementation data into the locations expected by the Deployment Template workflow, and communicates to the EAC that the data is ready for processing.

- Run [appDir]/control/baseline_update.sh script.

$ ./load_baseline_test_data.sh

Setting flag ‘baseline_data_ready’ in the EAC.

$ ./baseline_update.sh

[07.18.12 03:33:14] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 03:33:14] INFO: Definition has not changed.

[07.18.12 03:33:14] INFO: Starting baseline update script.

[07.18.12 03:33:14] INFO: Acquired lock ‘update_lock’.

[07.18.12 03:33:14] INFO: Downloading config files from Web Studio.

[07.18.12 03:33:15] INFO: [ITLHost] Starting shell utility ‘emgr_update_get_ws_settings’.

[07.18.12 03:33:17] INFO: [ITLHost] Starting shell utility ‘cleanDir_complete-index-config’.

[07.18.12 03:33:18] INFO: Retrieving Dev Studio configuration.

[07.18.12 03:33:18] INFO: [ITLHost] Starting copy utility ‘fetch_dev_studio_config’.

[07.18.12 03:33:18] INFO: Retrieving Web Studio configuration.

[07.18.12 03:33:18] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_ContentAssemblerRefApp.thesaurus.xml’.

[07.18.12 03:33:18] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_ContentAssemblerRefApp.merch_rule_group_default.xml’.

[07.18.12 03:33:19] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_ContentAssemblerRefApp.merch_rule_group_default_redirects.xml’.

[07.18.12 03:33:19] INFO: [ITLHost] Starting shell utility ‘move_-_to_processing’.

[07.18.12 03:33:20] INFO: [ITLHost] Starting copy utility ‘fetch_config_to_input_for_forge_Forge’.

[07.18.12 03:33:20] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_Forge’.

[07.18.12 03:33:22] INFO: [ITLHost] Starting component ‘Forge’.

[07.18.12 03:33:31] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_Dgidx’.

[07.18.12 03:33:32] INFO: [ITLHost] Starting component ‘Dgidx’.

[07.18.12 03:33:57] INFO: [MDEXHost] Starting copy utility ‘copy_index_to_host_MDEXHost_Dgraph1′.

[07.18.12 03:33:59] INFO: Applying index to dgraphs in restart group ‘A’.

[07.18.12 03:33:59] INFO: [MDEXHost] Starting shell utility ‘mkpath_dgraph-input-new’.

[07.18.12 03:34:00] INFO: [MDEXHost] Starting copy utility ‘copy_index_to_temp_new_dgraph_input_dir_for_Dgraph1′.

[07.18.12 03:34:01] INFO: [MDEXHost] Starting shell utility ‘move_dgraph-input_to_dgraph-input-old’.

[07.18.12 03:34:02] INFO: [MDEXHost] Starting shell utility ‘move_dgraph-input-new_to_dgraph-input’.

[07.18.12 03:34:06] INFO: [MDEXHost] Starting backup utility ‘backup_log_dir_for_component_Dgraph1′.

[07.18.12 03:34:07] INFO: [MDEXHost] Starting component ‘Dgraph1′.

[07.18.12 03:34:21] INFO: [MDEXHost] Starting shell utility ‘rmdir_dgraph-input-old’.

[07.18.12 03:34:22] INFO: [ITLHost] Starting copy utility ‘fetch_post_forge_dimensions_to_ws_temp_dir_-d03-endeca-apps-ContentAssemblerRefApp-data-web-studio-temp’.

[07.18.12 03:34:23] INFO: Uploading post-Forge Dimensions to Web Studio.

[07.18.12 03:34:24] INFO: [ITLHost] Starting shell utility ‘emgr_update_set_post_forge_dims’.

[07.18.12 03:34:27] INFO: [ITLHost] Starting backup utility ‘backup_state_dir_for_component_Forge’.

[07.18.12 03:34:28] INFO: [ITLHost] Starting backup utility ‘backup_index_Dgidx’.

[07.18.12 03:34:29] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_LogServer’.

[07.18.12 03:34:30] INFO: [ITLHost] Starting component ‘LogServer’.

[07.18.12 03:34:31] INFO: Released lock ‘update_lock’.

[07.18.12 03:34:31] INFO: Baseline update script finished

Uploading templates to the Experience Manager

The sample application provides a set of example templates. We must upload these to Experience Manager using the emgr_update utility.

To upload the sample templates:

Run emgr_update with the –action of set_templates and the following parameters:

Parameter Value

–host The machine name and port for the staging Oracle Endeca Workbench environment,

in the format host:port (atg.ibizsoft.com:5006)

–app_name The name of the application to which you want the templates to apply.

(ContentAssemblerRefApp)

–dir The path to the local directory where your templates are stored. The sample

templates are located in the /config/page_builder_templates directory of

the application.

(/d03/endeca/apps/ContentAssemblerRefApp/config/page_builder_templates)

1. Naviate to the /bin directory of the Platform Services Installation.

$cd /d03/endeca/PlatformServices/6.1.3/bin

2. Run the emgr_update script.

$ ./emgr_update –action set_templates –host atg.ibizsoft.com:5006 –app_name ContentAssemblerRefApp –dir /d03/endeca/apps/ContentAssemblerRefApp/config/page_builder_templates

After update verify the webstudio.log in /d03/endeca/XMGR/endeca/Workbench/workspace/logs/, for Successful update.( : $ENDECA_TOOLS_CONF/logs/webstudio.log)

2012-07-18 03:29:33,494 INFO com.endeca.manager.core.Instance:34 – Creating instance ContentAssemblerRefApp

2012-07-18 03:29:37,576 INFO com.endeca.manager.core.ResourcesManager:227 – Sucessfully set resources for instance ‘ContentAssemblerRefApp’, 43 modified.

2012-07-18 03:34:25,108 INFO com.endeca.manager.core.ResourcesManager:227 – Sucessfully set resources for instance ‘ContentAssemblerRefApp’, 1 modified.

2012-07-18 03:41:38,901 INFO com.endeca.manager.core.ResourcesManager:227 – Sucessfully set resources for instance ‘ContentAssemblerRefApp’, 15 modified.

Verify that the application is provisioned correctly with all Endeca components

Confirm that the templates are available in Experience Manager.

1. Log in to Workbench.

Go to http://atg.ibizsoft.com:5006

The default Username is ******* and the default Password is *****.

http://atg.ibizsoft.com:5006

2. Select Experience Manager from the menu.The List View displays.

3. Click New Landing Page.The Edit View displays.

4. Click Select Template.If the ThreeColumnNavigationPage template is available, your template upload was successful

If templates do not display in Experience Manager after uploading them using emgr_update, check

the Workbench log for possible causes:

$ENDECA_TOOLS_CONF/logs/webstudio.log

(/d03/endeca/XMGR/endeca/Workbench/workspace/logs)

Confirm that the Endeca Components (DGraphs, LogServer, etc,.) are running correctly.

1. Launch EAC Admin Console

Configuring template thumbnail images in Experience Manager

Thumbnail images must be hosted on a Web server in order to display.

We must edit the thumbnails.xml file to contain the absolute path to the thumbnail images included with the Content Assembler reference application.

To configure thumbnails:

1. Stop the Endeca Tools Service.

$ $ENDECA_TOOLS_ROOT/server/bin/shutdown.sh

2. Navigate to the directory where the thumbnails.xml file is located in your Content Assembler

API installation (/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference)

$ cd /d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/

3. Edit the thumbnails.xml file so that the docBase points to the reference/thumbnails

subdirectory of your Content Assembler API directory (/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/thumbnails)

$ vi thumbnails.xml

<Context

path=”/thumbnails”

docBase=”/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/thumbnails”

debug=”0″

privileged=”false”

4. Copy the thumbnails.xml file to $ENDECA_TOOLS_CONF/conf/Standalone/localhost

$ cp thumbnails.xml /d03/endeca/XMGR/endeca/Workbench/workspace/conf/Standalone/localhost/

5. Start the Endeca Tools Service.

$ $ENDECA_TOOLS_ROOT/server/bin/startup.sh

Deploying the Content Assembler reference application for Java

Configure the Endeca Tools Service for the Content Assembler reference application using the sample context file included in the Content Assembler API installation.

To deploy the Content Assembler reference application for Java:

1. Stop the Endeca Tools Service.

$ $ENDECA_TOOLS_ROOT/server/bin/shutdown.sh

2. Navigate to the reference subdirectory of your Content Assembler API directory.

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference.

$ cd /d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/

3. Edit the ContentAssemblerRefApp.xml file so that the docBase points to the

ContentAssemblerRefApp subdirectory of your Content Assembler API directory.

/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/ContentAssemblerRefApp

$ vi ContentAssemblerRefApp.xml

<Context

path=”/ContentAssemblerRefApp”

docBase=”/d03/endeca/ContentAssemblerAPIs/Java/2.1.2/reference/ContentAssemblerRefApp”

debug=”0″

privileged=”false”

4. Copy the ContentAssemblerRefApp.xml file to

$ENDECA_TOOLS_CONF/conf/Standalone/localhost directory.

$ cp ContentAssemblerRefApp.xml $ENDECA_TOOLS_CONF/conf/Standalone/localhost

5. Start the Endeca Tools Service.

$ $ENDECA_TOOLS_ROOT/server/bin/startup.sh

Verify the Deployment of the Reference Application:

Navigate to your Content Assembler reference application to verify the deployment:

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp

:supposed to work.

Note: did not work at this point of time

Making the Content Assembler reference application your preview application

The preview application in Experience Manager allows content administrators to verify the behavior

of the pages they create.

Before content administrators create pages in Experience Manager, you should replace the default preview application with one that can render pages appropriately based on the templates you have

created.You should update the preview application periodically as you begin to customize cartridges.To make the Content Assembler reference application your Workbench preview application:

1. Log in to Workbench as an administrative user.

http://atg.ibizsoft.com:5006

admin/admin

2. Navigate to Application Settings > Preview App settings.

3. Edit the default URL Mappings as indicated below to point to your Content Assembler referenceapplication. The Experience Manager does not make use of the Record URL, so you can leave the default value.

For the Content Assembler reference application for Java, specify the following:

Search URL

http://host:8006/ContentAssemblerRefApp/controller?N=0&Ntk=${key}&Ntt=${terms}&Nty=1&D=${terms}&Ntx=mode+matchallpartial&Dx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

Navigation URL

http://host:8006/ContentAssemblerRefApp/controller?N=${nav}&Nmpt=${previewtime}&Nmrf=${rulefilter}

Search and Navigation URL

http://host:8006/ContentAssemblerRefApp/controller?N=${nav}&Ntk=${key}&Ntt=${terms}&Nty=1&D=${terms}&Ntx=mode+matchallpartial&Dx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

FROM (Existing Values) Bkp:

ttp://atg.ibizsoft.com:5006/endeca_jspref/controller.jsp?eneHost=atg.ibizsoft.com&enePort=25000&N=0&Ntk=${key}&Ntt=${terms}&Nty=1&D=${terms}&Ntx=mode+matchall&Dx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

http://atg.ibizsoft.com:5006/endeca_jspref/controller.jsp?eneHost=atg.ibizsoft.com&enePort=25000&N=${nav}&Nmpt=${previewtime}&Nmrf=${rulefilter}

http://atg.ibizsoft.com:5006/endeca_jspref/controller.jsp?eneHost=atg.ibizsoft.com&enePort=25000&N=${nav}&Ntk=${key}&Ntt=${terms}&Ntx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

http://atg.ibizsoft.com:5006/endeca_jspref/controller.jsp?eneHost=atg.ibizsoft.com&enePort=25000&R=${record}

TO (Updated Values) to:

Search URL :

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp/controller?N=0&Ntk=${key}&Ntt=${terms}&Nty=1&D=${terms}&Ntx=mode+matchallpartial&Dx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

Navigation URL:

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp/controller?N=${nav}&Nmpt=${previewtime}&Nmrf=${rulefilter}

Search and Navigation URL:

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp/controller?N=${nav}&Ntk=${key}&Ntt=${terms}&Nty=1&D=${terms}&Ntx=mode+matchallpartial&Dx=mode+matchall&Nmpt=${previewtime}&Nmrf=${rulefilter}

Record URL (lesft as such)

http://atg.ibizsoft.com:5006/endeca_jspref/controller.jsp?eneHost=atg.ibizsoft.com&enePort=25000&R=${record}

4. Click OK.

5. Verify Content Assembler Preview Application

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp

:supposed to work.Note: did not work at this point of time

ERROR: com.endeca.navigation.ENEException: Navigation Engine not able to process request http://atg.ibizsoft.com:25000/graph?node=0&allgroups=1&offset=0&nbins=10&dym=1&irversion=614

ERROR Scenario:

This error usually occurs when the front-end application is using a pre-6.2.x version of the Oracle Endeca Presentation API to send queries to the MDEX Engine (dgraph). By default, the 6.2 MDEX Engine will only accept queries sent using the 6.2.x version of the Presentation API.

But in our case, we are getting the error even though we are using Endeca Presentation API 6.2.2 and even after copying the required jar files from the PresentationAPI into the front-end application’s WEB-INF/lib sub-directory on the web application server (to avoid Navigation Errors in Workbench)

So, according to Metalink Doc ID 1399513.1, we opted to allow the dgraph to accept queries sent using older Presentation API versions by specifying the –back_compat flag in your MDEX Engine 6.2 dgraph flags.

Enable –back_compat flag in dgraph options

To use the –back_compat flag, find the irversion value used by your current queries (e.g., 601,614) and add the flag with this value in your dgraph command-line arguments. The new setting will take effect the next time the dgraph is restarted.

For the example above, adding this flag and value…

–back_compat 601

…and then restarting the dgraph should resolve the ENEException issue in the above example.

If using the Deployment Template framework, add the –back_compat flag and its value as two separate <arg> elements (in order) within the <args> element for the <dgraph-defaults> component in the application’s config/script/AppConfig.xml file, along these lines:

<args>

[...]

<arg>–back_compat</arg>

</args>

? $ vi apps/ContentAssemblerRefApp/config/script/AppConfig.xml

<arg>–back_compat</arg>

</dgraph-defaults>

<args>

<arg>–back_compat</arg>

</args>

Optionally edited these files also.

ContentAssemblerAPIs/Java/2.1.2/reference/pagebuilder_wine_app/script/AppConfig.xml

Endeca/Solutions/deploymentTemplate-3.2.2/data/eac-java/dgraph/config/script/AppConfig.xml

Again, this change should take effect when the dgraph component is next restarted. You can also use the runcommand.sh (UNIX) or runcommand.bat (Windows) utility from the application’s control sub-directory to propagate the configuration change immediately (entailing an immediate restart in baseline-update order for all affected dgraphs) as follows…

./runcommand.sh –update-definition

This should prevent the error.

? $ cd /d03/endeca/apps/ContentAssemblerRefApp/control/

$ ./runcommand.sh –update-definition

[07.18.12 07:35:34] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 07:35:35] INFO: Updating definitions for dgraphs in restart group ‘A’.

[07.18.12 07:35:35] INFO: Stopping component ‘Dgraph1′.

[07.18.12 07:35:35] INFO: Updating definition for component ‘Dgraph1′.

[07.18.12 07:35:36] INFO: [MDEXHost] Starting component ‘Dgraph1′.

[07.18.12 07:35:42] INFO: Definition updated.

? Restart all Endeca services

Verify Content Assembler Preview Application

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp

à now this works

vi ./ContentAssemblerAPIs/Java/2.1.2/reference/ContentAssemblerRefApp/WEB-INF/web.xml

Working with the Experience Manager

Once you have completed setup of the sample application, you can log in to the Experience Manager,make edits to a landing page, and see the changes in the reference application.

Before proceeding ensure that you have run a baseline update, uploaded the sample templates to

Experience Manager, and deployed the Content Assembler reference application.

To validate the sample project:

1. Navigate to http://atg.ibizsoft.com:5006/ContentAssemblerRefApp

2. Using the navigation menu on the left, navigate to Wine Type > Red.

Notice the site banner image and the promotions in the right column.

3. Log in to the Workbench.

Open a second Web browser window and navigate to http://atg.ibizsoft.com:5006/

Enter the default Username ****** and Password ******. Click Log in.

4. Select Experience Manager from the menu. The List View displays.

5. Select Red Wine Landing Page from the landing pages list.The Edit View displays.

6. From the Content Tree on the left, expand the Header section and choose Site Banner.

7. From the Content Detail Panel on the right, edit the Image name to read /images/WineDemoImages/site-banner-bottles.jpg.

8. From the Content Tree on the left, expand the RightColumn section.

9. Reorder the list by dragging Customer Favorites to the bottom of the list and Wine Club to the top.

10. Click OK.You are returned to the List View.

11. Click Save All Changes.The Status dialog box displays.

12. Click OK.

13. Switch to the Web browser window with your Content Assembler reference application. Refresh this window to view your changes.

The banner image of wine barrels is replaced by a row of bottles, and the order of items in the right column has changed.

14. Click the Wine Store logo to return to the home page.

Note that the change to the site banner applies only to the red wine page.

Basic Scripts, Commands and URLs:

Setting Up The Environment

$ su – endeca

$ source /d03/endeca/MDEX/6.2.2/mdex_setup_sh.ini

$ source /d03/endeca/PlatformServices/workspace/setup/installer_sh.ini

$ source /d03/endeca/XMGR/endeca/Workbench/workspace/setup/installer_sh.ini

Start/Stop the Endeca HTTP Service

To start/stop the Endeca HTTP Service, change to the $ENDECA_ROOT/tools/server/bin directory and run the startup.sh / shutdown.sh

• To start the Endeca HTTP Service:

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/startup.sh

• To stop the Endeca HTTP Service:

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/shutdown.sh

##################

$ cd /d03/endeca/PlatformServices/6.1.3/tools/server/bin

$ ./startup.sh

Using ENDECA_ROOT: /d03/endeca/PlatformServices/6.1.3

Using ENDECA_CONF: /d03/endeca/PlatformServices/workspace

Using CATALINA_BASE: /d03/endeca/PlatformServices/workspace

Using CATALINA_HOME: /d03/endeca/PlatformServices/6.1.3/tools/server

Using CATALINA_TMPDIR: /d03/endeca/PlatformServices/workspace/temp

Using JRE_HOME: /d03/endeca/PlatformServices/6.1.3/j2sdk

Using CLASSPATH: /d03/endeca/PlatformServices/6.1.3/tools/server/bin/bootstrap.jar

##################

Start/Stop the Endeca Tools Service (Workbench)

To start/stop the endeca Tools Service, navigate to $ENDECA_TOOLS_ROOT/server/bin directory and run the startup.sh /shutdown.sh

• Start the Endeca Tools Service with the following command:

$ $ENDECA_TOOLS_ROOT/server/bin/startup.sh

• Stop the Endeca Tools Service with the following command:

$ $ENDECA_TOOLS_ROOT/server/bin/shutdown.sh

##################

cd $ENDECA_TOOLS_ROOT/server/bin/

$ ./startup.sh

Using ENDECA_TOOLS_ROOT: /d03/endeca/XMGR/endeca/Workbench/2.1.2

Using ENDECA_TOOLS_CONF: /d03/endeca/XMGR/endeca/Workbench/workspace

Using CATALINA_BASE: /d03/endeca/XMGR/endeca/Workbench/workspace

Using CATALINA_HOME: /d03/endeca/XMGR/endeca/Workbench/2.1.2/server

Using CATALINA_TMPDIR: /d03/endeca/XMGR/endeca/Workbench/workspace/temp

Using JRE_HOME: /d03/endeca/XMGR/endeca/Workbench/2.1.2/j2sdk

##################

Verify the XMGR Workbench installation http://atg.ibizsoft.com:5006

Start/Stop the CAS Service

To Start / Stop the CAS Service, navigate to /d03/endeca/CAS/3.0.2/bin and run the scripts

cas-service.sh / cas-service-shutdown.sh

• To start the CAS Service

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service.sh &

• To stop the CAS Service

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service-shutdown.sh &

Bouncing the Endeca Server (All Application Services)

Restart all:

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service-shutdown.sh &

$ $ENDECA_TOOLS_ROOT/server/bin/shutdown.sh

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/shutdown.sh

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/startup.sh

$ $ENDECA_TOOLS_ROOT/server/bin/startup.sh

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service.sh &

URL’s

http://atg.ibizsoft.com:5006

http://atg.ibizsoft.com:5006/endeca_jspref

http://atg.ibizsoft.com:5006/ContentAssemblerRefApp

http://atg.ibizsoft.com:6500/cas/?wsdl

Installing Oracle Endeca For Mobile 1.2.2

The Oracle Endeca for Mobile product is packaged as a ZIP archive that includes the following packages:

oracle-endeca-mobile-xmgr-extensions-<version>.zip :

Set of web applications and swf files that make up the Mobile Editors and Cartridges. Installed on the Oracle Endeca Workbench server

endeca-mobile-api-<version>.zip :

Java Web application, packaged as a WAR file. Installed in a Java Web application server

endeca-ios-application-<version>.zip :

iPhone and iPad Universal refapp XCode project, core and Three20 library XCode projects. Installed in a Mac development environment Xcode+iPhone SDK.

endeca-mobile-web-application-<version>.zip :

Set of JSPs/CSS/HTML/images/JavaScript/etc and JAR files for Mobile Web. Installed on top of the endeca-mobile-api

endeca-camerastore-data-<version>.zip :

Sample dataset used by the reference apps. Installed on a server running the MDEX Engine and Platform Services

Supported Devices

While the Oracle Endeca for Mobile product is built to work on a wide variety of devices and expected to work on other devices than those listed below, the following are the devices that are officially supported and tested on:

iPhone/iPad – iOS 4.0 and greater

MobileWeb – iPhone, Android, and BlackBerry (Pearl, Curve, Bold, Storm, Tour, Torch)

Introduction:

Oracle provided a Dataset for the Mobile implementation to be tested called as Camera Store Dataset.

The camerastore dgraph should be installed in an environment with the Endeca MDEX Engine, Platform Services, Workbench, and the Deployment Template. It is shipped as a Deployment Template project.

By default, the Mobile API is configured to work with the Camera Store dataset.

Download and stage the Endeca Mobile Componnets

$ cd /d03

$ unzip V31159-01.zip

$ ls -lrt

total 2413808

-rw-r–r– 1 endeca dba 18722687 Feb 13 2012 endeca-camerastore-data-1.2.2.zip

-rw-r–r– 1 endeca dba 18497266 Feb 13 2012 endeca-ios-application-1.2.2.zip

-rw-r–r– 1 endeca dba 2261503 Feb 13 2012 oracle-endeca-mobile-xmgr-extensions-1.2.2.zip

-rw-r–r– 1 endeca dba 1739277 Feb 13 2012 endeca-mobile-web-application-1.2.2.zip

-rw-r–r– 1 endeca dba 8467071 Feb 13 2012 endeca-mobile-api-1.2.2.zip

$ chmod +x *.zip

Installing the Endeca Camera Store Dataset (Deploy the app)

The endeca Camera Store data set has to be deployed as an endeca app using the deployment template.

This app is used by the endeca mobile application as a reference application.

Make sure that the environment is sourced and all the endeca services are running.

? Unzip endeca-camerastore-data-<version>.zip

$ unzip endeca-camerastore-data-1.2.2.zip

$ cd /d03/endeca/Mobile/1.2.2/camerastore/

control deploy.xml page_builder_templates pipeline script test_data

? Run the Deployment Template “deploy” command from command line from the

endeca/Mobile/1.2.2/camerastore directory, specifying deploy.xml as the app file

$ /d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/bin/deploy.sh –app deploy.xml

——————————————————————————

Found version 6.1 of Platform Services installed in directory

/d03/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.

07/18/2012 07:55:27 [deploy.pl] INFO: Starting deployment template

installation.

——————————————————————————

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

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]:

——————————————————————————

Enter a short name for your application.

Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$

Application name:

camerastore

——————————————————————————

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/camerastore, specify the path as

/localdisk/apps.

Deployment directory:

/d03/endeca/apps

——————————————————————————

Specify the port on which the Oracle 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:

5555

——————————————————————————

Do you want to enable integration with the Oracle Endeca Workbench?

Enable Oracle Endeca Workbench integration? [Y/N]:

——————————————————————————

Specify the port on which the Oracle Endeca Workbench is running. This is

configured in the server.xml file in the Oracle Endeca Workbench workspace

directory. Ports must be in the range 1024-65535 [default: 8006].

Oracle Endeca Workbench port:

5006

07/18/2012 07:56:13 [deploy.pl] INFO: Deploying application into

/d03/endeca/apps/camerastore

07/18/2012 07:56:13 [AppDescriptorReader] INFO: Parsing application descriptor

file deploy.xml.

07/18/2012 07:56:13 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/lib/../conf/dgraph_eac_java_app_descriptor.xml.

——————————————————————————

The Page Builder sample templates refer to image locations within the Mobile

Reference Application. Specify the hostname of the Mobile Reference

Application. [Default: localhost]

atg.ibizsoft.com

——————————————————————————

Specify the port of the Mobile Reference Application [Default: 8006]

5066

——————————————————————————

What port should be used for Dgraph1? [Default: 15000]

23000

——————————————————————————

What port should be used for Dgraph2? [Default: 15001]

23001

——————————————————————————

What port should be used for LogServer? [Default: 15010]

23010

07/18/2012 07:58:28 [AppDescriptorReader] INFO: Parsing application descriptor

file

/d03/endeca/Endeca/Solutions/deploymentTemplate-3.2.2/lib/../conf/dgraph_eac_java_app_descriptor.xml.

07/18/2012 07:58:28 [deploy.pl] INFO: Processing install with id ‘Dgraph’

07/18/2012 07:58:28 [AppDescriptorReader] INFO: Parsing application descriptor

file deploy.xml.

07/18/2012 07:58:28 [deploy.pl] INFO: Processing install with id

’DefaultTemplateManagerApp’

07/18/2012 07:58:29 [CopyHelper] INFO: No files matched recursive pattern ‘*’

in source dir

/d03/endeca/Mobile/1.2.2/camerastore/page_builder_template_thumbnails.

07/18/2012 07:58:29 [deploy.pl] INFO: Application successfully deployed.

[endeca@atg camerastore]$

Application names,ports,host,dir’s,dgraph ports set for camera store

ü Install base deployment? [Y/N]: Y

ü Application name: camerastore

ü Deployment directory: /d03/endeca/apps

ü EAC port: 5555

ü Enable Oracle Endeca Workbench integration? [Y/N]: Y

ü Oracle Endeca Workbench port: 5006

ü Specify the hostname of the Mobile Reference Application: atg.ibizsoft.com

ü Specify the port of the Mobile Reference Application : 5066

ü What port should be used for Dgraph1: 23000

ü What port should be used for Dgraph2: 23001

ü What port should be used for LogServer:213010

è Check the app directory for the contents created in the camerastore app.

$ cd /d03/endeca/apps/camerastore

config control logs test_data

Initializing the application and loading baseline data and templates:

è Run the Deployment Template scripts by running the following commands:

$ cd /d03/endeca/apps/camerastore/control/

Run ‘initialize_services.sh’

./initialize_services.sh

Removing existing application provisioning…

[07.18.12 08:04:05] INFO: Removing application. Any active components will be forced to stop.

[07.18.12 08:04:05] INFO: Application ‘camerastore’ is not defined.

Setting EAC provisioning and performing initial setup…

[07.18.12 08:04:06] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 08:04:06] INFO: Setting definition for application ‘camerastore’.

[07.18.12 08:04:07] INFO: Setting definition for host ‘ITLHost’.

[07.18.12 08:04:07] INFO: Setting definition for host ‘MDEXHost’.

[07.18.12 08:04:07] INFO: Setting definition for host ‘webstudio’.

[07.18.12 08:04:07] INFO: Setting definition for script ‘BaselineUpdate’.

[07.18.12 08:04:07] INFO: Setting definition for script ‘PartialUpdate’.

[07.18.12 08:04:07] INFO: Setting definition for script ‘ConfigUpdate’.

[07.18.12 08:04:07] INFO: Setting definition for custom component ‘ConfigManager’.

[07.18.12 08:04:08] INFO: Updating provisioning for host ‘ITLHost’.

[07.18.12 08:04:08] INFO: Updating definition for host ‘ITLHost’.

[07.18.12 08:04:08] INFO: [ITLHost] Starting shell utility ‘mkpath_dgraph-config’.

[07.18.12 08:04:09] INFO: [ITLHost] Starting shell utility ‘mkpath_temp’.

[07.18.12 08:04:10] INFO: [ITLHost] Starting shell utility ‘mkpath_complete-index-config’.

[07.18.12 08:04:11] INFO: [ITLHost] Starting shell utility ‘mkpath_config’.

[07.18.12 08:04:12] INFO: Setting definition for component ‘Forge’.

[07.18.12 08:04:12] INFO: [ITLHost] Starting shell utility ‘mkpath_incoming’.

[07.18.12 08:04:13] INFO: Setting definition for component ‘PartialForge’.

[07.18.12 08:04:13] INFO: [ITLHost] Starting shell utility ‘mkpath_incoming’.

[07.18.12 08:04:15] INFO: [ITLHost] Starting shell utility ‘mkpath_cumulative-partials’.

[07.18.12 08:04:16] INFO: Setting definition for component ‘Dgidx’.

[07.18.12 08:04:16] INFO: Setting definition for component ‘Dgraph1′.

[07.18.12 08:04:16] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-dgraph-input’.

[07.18.12 08:04:18] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-cumulative-partials’.

[07.18.12 08:04:19] INFO: [MDEXHost] Starting shell utility ‘mkpath_local-dgraph-config’.

[07.18.12 08:04:19] INFO: Setting definition for component ‘LogServer’.

[07.18.12 08:04:19] INFO: [ITLHost] Starting shell utility ‘mkpath_input’.

[07.18.12 08:04:21] INFO: Setting definition for script ‘DailyReports’.

[07.18.12 08:04:21] INFO: Setting definition for script ‘WeeklyReports’.

[07.18.12 08:04:21] INFO: Setting definition for script ‘DailyHtmlReports’.

[07.18.12 08:04:21] INFO: Setting definition for script ‘WeeklyHtmlReports’.

[07.18.12 08:04:21] INFO: Setting definition for component ‘WeeklyReportGenerator’.

[07.18.12 08:04:22] INFO: Setting definition for component ‘DailyReportGenerator’.

[07.18.12 08:04:22] INFO: Setting definition for component ‘WeeklyHtmlReportGenerator’.

[07.18.12 08:04:22] INFO: Setting definition for component ‘DailyHtmlReportGenerator’.

[07.18.12 08:04:22] INFO: Definition updated.

[07.18.12 08:04:22] INFO: Updating IAP Workbench configuration…

[07.18.12 08:04:22] INFO: Downloading config files from Web Studio.

[07.18.12 08:04:22] INFO: [ITLHost] Starting shell utility ‘emgr_update_get_ws_settings’.

[07.18.12 08:04:24] INFO: Retrieving Dev Studio configuration.

[07.18.12 08:04:24] INFO: [ITLHost] Starting copy utility ‘fetch_dev_studio_config’.

[07.18.12 08:04:25] INFO: Retrieving Web Studio configuration.

[07.18.12 08:04:25] INFO: Uploading config files to Web Studio.

[07.18.12 08:04:25] INFO: [ITLHost] Starting shell utility ‘emgr_update_update_mgr_settings’.

[07.18.12 08:04:27] INFO: Finished updating IAP Workbench.

Finished updating EAC.

Run ‘load_baseline_test_data.sh’

$ ./load_baseline_test_data.sh

Setting flag ‘baseline_data_ready’ in the EAC.

Run ‘baseline_update.sh’

$ ./baseline_update.sh

[07.18.12 08:05:48] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 08:05:48] INFO: Definition has not changed.

[07.18.12 08:05:48] INFO: Starting baseline update script.

[07.18.12 08:05:48] INFO: Acquired lock ‘update_lock’.

[07.18.12 08:05:48] INFO: Downloading config files from Web Studio.

[07.18.12 08:05:48] INFO: [ITLHost] Starting shell utility ‘emgr_update_get_ws_settings’.

[07.18.12 08:05:51] INFO: [ITLHost] Starting shell utility ‘cleanDir_complete-index-config’.

[07.18.12 08:05:52] INFO: Retrieving Dev Studio configuration.

[07.18.12 08:05:52] INFO: [ITLHost] Starting copy utility ‘fetch_dev_studio_config’.

[07.18.12 08:05:52] INFO: Retrieving Web Studio configuration.

[07.18.12 08:05:52] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_camerastore.thesaurus.xml’.

[07.18.12 08:05:52] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_camerastore.merch_rule_group_default_redirects.xml’.

[07.18.12 08:05:52] INFO: [ITLHost] Starting shell utility ‘move_-_to_processing’.

[07.18.12 08:05:54] INFO: [ITLHost] Starting copy utility ‘fetch_config_to_input_for_forge_Forge’.

[07.18.12 08:05:54] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_Forge’.

[07.18.12 08:05:55] INFO: [ITLHost] Starting component ‘Forge’.

[07.18.12 08:06:09] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_Dgidx’.

[07.18.12 08:06:10] INFO: [ITLHost] Starting component ‘Dgidx’.

[07.18.12 08:06:48] INFO: [MDEXHost] Starting copy utility ‘copy_index_to_host_MDEXHost_Dgraph1′.

[07.18.12 08:06:49] INFO: Applying index to dgraphs in restart group ‘A’.

[07.18.12 08:06:49] INFO: [MDEXHost] Starting shell utility ‘mkpath_dgraph-input-new’.

[07.18.12 08:06:50] INFO: [MDEXHost] Starting copy utility ‘copy_index_to_temp_new_dgraph_input_dir_for_Dgraph1′.

[07.18.12 08:06:52] INFO: [MDEXHost] Starting shell utility ‘move_dgraph-input_to_dgraph-input-old’.

[07.18.12 08:06:54] INFO: [MDEXHost] Starting shell utility ‘move_dgraph-input-new_to_dgraph-input’.

[07.18.12 08:06:55] INFO: [MDEXHost] Starting backup utility ‘backup_log_dir_for_component_Dgraph1′.

[07.18.12 08:06:56] INFO: [MDEXHost] Starting component ‘Dgraph1′.

[07.18.12 08:07:02] INFO: [MDEXHost] Starting shell utility ‘rmdir_dgraph-input-old’.

[07.18.12 08:07:04] INFO: [ITLHost] Starting copy utility ‘fetch_post_forge_dimensions_to_ws_temp_dir_-d03-endeca-apps-camerastore-data-web-studio-temp’.

[07.18.12 08:07:04] INFO: Uploading post-Forge Dimensions to Web Studio.

[07.18.12 08:07:04] INFO: [ITLHost] Starting shell utility ‘emgr_update_set_post_forge_dims’.

[07.18.12 08:07:06] INFO: [ITLHost] Starting backup utility ‘backup_state_dir_for_component_Forge’.

[07.18.12 08:07:06] INFO: [ITLHost] Starting backup utility ‘backup_index_Dgidx’.

[07.18.12 08:07:07] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_component_LogServer’.

[07.18.12 08:07:08] INFO: [ITLHost] Starting component ‘LogServer’.

[07.18.12 08:07:11] INFO: Released lock ‘update_lock’.

[07.18.12 08:07:11] INFO: Baseline update script finished.

Run ‘update_web_studio_config.sh’

$ ./update_web_studio_config.sh

[07.18.12 08:07:56] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.

[07.18.12 08:07:57] INFO: Definition has not changed.

[07.18.12 08:07:57] INFO: Downloading config files from Web Studio.

[07.18.12 08:07:57] INFO: [ITLHost] Starting shell utility ‘cleanDir_config’.

[07.18.12 08:07:59] INFO: [ITLHost] Starting shell utility ‘emgr_update_get_ws_settings’.

[07.18.12 08:08:00] INFO: [ITLHost] Starting shell utility ‘cleanDir_complete-index-config’.

[07.18.12 08:08:01] INFO: Retrieving Dev Studio configuration.

[07.18.12 08:08:01] INFO: [ITLHost] Starting copy utility ‘fetch_dev_studio_config’.

[07.18.12 08:08:02] INFO: Retrieving Web Studio configuration.

[07.18.12 08:08:02] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_camerastore.thesaurus.xml’.

[07.18.12 08:08:02] INFO: [ITLHost] Starting copy utility ‘fetch_web_studio_config_file_camerastore.merch_rule_group_default_redirects.xml’.

[07.18.12 08:08:02] INFO: Uploading config files to Web Studio.

[07.18.12 08:08:02] INFO: [ITLHost] Starting shell utility ‘emgr_update_update_mgr_settings’.

Run ‘set_templates.sh’

$ ./set_templates.sh

Removing existing Page Builder templates for camerastore

Setting new Page Builder templates for camerastore

Finished setting templates

Installing the Endeca Mobile API

? 1. Unzip endeca-mobile-api-<version>.zip

$ unzip endeca-mobile-api-1.2.2.zip

$ cd /d03/endeca/Mobile/1.2.2/web/

mobile.war

? 2. Install mobile.war in a Java Application server. You will need to explode (unzip) the WAR file in

order to edit the configuration.

$ unzip mobile.war

$ ls

drwxr-xr-x 3 endeca dba 4096 Feb 13 10:41 META-INF

drwxr-xr-x 7 endeca dba 4096 Feb 13 10:41 WEB-INF

-rw-r–r– 1 endeca dba 7887180 Feb 13 10:41 mobile.war

? 3. Edit /WEB-INF/spring/app-config.xml, and update the host and port in the mdexConfig bean:

$ cd /d03/endeca/Mobile/1.2.2/web/WEB-INF/spring

$ vi app-config.xml

<!– config –>

? Now create the update mobile.war file and place it in the webapps directory of the web

application server (Installing mobile.war in the Java application server)

$ cd /d03/endeca/Mobile/1.2.2/web/

META-INF mobile.war WEB-INF

$mv mobile.war mobile.war_bkp

META-INF mobile.war_bak WEB-INF

$jar –cvf mobile.war META-INF WEB-INF

META-INF mobile.war mobile.war_bak WEB-INF

Copy the updated mobile.war to web application server ( webapps dir of $CATALINA_HOME)

$ cp mobile.war /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps/

$ cd /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps/

casconsole-3.0.2-ssl.war casconsole-3.0.2.war casconsole-infocenter-3.0.2.war

endeca_jspref mobile.war mobile.xml

? Crete a folder mobile with the contents of the mobile.war.

$ cd /d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps/

$unzip mobile.war

casconsole-3.0.2-ssl.war casconsole-3.0.2.war casconsole-infocenter-3.0.2.war endeca_jspref mobile.war WEB-INF META-INF

$mkdir mobile

$cp -R WEB-INF META-INF mobile/

$rm –rf WEB-INF META-INF

? Crete a mobile.xml file with docBase pointing to the mobile directory created and place it under

/d03/XMGR/endeca/Workbench/workspace/conf/Standalone/localhost/ directory.

$ vi mobile.xml

<!– Context configuration file for Mobile –>

<Context

path=”/mobile”

docBase=”/d03/endeca/XMGR/endeca/Workbench/2.1.2/server/webapps/mobile”

debug=”1″

privileged=”false”>

</Context>

$ cp mobile.xml /d03/XMGR/endeca/Workbench/workspace/conf/Standalone/localhost/

4. Replace /WEB-INF/lib/endeca_navigation-6.1.4.jar with the 6.1.0 endeca_navigation.jar

(which you can find in /Endeca/PlatformServices/6.1.0/lib/java/endeca_navigation.jar )

Replace /d03/endeca/Mobile/1.2.2/web/WEB-INF/lib/endeca_navigation-6.1.5.jar with the 6.1.0 endeca_navigation.jar which can be found in /endeca/PlatformServices/6.1.3/lib/java/endeca_navigation.jar

$ cd WEB-INF/lib/

endeca_navigation-6.1.5.jar

$ mv endeca_navigation-6.1.5.jar endeca_navigation-6.1.5.jar.bkp.180712

$ cp /d03/endeca/PlatformServices/6.1.3/lib/java/endeca_navigation.jar .

5. Start/restart the Application server

Restart all services

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service-shutdown.sh &

$ $ENDECA_TOOLS_ROOT/server/bin/shutdown.sh

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/shutdown.sh

$ /d03/endeca/PlatformServices/6.1.3/tools/server/bin/startup.sh

$ $ENDECA_TOOLS_ROOT/server/bin/startup.sh

$ nohup /d03/endeca/CAS/3.0.2/bin/cas-service.sh &

6. If everything is setup correctly, you should be able to access the /mobile/search/api.json URL.

For example: http://[app_server_host]:[port]/mobile/search/api.json This URL should return a

response that looks like this:

ci: {

templateId: “MobileFeaturedPage”

templateType: “PageTemplate”,

name: “Categories”,

props: [

…

]

}

http://atg.ibizsoft.com:5006/mobile/search/api.json

Oracle Endeca Commerce 2.1.2 Installation And Configuration

Leave a Comment Cancel reply

We Support