x Want to participate? Join the group to interact
  • Replies 3 replies
  • Subscribers 133 subscribers
  • Views 1211 views
  • Users 0 members are here
Browse Forums
Announcements
271
topics
260
replies
Databases and Operating Systems
765
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
852
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
877
topics
3k
replies
Sage CRM for Sage 300
183
topics
415
replies
murni

Installing web screen on another server

Posted By

Hi all,

I have 3 servers:

A - 1 DB  Server

B - 1 Sage 300 Application server (using Sage 300 2021)

C - 1 Sage 300 web screen server (using Sage 300 2021)

Installing A and B is okay. I have a bit of problem installing C. I am following guide from https://help.sage300.com/en-us/2021/web/Content/Installation/InstallingWebScreens.htm

There is no mention of where the installation folder & shared data paths supposed to point. is it the installation folder & shared data folder from server B, or the installation folder & shared data folder of server C?

Thank you.

Parents

  • When installing Webscreens on Server C, the Programs should be installed locally - so set the path to a local drive on Server C e.g. C:\*, and the SharedData directory should be set to the SharedData path that you configured on Server B (there should be only one SharedData path).

    If you are using Global Search, Sage recommends pointing the Global Search service on Server C to the Global Search service on Server B (so that you don't have multiple instances of Global Search hitting your database) - see the attachment here for further information (apply step 6 on Server C).

Reply

  • When installing Webscreens on Server C, the Programs should be installed locally - so set the path to a local drive on Server C e.g. C:\*, and the SharedData directory should be set to the SharedData path that you configured on Server B (there should be only one SharedData path).

    If you are using Global Search, Sage recommends pointing the Global Search service on Server C to the Global Search service on Server B (so that you don't have multiple instances of Global Search hitting your database) - see the attachment here for further information (apply step 6 on Server C).

Children

*Community Hub is the new name for Sage City