...
- Open Windows Explorer and navigate to the SynergeticCommunityPortal/Bin directory on your server.
- Double click the Synergetic.Application.SynCommPortalCreateConfig.exe.
The Create SynergeticCommunityPortal Config File window is displayed. - Change the database credentials to match the new database.
- Change the Directory field to the name of the new configuration file. For example, SynCommPortalTEST.xml.
- Click Create File.
The new configuration file is created.
Note: To access the new configuration, append ?cfg= to the Community Portal URL, followed by the configuration filename without the .xml extension. For example, http://PortalServer.Name.com.au/login.aspx?cfg=SynCommPortalTEST.
...
- Install a second instance of the Community Portal. For example, to SynergeticCommunityPortal2.
Note: Do not change the authentication settings at this point, as they are still being used for your original Community Portal installation. - Open Windows Explorer and navigate to the SynergeticCommunityPortal2/Bin directory on your server.
- Double click the Synergetic.Application.SynCommPortalCreateConfig.exe.
The Create SynergeticCommunityPortal Config File window is displayed. - Change the database credentials to match the new database.
- Change the Directory field to the name of the new configuration file. For example, SynCommPortal2.xml.
- Click Create File.
The new configuration file is created. - Navigate to Site\Config in the SynergeticCommunityPortal2 directory.
- Copy UserExample.config.
- Rename the copy to User.config.
- Open User.config with Notepad.
- Rename the value of the SynCommPortalConfigFileName to the configuration file you created in step 6.
Note: Inform Synergetic Management Systems you have installed additional Community Portal instances so they include all of your portals when they perform upgrades.
...
- Select Module > System > Configuration File Maintenance in the Synergetic main menu.
- Find the CommunityPortal:Reports:Connection:UseADOFlag configuration setting.
Tip: Search for UseADOFlag to find this configuration setting quickly. - Select the Value field to set the configuration setting to True.
- Test each report you want to use on the web server.
- If errors occur for a report, find the UseDSNProperties datasource property in the report.
- Set either the:
• Main report UseDSNProperties property to True and the SubReport UseDSNProperties property to False
• Main report UseDSNProperties property to False and the SubReport UseDSNProperties property to True. - Repeat steps 4 through 6 for each report.