Avaya Customer Interaction Express 1.0, User Manual

Page: 71 / 344

Installing the server components
Edition: 1.1 03/08/2007 71
<servlet-name>upload</servlet-name>
<url-pattern>/upload</url-pattern>
</servlet-mapping>
<security-constraint>
<web-resource-collection>
<web-resource-name>Update Store Protected Area</web-resource-name>
<url-pattern>/admin/main</url-pattern>
<url-pattern>/admin/upload</url-pattern>
<url-pattern>/admin/updates</url-pattern>
<url-pattern>/admin/delete</url-pattern>
<url-pattern>/admin/newUpdate</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name> tomcat </role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>Update Store Admin</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/loginError.jsp</form-error-page>
</form-login-config>
</login-config>
<security-role>
<role-name> tomcat </role-name>
</security-role>
</web-app>
The entries for <security-role> and <auth-constraint> in particular may need to be changed from tomcat to
another name.
In the updateStore.properties file you must specify the path to an existing folder where you want
UpdateStore to save the setup.
Example:
#Properties for the Avaya Update Store
#location (path) into local file system where the uploaded setups are stored
store.location.path=c:\\updatestore
Note that you must enter special characters like "\," in a path name with "\".
Log files
The AyavaUpdateService and updater write to the client PC's NTEventLog. The updater also writes a log
file (AvayaUpdateService.log) in the installation directory that contains information on the last update.