This guide details the steps for configuring the local development environment for Primate EOS, a low-code development platform. The instructions focus on database configuration and initial service startup.

Key Primate EOS Modules

• BPS: Business Process Suite for workflow management.
• Coframe: Handles login authentication and authorization.
• Governor: Provides system management, application management, configuration, logging, and database setup.

Configuration Procedure

Step 1: Extract and Configure Core Files

After extracting the development package to a directory like D:\EOS\Developer\, configure the database connection.

1.1 Configure the Primary Database Connection
Edit the user-config.xml file located at:
D:\EOS\Developer\apache-tomcat-7.0.94\webapps\default\WEB-INF\_srv\config\
Update the database settings within the <group name="default"> section.

<group name="default">
    <configValue key="Database-Type">MySql</configValue>
    <configValue key="Jdbc-Type"/>
    <configValue key="C3p0-DriverClass">com.mysql.cj.jdbc.Driver</configValue>
    <configValue key="C3p0-Url">jdbc:mysql://127.0.0.1:3306/eos?characterEncoding=utf8&useSSL=true&serverTimezone=Asia/Shanghai</configValue>
    <configValue key="C3p0-UserName">root</configValue>
    <configValue key="C3p0-Password">123456</configValue>
    <configValue key="C3p0-PoolSize">5</configValue>
    <configValue key="C3p0-MaxPoolSize">5</configValue>
    <configValue key="C3p0-MinPoolSize">5</configValue>
    <configValue key="Transaction-Isolation">ISOLATION_DEFAULT</configValue>
    <configValue key="Test-Connect-Sql">SELECT count(*) from EOS_UNIQUE_TABLE</configValue>
    <configValue key="Retry-Connect-Count">-1</configValue>
</group>

1.2 Configure the SSO Server Data Source
Edit the Spring configuration file deployerConfigContext.xml located at:
D:\EOS\Developer\apache-tomcat-7.0.94\webapps\sso-server\WEB-INF\
Ensure the dataSource bean points to the correct MySQL instance.

<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
    <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
    <property name="url" value="jdbc:mysql://127.0.0.1:3306/eos?serverTimezone=Asia/Shanghai"/>
    <property name="username" value="root"/>
    <property name="password" value="123456"/>
</bean>

Step 2: Modify Server Startup Scripts

Before starting the service, edit the server control scripts (startServer.cmd and stopServer.cmd) to set the correct JAVA_HOME path.

set DIRNAME=D:\EOS\Developer
set JAVA_HOME=G:\Java\jdk1.8.0_102
set CATALINA_BASE=%DIRNAME%/apache-tomcat-7.0.94
set EXTERNAL_CONFIG_DIR=%DIRNAME%/apps_config
...

Step 3: Configure Application-Level Settings

After the initial service start, you may encounter database-related errors. Configure the application-level settings file at:
D:\EOS\Developer\apps_config\default\config\user-config.xml
Update the databace password here. The service will automatically encrypt the plain-text password upon successful startup.

<configValue key="C3p0-UserName">root</configValue>
<configValue key="C3p0-Password">{3DES}CdD8k5TQAhonaBtT6K7BNRU=</configValue>
...

Step 4: Initialize the System via Governor

Start the Tomcat service, either via the modified startServer.cmd or direct from the Tomcat bin directory. Ignore initial startup errors. Once running, access the Governor management console through you're browser to initialize the system database.

Default Governor Credentials:
Username: sysadmin
Password: 000000

Proceed with the initialization wizard. Some errors during this process may be non-critical and won't prevent basic functionality.

Step 5: Resolve Logging Configuration

A common error is a missing Log4j configuration file. Resolve this by copying a valid log4j-xxx.xml configuration file to the expected directory as indicated in the error log.