SEP notes (4)
Installation plan (considerations before installation)
(1) What is dB used?
There are two options: built-in Sybase dB and external ms SQL dB (which can be SQL 2000 or SQL 2005)
If the number of users is less than 1000, you can use the built-in Sybase dB. The disadvantage is that the number of clients cannot exceed 1000, and the performance is poor. The more clients, the worse the performance. The advantage is that the installation is extremely simple.
If the number of users is more than 1000, you must use ms SQL dB (which can be installed on the same hardware server or a dedicated SQL Server ). Moreover, if high availability is required, only external ms SQL can be used.
Q: What should we choose?
A: External Database, ms SQL 2000 Cluster
(2) failover Solution
There are several aspects of failover
First, ms SQL itself can build a cluster (redundant on the database server hardware)
Second, you can install two Sep mgmt svr instances to connect to the same ms SQL dB to achieve load balancing and high availability. (Perform redundancy on the SEP Mgmt Server)
Third, you can create two ms SQL databases, establish a replication relationship between the two databases, and synchronize the data of the two databases. (Redundant database data)
Prerequisites for using external ms SQL Server 2000
Prerequisites:
1) mixed mode is required (both Windows Authentication and SQL Server authentication are supported)
2) Install SQL SP4
3) The report function requires that SQL statements are case-insensitive)
4) language requirements: English
5) do not use the default Instance name. Use SEPm or another name (the default name is unnamed and will be confused in the future)
6) The SEP Mgmt Server and the DB server use plain text to transmit the database user name and password. If possible, use a dedicated VLAN for transmission.
In addition:
1) You still need to install the SQL Server Client tool on the SEP Mgmt Server.
2) best practice is used to create a database during Sep MGMT installation, instead of using an existing database.
Install Sep manager with external MS SQL DB
Step 1: Prepare,
(1) Check whether Windows Server 2003 has been installed. All patches are complete.
(2) install IIS 6.0
(3) install the ms SQL Server 2000 client tool (because the BCP tool is called to create a database when Sep manager is installed)
Step 2: Install Sep Manager
* Sep manager is installed by the next to finish buttons;
* After the installation is completed, wait about 15 seconds. The Management Server Configuration Wizard will appear to configure the database.
Step 3: Configure Sep manager and database settings
* Because this is the first installation, you must set the first site and select "install my first site"
* Next, you need to enter some server information. You don't need to change it. Just take a note and record it.
-- Server name: The default value is computer name,
-- Server port: 8443
-- Web Console port: 9090
-- Server data folder: this does not need to be changed.
* Enter the site name.
* Next, enter the encryption password, which is used for encryption when data is transmitted between the client and the server. This password is not required at ordinary times, but is required for disaster recovery.
* Next, select the database type. There are two options: Embedded Sybase Database and ms SQL Server. Select ms SQL Server.
* Enter a series of configuration parameters.
-- Database Server: The format is <SERVER_NAME>/<instance_name>
-- SQL port number: The default value is 1433, which does not need to be changed.
-- Database Name: The default value is sem5, which does not need to be changed.
-- User: database user, which is created when the database is created. The default value is sem5 and does not need to be changed.
-- Password: password of the database user, which must be recorded and stored in a safe place
-- SQL client Folder: If you have installed the ms SQL Server Client tool, you should have entered the path here and do not need to change it. If it is null, your SQL client tool is not installed or is not correctly installed. You need to reinstall it.
-- DBA User: generally SA
-- DBA password: The SA password above. Consult the company DBA
-- Database data folder: Click the default button on the edge to automatically detect the event. (If the above parameters are incorrect and the connection to the database fails to be correctly established, the connection will fail. Check the above configuration, including the database server name, name resolution, and database port, DBA account and password)
* Click Next and enter the SEP Manager Administrator Account (Admin by default) and password.
* Then, the system starts to create and initialize the database. wait a few minutes.
* Finally, you will be asked if you want to start migration and deployment wizard.
Step 4: Distribution Client
If sav or SCS exists, this wizard will help you migrate (we don't want it now); it will also guide you to generate a distributable Client installation package and distribute it to the client. (If NO is selected here, You can manually run/tomcat/bin/clientremote.exe to enable it later)
This step can be performed after various policies are configured, so that the policy has been packaged in the Client installation package that can be distributed.