Dyn/admin home page issue in ATG10.2

I encountered below error while trying to open the home page of dyn/admin in ATG10.2.

Unable to execute the command javac -classpath C:\apps\java\jre\lib\resources.jar;C:\apps\java\jre\lib\rt.jar;C:\apps\java\jre\lib\sunrsasign.jar;C:\apps\java\jre\lib\jsse.jar;C:\apps\java\jre\lib\jce.jar;........................................................................................................................./atg/dynamo/servlet/pagecompile/PageCompileServlet The detailed exception is: java.io.IOException: Cannot run program "javac": CreateProcess error=206, The filename or extension is too long.

Follow below steps to resolve this issue.

Add ExtendedJhtmlPageProcessor component at atg\dynamo\servlet\pagecompile\ location and restart the sever.

Steps

1. Navigate to ATG_HOME\localconfig directory.

2. Create atg\dynamo\servlet\pagecompile directory structure there.

3. CreateExtendedJhtmlPageProcessor.properties file with below content in that directory.

     #atg\dynamo\servlet\pagecompile\ExtendedJhtmlPageProcessor.properties

     $class=atg.servlet.pagecompile.jsp11.JSPPageProcessor

     javaCompilerClassName=atg.servlet.pagecompile.SunJavaSourceCompiler

WebLogic Server getting boot identity from the user issue solution

I have just started using WebLogic Server. I tried to start one of the managed server from command line it stucked at. 

getting boot identity from the user

I entered admin username followed by password then it continued.In this way every time you need to enter username/password.

With below small  and easy configuration you can resolve this issue (Avoid authentication prompt).

1. Create boot.properties in $DOMAIN_HOME/servers/[server_name]/security directory.

2. Put content in below format in the file.

      username=[superuser with admin role]

      password=[password of user(admin role)]

3. Alternatively you can copy boot.properties from  $DOMAIN_HOME/servers/AdminServer/security,then alter the file accordingly.

Note : WebLogic only prompts for username/password when running in Production mode it won't prompt for username/password in development mode.

Introduction to Endeca Application Controller (EAC)

The EAC provides the infrastructure to support Endeca application.Endeca Application Controller (EAC) is a control system used to control, manage,and monitor components in Endeca implementation.

There are two types of EAC instances.

1. EAC Central Server
2. EAC Agent

1. EAC Central Server

One instance of the EAC serves as the EAC Central Server.The EAC Central Server also contains a repository that stores provisioning information — such as, data about the hosts, components, applications and scripts.This instance includes and WSDL enabled public interface.Other applications communicates with EAC using this interface.EAC central server works as an controller of EAC agents.EAC central server communicates with EAC agents using internal web service interface.

2. EAC Agents 

EAC instances other then EAC Central server are EAC agents.These EAC agents instruct host machine for execution of actual task such Forging or Indexing.

There are 3 ways to communicate with EAC.

1. Endeca Workbench.
2. The command line utility, eaccmd.
3. Endeca WSDL-enabled interface(using language that supports web services).Endeca workbench and Endeca deployment template utilize this method.

You can use below scripts to start and stop EAC from commandline.
1. EAC start script.
   $ENDECA_ROOT/tools/server/bin/startup.sh
2. EAC stop script.
   $ENDECA_ROOT/tools/server/bin/shutdown.sh
Note : On windows EAC is created,configured and registered as "Endeca HTTP service".

EAC configuration file
EAC reads configuration from eac.properties file.This file is located in the $ENDECA_CONF/conf directory.

EAC log file.

EAC log file is located in the $ENDECA_CONF/logs directory.You can update EAC logging related configuration in the logging.properties file.This file is located under $ENDECA_CONF/conf.