You can use an external file repository server to keep your documents more secure and reliable.
Figure: Store files in external repository
As shown in the above figure, you may edit ${BURGEONSOFT_HOME}/deploy/resourcemanager.sar/service.xml, find attribute RESOURCE_REPOSITORY, and redirect its value to a network drive.
In Windows system, you can use network drive mapping to map a shared folder on an external file server to a DocCare2 server’s local drive and give DocCare2 server the right to write file to this folder.
For example: you may map \\myfileserver\repository to z: on the DocCare2 server.
In Unix/Linux system, you can use NFS to allow DocCare2 server to read/write file to an external file server.
You can also redirect the value of attribute BACKUP_DIR to a network drive. Thus, the backup archives will be store in it.
If you already have a Tomcat Server and do not want to setup another one, DocCare2 allows you to use the existing Tomcat Server instead of using the embedded Tomcat. This allows you to separate DocCare2 server and web server.
Figure: Standalone Tomcat Server
You should download ‘lite’ and ‘web’ package from Burgeonsoft site. DocCare2 Lite package does not contain web module and JSP/Servlet Engine. DocCare2 Web package contains web module only and you can deploy it in the existing JSP/Servlet Engine.
The steps to install DocCare2 Lite are same as Full package.
Then you can add DocCare2 web module to the JSP/Servlet Container. If you are using Tomcat, you can simply create a directory under ${CATALINA_HOME}/webapps. Then extract DocCare2 web module to this directory. Or you can create a Tomcat Context and extract DocCare2 web module to the context’s docBase directory.
Before you start Tomcat server, you should modify ${WEB_MODULE_DIR}/WEB-INF/conf/application-config.properties. ${WEB_MODULE_DIR} refers to the directory in which DocCare2 web module is deployed.
There are some parameters need to be set correctly.
| RESOURCE_REPOSITORY | Absolute path of the directory used to store DocCare2 documents. The value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| TEMP_RESOURCE_REPOSITORY | Absolute path of the directory used to store temporary user uploaded files. The value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| BACKUP_DIR | Absolute path of the directory used to store all backup archives. The value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| UPLOAD_DIR | This defines the root directory a user can access when he is importing batch documents from remote file system. The value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| USER_LOG_DIR | The value defines the location to store user action log. This value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| INTERNAL_JSP_CONTAINER | Set the value to true if DocCare2 uses embedded JSP Container (Apache Tomcat) |
| DEFAULT_CHARSET | Default character set encoding. The value should be the same as what defines in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml |
| burgeon.jndi.port burgeon.jndi.host |
JNDI hostname and port. The value should be the same as what defines in ${BURGEON_HOME}/conf/jndi.properties |
grant codeBase "file:absolute_path_of_web_module/-" {
permission java.security.AllPermission;
};
|
If your Tomcat is working with Apache via mod_jk, the steps to deploy DocCare2 are similar as to deploy on a standalone Tomcat server. One thing to notice is that you need to move all the files under ${WEB_MODULE_DIR}/WEB-INF/lib to ${CATALINA_HOME}/shared/lib. Or you may come up with class loading problems.
You also need to append the following paragraph to ${WEB_MODULE_DIR}/WEB-INF/conf/client.policy.
grant codeBase "file:${CATALINA_HOME}/shared/lib/-" {
permission java.security.AllPermission;
};
|
