Software Requirements
Operating System:
You can install these products on the following server operating systems:
- Microsoft Windows 2003 R2 Server.
- Microsoft Windows 2008 Server.
- Microsoft Windows 2008 R2 Server.
- Microsoft Windows 2012 Server.
- Microsoft Windows 2014 Server.
- Microsoft Windows 2016 SP1+ Server.
The recommended operating system is Microsoft Windows Server 2014 (64bit).
For demonstration purposes only, you can install these products on the following workstation operating systems:
- Windows XP Professional 32-bit SP2 or SP3.
- Windows Vista.
- Windows 7 Ultimate, Enterprise or Business Editions.
NOTE: These platforms are not suitable for live deployments.
In all cases, it is recommended that the latest service pack and patches are applied to the server.
Internet Information Server: On the AP tier, Internet Information Server (IIS) version 6.0 or greater must be installed.
MooD: MooD 15 must be installed on both the BIE and AP tiers.
Microsoft .NET Framework: MooD 15, BIE, and AP all require Microsoft .NET Framework 2.0 Service Pack 2. This framework may already be installed, but, if not, it will be installed with the products.
Microsoft XML: MooD 15 requires Microsoft XML v 6.0 SP1. If it is not installed, it will be installed with the products.
SQL Control Types 2008 R2 SP1: required by MooD 15, and will be installed if not already present.
SQL Management Objects 2008 R2 SP1: required by MooD 15, and will be installed if not already present.
SSCERuntime Package: required by MooD 15, and will be installed if not already present.
AJAX extensions for .Net: required by MooD 15 and AP tiers, and will be installed if not already present.
Microsoft Office: On the BIE and AP tiers, Microsoft Excel 2003 or later may be required if your solution uses the Excel import synchronization activator configured to run in Excel Native model.
Business Integration Engine (BIE)
2. Install a Database Engine
2.1 Install Microsoft SQL Server as the Database Tier
Databases can be hosted on SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014 or SQL Server 2014. Express versions can be used for demonstration purposes only, but they are not suitable for live deployment. The recommended option is SQL Server 2014. All SQL Server products require the same installation choices.
2.1.1 Ensure that mixed mode authentication and full text indexing is selected as part of the installation procedure.
2.1.1 Be sure to remember the SA password that you choose.
2.1.2 If the BIE server and SQL Server are on different machines, open a TCP port on the SQL server machine firewall so the BIE can connect to the database. For SQL Server, the default port is 1433.
2.1.3 Configure SQL Server to accept TCP/IP connections;
2.1.3.1 From the Start menu, open SQL Server Configuration Manager.
2.1.3.2 In the right-hand panel, browse to the protocols for your SQL Server instance.
2.1.3.3 In the right-hand panel, right-click TCP/IP.
2.1.3.4 Choose Enable.
2.1.3.5 Stop and start the SQL Server service.
Refer to your Microsoft support team for more assistance.
2.2 Install Oracle as the Database Tier
Databases can be hosted on Oracle 10g and 11g (using the appropriate 32bit driver). Full text indexing must be installed.
Please refer to your Oracle support team for help installing Oracle.
If the BIE server and Oracle are on different machines, open a port so the BIE can connect to the database. For Oracle, the default port is 1521.
3.Install and Licence MooD 15
Perform a custom installation of MooD 15 to not include the installation of SQL Server Express, and ensure it is available to everyone who uses this computer. More details of this procedure can be found in the MooD Release Notes.
Note that the InstallShield wizard will check that certain prerequisites are installed on the machine and install them if necessary. On 64 bit installations, the status of this check will progress through Pending > Installed > Succeeded even if the prerequisites are already installed
Start MooD 15 Repository Manager. On the File tab, click Manage Licence and install a licence file (using a Licence Server is not supported for Active Enterprise Server installations). See the Repository Manager Guide for details.
4. Configure Repository Server and Create or Restore a Repository
Start MooD 15 Repository Manager, add the Database Engine Server and create or restore a repository. See the Repository Manager Guide for details. The next section gives some additional guidance for SQL Server.
In whatever repository you create or restore, it is advisable to locate or create some content to assist with testing the Active Enterprise setup, for example, a Home page for Administrator.
4.1 SQL Server
Key points and guidance:
- We recommend running Repository Manager as Administrator. Right click the MooD 15 icon and select Run as Administrator.
- To create a new database, you must have a connection to the server, and the user credentials used must have administrative privileges on SQL Server. In Repository Manager, when you add a server, on the Add Server dialog box on the Servers tab, make sure Security is set to use Native SQL Authentication.
- Use the Test button on the Add Server dialog box to test the credentials and server name. If the test fails, check the details you have supplied.
- If you supplied SQL Server sysadmin user credentials when you added the server, you can create a repository immediately. If not, you will need to provide sysadmin credentials in the Add Repository dialog box. This will be cached for the duration of the Repository Manager session, but, for subsequent sessions, will revert to the credentials provided when the server was added.
- If you do not have access to a sysadmin user, on the Add Repository dialog box, select the Create SQL script only checkbox and then give the script created to your database administrator (DBA). The DBA can use this script to create the repository for you. The DBA must use sysadmin privileges to ensure that the correct user is assigned the correct role.
- For normal connection to the SQL repository, the SQL login that is used to access the SQL database must only be associated with the RepName_role database role for that database. This role is created by MooD upon database creation. If the database is renamed, this role will also need to be renamed accordingly.
- Once the repository has been created in SQL Server, it should be visible to Repository Manager. On the Server tab, select the server, and then click Find all repositories on the selected server. If SQL authentication as listed above is supplied, the repository will be listed. Set it to Show to make it visible on the Repositories tab.
5. Install the Business Integration Engine (BIE)
5.1.1 Install the Business Integration Engine;
5.1.1.1 Using the MooD Media, navigate to the Business Integration Server/Business Integration Engine folder and run the setup.exe file.
5.1.1.2 Review and accept the licence agreement.
5.1.1.3 Select an installation folder for BIE (the default is recommended), and ensure it is available to everyone who uses the computer.
NOTE:
- If the BIE server and Active Publisher server are on different machines, configure your firewall to open a port so that Active Publisher can connect to the BIE. By default, this is port 50015, and is configurable in the BIE’s config.xml file.
- If the port is changed from the default, it will also need to be changed in Business Architect. In the Explorer Bar, under Libraries, click Web Publishing. Select the Active Publish profile, and then, on the ribbon, click Edit and change the port selected.
6. Cache a Repository in Business Integration Engine (BIE)
6.1.1 It is advisable to validate the repository for publishing (but not required);
6.1.1.1 In MooD Repository Manager, right click the repository, and then click Validate.
6.1.1.2 Provide the repository administrative credentials.
6.1.1.3 Select Check & Fix errors and then click Next (this may take some time).
6.1.1.4 If there are any errors highlighted, contact MooD International support for advice.
6.1.2 It is advisable to defragment all indices (but not required);
6.1.2.1 In MooD Repository Manager, right click the repository, and then click Index Fragmentation.
6.1.2.2 Click Defragment All and then click OK.
6.1.3 Ensure BIE service is started;
6.1.3.1 Navigate to Control Panel > Administrative Tools > Services.
6.1.3.2 Locate and start the service named Business Integration Engine 15.
6.1.3.3 Alternatively, run this command from a command line;
6.1.4 Use the BIE Manager to create a cache of the desired repository;
6.1.4.1 Open the BIE Manager. Use Start > All Programs > MooD 15 >
Business Integration Engine Manager.
6.1.4.2 Ensure the BIE Server and BIE Port number boxes are correct, and then click Connect.
6.1.4.3 Select the required repository and then select Enable support for BIE. Enter the repository administrator username and password, choose a security provider from those installed, select the plug-in(s) you wish to enable for the repository, and then click Apply.
It is possible to install other security providers.
6.1.4.4 The repository status will change to The repository is ready.
Active Publisher
Install Internet Information Server (IIS)
Both IIS and ASP.NET are required by the Active Publisher tier. For further guidance on IIS installation, contact your Microsoft support team.
7.1 Windows Server 2003 and XP Installation
7.1.1 IIS is installed using the Add or Remove Programs dialog in Control Panel. Use the Add or Remove Windows Components tab.
7.1.2 If .NET 2.0 Service Pack 2 has been installed prior to the installation of IIS, you must run the following command to re-register ASP.NET.
7.1.2.1 Open the command prompt dialog. Click Start > Run and in the Run dialog type cmd and then press Enter. This opens the command prompt dialog. (If running on Vista and UAC is turned on then you will need to run cmd as Administrator.)
7.1.2.2
In the command prompt dialog, enter the following commands; (Each line is a single command. Press Enter after each. The exit command closes the command prompt dialog.)
7.2 Windows Vista / Windows 7 Installation
7.2.1 IIS is installed using the Turn Windows Features on or off dialog in Control Panel (in the Programs and Features section).
7.2.2 Select the Internet Information Services item to install IIS with default features enabled. The following additional sub-features must also be enabled:
· Web Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase and IIS 6 configuration compatibility
- World Wide Web Services > Application Development Features
> ASP.NET
7.2.3 For installations utilising integrated authentication, the following is also required:
· World Wide Web Services > Security > Windows Authentication
7.3 Windows Server 2008 Installation
7.3.1 IIS is installed using the Roles section in the Server Manager application.
7.3.2 In the Roles Summary click Add Roles and select the Web Server (IIS)
role.
7.3.3 When prompted, select Role Service. In addition to the defaults, the following must be selected:
· Web Server > Application Development > ASP.NET
- Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility
7.3.4 For installations utilising integrated authentication, the following is also required:
· Web Server > Security > Windows Authentication
8. Install Active Publisher
Follow the steps below to install the first instance of Active Publisher on a server.
8.1 Installation
8.1.1 Using the MooD Media, navigate to the Business Integration Server/Active Publisher folder and run the setup.exe file.
8.1.2 Review and accept the licence agreement.
8.1.3 During the installation you will be prompted to create an application pool in IIS. Allow this. When you configure IIS, you can use this pool, or add additional pools.
8.1.4 Set Site and Virtual Directory appropriately. Virtual Directory is used to build up the web address for Active Publisher. For example, if you are installing on a machine called WebServer and install to a virtual directory called MyRepository, you would access Active Publisher from http://WebServer/MyRepository. Port 80 will be used as the default port for IIS. Configuration of this port is possible using the IIS Management Console.
9. Configure Internet Information Server (IIS)
9.1 Windows XP Configuration
9.1.1 Add the ASPNET user to the Administrators group.
9.1.1.1 Open Computer Management (run compmgmt.msc).
9.1.1.2 Find the ASPNET user (under System Tools > Local Users and Groups > Users).
9.1.1.3 Right-click the ASPNET user and select Properties. On the Member Of tab, add the user to the Administrators group.
9.1.2 Set the ASP.NET version.
9.1.2.1 Open Internet Information Services (IIS) Manager (run inetmgr.exe).
9.1.2.2 Find the Active Publisher virtual directory (under Web Sites >
Default Web Site).
9.1.2.3 Right-click and select Properties. On the ASP.NET tab, ensure that
ASP.NET version 2.0.xxxxx is selected.
9.2 Windows Server 2003 Configuration
9.2.1 If running on the 64-bit edition of Windows Server 2003, switch to the 32-bit version of ASP.NET.
9.2.1.1 Enter the following commands and press Enter (there are two commands (exit is the second));
9.2.2 Enable the ASP.NET extension.
9.2.2.1 Open Internet Information Services (IIS) Manager (run inetmgr.exe).
9.2.2.2 Navigate down to Web Service Extensions, select ASP.NET v2.0.xxxxx from the list, and then click the Allow button.
9.2.3 Create a new application pool. It is good practice to name application pools after the applications they will serve.
Note that the Active Publisher installation allows you to create an application pool during installation. If you did this, and you want to use that pool, you do not have to create a new pool. However, you should check that its settings match those of the one created here.
9.2.3.1 In Internet Information Services (IIS) Manager, navigate to Application Pools and create a new one (right click and select New) using the default settings.
9.2.3.2 Right click on the new application pool and select Properties. On the
Identity tab, select the Local System predefined user.
9.2.4 Assign Active Publisher to the new application pool and set the ASP.NET version.
9.2.4.1 In Internet Information Services (IIS) Manager find the Active Publisher virtual directory (under Web Sites > Default Web Site).
9.2.4.2 Right-click and select Properties.
9.2.4.3 On the Virtual Directory tab, in the Application settings section, select the application pool created in 9.2.3.
9.2.4.4 On the ASP.NET tab, ensure that ASP.NET version 2.0.xxxxx is selected.
9.3 Windows Server 2008, Windows 7 and Windows Vista Configuration
9.3.1 Create a new application pool. It is good practice to name application pools after the applications they will serve.
Note that the Active Publisher installation allows you to create an application pool during installation. If you did this, and you want to use that pool, you do not have to create a new pool. However, you should check that its settings match those of the one created here.
9.3.1.1 Open Internet Information Services (IIS) Manager (run inetmgr.exe).
9.3.1.2 Navigate to Application Pools and create a new one (right click and select Add Application Pool). Ensure that .NET Framework version 2.0.xxxxx is selected.
9.3.1.3 Right click on the new application pool and click Advanced Settings. Under Process Model, set Identity to LocalSystem. If running on a 64-bit edition of Windows, also set Enable 32-bit Application to True.
9.3.2 Assign Active Publisher to the new application pool.
9.3.2.1 In Internet Information Services (IIS) Manager find the Active Publisher virtual directory (under Sites > Default Web Site).
9.3.2.2 Right click the virtual directory and select Manage Application > Advanced Settings. Set the Application Pool to the one created in 9.3.1.
9.3.3 If integrated authentication is to be used, it must be enabled for the virtual directory.
9.3.3.1 In Internet Information Services (IIS) Manager, select the Active Publisher virtual directory (under Sites > Default Web Site).
9.3.3.2 In the right-hand pane, under the IIS heading, select Authentication.
9.3.3.3 Right-click Windows Authentication, and then select Enable.
You will also need to ensure that your repository is configured to use Windows Authentication.
10. Configure Active Publisher
10.1.1 In the folder \Inetpub\wwwroot\<Virtual Directory>\bin, you will find the application ConfigureActivePublisher.exe. Double-click this to run the Active Publisher configuration tool (note that this program modifies the ActivePublisher.config file in the parent folder).
10.1.2 Under Repository, use the Name drop down list to choose the repository that this Active Publisher installation will serve, and set the appropriate administrator name and password for the repository (the MooD logon not the SQL logon).
10.1.3 The remaining settings can be accessed from within Business Architect. In the Explorer Bar, under Libraries, click Web Publishing. Select the Active Publish profile, and then, on the ribbon, click Edit.
10.1.4 Under BIE Server, set the BIE Port and BIE Server settings. If the BIE is installed on the same machine, the default settings (50015 and localhost) should be fine.
10.1.5 Click OK to accept the changes.
10.1.6 Active Publisher should detect the changed configuration and automatically restart. It can be manually restarted by entering iisreset from a command prompt.
You should now be able to view your repository by opening a web browser and navigating to
If you'd like to read more of this guide, please click on the attachment.
Comments
0 comments
Please sign in to leave a comment.