On the
Add Roles window, select all the
Search roles:
Mashup API
Search API
Search Server
Mashup UI
Storage Service
Click
Accept.
Configure the
Search Server role:
For Instance name, enter a unique name such as
ss1.
For API port, enter a port number, for example, baseport +
10.
For UI port, enter a port number, for example, baseport.
Select HTTPS if you need to use SSL for the hosted Mashup
UIs. For more information, see Enable HTTPs for the Mashup UI in the Exalead CloudView Administration
Guide.
Configure the
Search API
role:
For Search server instance, enter the instance name
specified in step 4.
Configure the
Mashup API role:
For Search server instance, enter the instance name
specified in step 4.
For Instance name, enter a unique name such as
ac1.
For Mashup application, enter your application name, if
not using default.
Configure the
Storage Service role:
For Search server instance, enter the instance name
specified in step 4.
For Instance name, enter a unique name such as
sts1.
Configure the
Mashup UI role:
For Search server instance, enter the instance name
specified in step 4.
For Instance name, enter a unique name such as
mu1.
For HTTP context path, enter the path for the application
such as /mashup-ui.
For Storage serviceinstance, enter the instance name specified in step 7.
Before you begin:
While most of the
deployment scenarios covered in this guide use the default search target, the
scenario shown in Recommended Deployment uses a local-only search target. With a local-only search target, the search server only searches indexes that are on the same machine.
In the Administration Console, select Deployment > Build groups > Search Targets.
Delete the default search target,
st0.
Click
Add search target:
For
Name, type
st0.
For
Type, select
Local only.
Click
Accept.
In the settings for this new search target, under
Build groups, select the target build group.