On the Endeca side, you must specify the hostname and port used to connect to the REST Service (the remainder of the URL after the port is well known and cannot be changed.) The REST Service allows Experience Manager to query the user segment server to retrieve the ATG user segments. You can configure the hostname and port in either of the following ways:
By directly modifying the
atgServices.jsonfile for the Endeca application that needs access to ATG user segment data. With this approach, you are making a one-time change that will have to be repeated if you re-create the Endeca application in the future.By modifying the deployment template used to create your Endeca application to add the necessary hostname and port prompts and then store the responses in the application’s configuration. With this approach, every Endeca application that is created using the modified deployment template will include the proper user segment sharing configuration.
Modifying the Endeca Application Directly
To specify the REST Service hostname and port directly in the Endeca application:
Navigate to the
config/editors_configdirectory of your deployed Endeca application on disk, for example,/usr/local/endeca/Apps/CRS/config/editors_config.Open
atgServices.jsonin a text editor.Set the
profileGroupsConnectionUrlproperty to the JSON response for thegetAllProfileGroupsoperation on the Content Administration server.For example:
{
profileGroupsConnectionUrl:http://<ATG host>:<ATG HTTP port>
/rest/model/atg/userprofiling/ProfileGroupsActor/
getAllProfileGroups?atg-rest-output=json&atg-preview=false
}Note: Oracle recommends specifying the host and HTTP port for the Content Administration server.
Save and close the file.
Navigate to the
controldirectory of your deployed Endeca application on disk, for example,/usr/local/endeca/Apps/CRS/control.Run the
set_editors_configscript, for example:./set_editors_config.sh
Modifying the Deployment Template
To modify the deployment template:
Locate the
deploy.xmlfile you will use to configure your Endeca application.Add two
<token>elements to the<custom-tokens>element with the following configuration:<custom-tokens>
<!-- Other tokens -->
<token name="USER_SEGMENTS_HOST">
<prompt-question>Please enter the hostname of the ATG server to
retrieve the user segments. This usually is the CA/Merch server.
[Default:localhost]</prompt-question>
<install-config-option>userSegmentsHost</install-config-option>
<default-value>localhost</default-value>
</token>
<token name="USER_SEGMENTS_PORT">
<prompt-question>Please enter the port number of the ATG server to
retrieve the user segments. This usually is the CA/Merch server.
Typical values are 7003 for WebLogic, 8080 for JBoss and Tomcat, and
9080 for WebSphere.</prompt-question>
<install-config-option>userSegmentsPort</install-config-option>
</token>
</custom-tokens>In the same directory as the
deploy.xmlfile, add an/editors_config/atgServices.jsonfile with the following content:{
profileGroupsConnectionUrl=
http://@@USER_SEGMENTS_HOST@@:@@USER_SEGMENTS_PORT@@/
rest/model/atg/userprofiling/ProfileGroupsActor/getAllProfileGroups?
atg-rest-output=json&atg-preview=false
}Save and close the file.
