Configure the Database Server

Controller/Worker vs Master/Slave: EnterWorks software prior to version 10.1.x used the terms "master" and "slave" rather than "controller" and "worker" in process and folder names. Folders and processes in newer versions of EnterWorks use the terms "controller" and "worker". If you are installing or patching an older version of EnterWorks, you may need to adapt the filepaths and process names accordingly. For instance, if this documentation refers to:

<drive>:\Enterworks\EnableServer\jbossController\standalone\configuration\conf\sharedConfig.properties

you may need to use the filepath:

<drive>:\Enterworks\EnableServer\jbossMaster\standalone\configuration\conf\sharedConfig.properties

Wildfly vs Jboss: Additionally, Red Hat has changed the name of their JBoss platform to Wildfly. Depending on the version of EnterWorks you are running, the names of some folders and processes may appear as either JBoss or Wildfly. If you are installing or patching an older version of EnterWorks, you may need to adapt the filepaths and process names accordingly. For instance, if this documentation refers to:

<drive>:\Enterworks\EnableServer\WildflyController\standalone\configuration\conf\sharedConfig.properties

you may need to use the filepath:

<drive>:\Enterworks\EnableServer\jbossMaster\standalone\configuration\conf\sharedConfig.properties

Microservice names: The names of the microservices have also been updated. The prefix of "enable2020-" has been changed to "enable-". For instance:

enable2020-channel-readiness-service

is now called:

enable-channel-readiness-service

Note: Before installing any 3rd-party or compatible software that is not included with the EnterWorks installation files, check that the version of the application is supported by consulting EnterWorks 10.2 System Requirements.

Configure the database server.

  1. To prepare this server to host the EPIM and EPX databases, install:

    • Microsoft SQL Server: Install with the Full-Text Search feature.

    • Microsoft SQL Server Management Studio (SSMS)

    • Microsoft SQL Server Client Tools: These should be installed everywhere SSMS is installed.

  2. In order to use SQL Server Management Studio (SSMS) to configure the EPIM and EPX databases, you must log into SSMS. To do so:

    1. It is assumed that the SQL Server is already installed. Ensure that the version of the SQL Server installed is supported by EnterWorks by consulting EnterWorks 10.2 System Requirements.

    2. Log into the SQL Server as a user with permission to create users and databases.

      1. Open the SQL Server Management Studio.

      2. Enter the server or use the Server name dropdown menu to select the server you wish to connect to.

      3. Enter the User name and Password credentials for an account with administrative privileges.

      4. Click the Connect button. SSMS will open the administration screen for the connected server.

      1. In SSMS, open the Security folder, right-click the Logins folder, and select New Login.

      2. The New Login window will appear. It will display the General page.

      3. Set the Login name to ewsys.

      4. Select SQL Server authentication and enter and confirm the Password.

      5. Make sure the Enforce password policy checkbox is unchecked. This will disable the Enforce password encryption and the User must change password at the next login checkboxes.

      6. Click the OK button.

      7. The ewsys account will appear in the list of logins.

    2. TCP/IP protocol must always be enabled. Named Pipes are not required for single server installations, however, they are required on multi-server installations.

      Depending on an enterprise's security requirements, you may or may not be able to enable TCP/IP protocol and Named Pipes yourself. The enterprise's IT department may need to do it for you.

      The tools available to you to enable TCP/IP protocol and Named Pipes depend on system configuration. The following are the steps to enable them using SQL Server Configuration Manager, however, on your machine that functionality may exist in the Microsoft Server Management Console.

      1. Open SQL Server Network Configuration and select Protocols for MSSQLSERVER.

        Enable TCP/IP and Named Pipes

      2. Right-click the TCP/IP protocol to set it to Enabled.

      3. To enable Named Pipes, right-click the Named Pipes protocol and set it to Enabled.

      4. The new protocols will not be usable until the server is restarted. Either restart the server now or wait until SQL Server Authentication Mode is enabled.

    3. To enable the SQL Server Authentication Mode:

      1. Open and log into SSMS.

      2. Open the server’s properties for editing: Right-click the server’s name and select Properties.

      3. Select the Security page.

      4. Set Server authentication to SQL Server and Windows Authentication and click the OK button.

      5. Restart the SQL Server.

      6. Test the SQL Server authentication:

        1. Log out of SSMS.

        2. Log back into SSMS using the ewsys credentials:

          1. Use the Authentication dropdown to select SQL Server Authentication.

          2. Enter ewsys for both the user name and password, then click the Connect button.

          3. If you were able to log in, you have correctly configured SQL Server Authentication.

  4. Configure EPIM and EPX Databases.