Administration

The StreamShare community is growing bigger and bigger every day. It has been a true pleasure watching it grow from nothing to a vivid place full of peers sharing my interest in this product. With a huge influx of new users, I thought it could be good to write up a set of best practices for the forum for the benefit of both new and experienced users.
I have put these practices together to help all users to maximize their chances of receiving the best possible assistance from the community in a timely manner.

Sometimes it's useful to periodically clean out old files from StreamServe directories. This can be accomplished in many different ways.

One method is outlined in http://streamshare.streamserve .com/Articles/Article/?article Id=332.

Here is another way, using the StreamServe Task Scheduler, and command-line tools.

Before deleting any StreamServe-related files, ensure that they are not in use by any StreamServe processes. To be safe, it may be desirable to shut down any StreamServer instances prior to running any deletion commands.

Real-time antivirus, security suite, disk encryption, backup, and defragmentation agents can cause problems, particularly on high-volume StreamServe servers. During StreamServe runtime, the Communication Server (“StreamServer”) is extremely I/O-intensive, and real-time agents can slow down processing, interfere with write locks, and/or mistakenly identify binary strings (e.g. in PDF, TIFF, JPEG files) as threats.

During the installation of StreamServe components, security agents may interfere with copying necessary program files.

Microsoft Windows includes a built-in firewall to secure network traffic to and from Windows systems. On Windows 7 and 2008 Server systems, the firewall is enabled by default, and will prevent other hosts from accessing network services installed on those systems.

Basic connectivity issues between Control Center and Management Gateway are very common, so the following how-to provides a general overview on opening the Windows Firewall for StreamServe services.

The StreamServe Database Administration Tool (“DB Admin Tool” or “DBAT”) is typically run in an interactive GUI mode, but its Java classes can also be instantiated from a command line. This can be useful to automate the migration of Composition Center and Composer messages from one environment to another; inspect the various StreamServe-related database schemas; prepare a Collector repository for migration; export a document definition file; etc.

For more details, refer to the DB Admin Tool and Control Center user documentation, as well as the Database Guidelines. Before proceeding, download the latest version of the DB Admin Tool from OpenText Knowledge Center.