For the EAC application, you must specify the hostname and port of the URL that is used to connect to the REST Service (the remainder of the URL after the port is well known and cannot be changed). You can create this configuration in either of the following ways:
By directly modifying the
atgServices.jsonfile for the EAC application that needs access to Business Control Center user segment data. With this approach, you are making a one-time change that will have to be repeated if you re-create the EAC application in the future.By modifying the deployment template used to create your EAC application to add the necessary hostname and port prompts and then store the responses in the application’s configuration. With this approach, every EAC application that is created using the modified deployment template will include the proper user segment sharing configuration.
Modifying the EAC Application Directly
To specify the REST Service hostname and port directly in the EAC application:
Navigate to the
config/ifcr/configuration/tools/xmgrdirectory of your deployed EAC application on disk, for example,/usr/local/endeca/Apps/CRS/config/ifcr/configuration/tools/xmgr.Open
atgServices.jsonin a text editor.Set the
profileGroupsConnectionUrlproperty to the JSON response for thegetAllProfileGroupsoperation on the Content Administration server.For example:
{
profileGroupsConnectionUrl:"http://<Content Administration
host>:<Content Administration server HTTP port>
/rest/model/atg/userprofiling/ProfileGroupsActor/
getAllProfileGroups?atg-rest-output=json&atg-preview=false"
}Save and close the file.
Navigate to the
controldirectory of your deployed EAC 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 EAC 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>Enter the hostname of user segment server.
This server will respond to user segment requests from the
Workbench. [Default:localhost]</prompt-question>
<install-config-option>userSegmentsHost</install-config-option>
<default-value>localhost</default-value>
</token>
<token name="USER_SEGMENTS_PORT">
<prompt-question>Enter the HTTP port of the user segment server.
This server will respond to user segment requests from the
Workbench.</prompt-question>
<install-config-option>userSegmentsPort</install-config-option>
</token>
</custom-tokens>In the same directory as the
deploy.xmlfile, add an/ifcr/configuration/tools/xmgr/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.
