Skip to main content
Solved

Customizations on multiple servers - Load balancer?

P
Freshman I

We are hosted on Acumatica’s platform, but we have two servers. I’m assuming (for lack of information) that this is a load balancing situation. We have two urls ourname and ourname-process. We are told it shares the same database. We were told we only need to install on the main server, so we install on that server. However, randomly, when we install, it causes issue. After install:

Main server functions as normal.
 

Process server:

  • All pages are white when loaded.
  • It loads the menus, etc.
  • API connections to the server break with a 500 error.
  • We can still login to the process server.

I’m attaching a screenshot and the package that broke the process server. Again, it works fine on our dev server (same version), and it works fine on our live main - just breaks the production.

 

Best answer by andriitkachenko

Hi @pdeatherage 
You can quickly check whether or not both instances are using the same database:

  • Upload your customization at the first instance.
  • Open your second instance and go to the Customizations screen
  • If you can see the customization - yes, they use the same database.

It’s a quite common configuration - for example when a client wants to have an ERP for internal use and a Portal for their clients to inquire about information related to them.

However, one database doesn’t mean they share the logic!

What I mean by that - you uploaded customization to the database. But it’s “dormant”, lying like an archive waiting to be applied.

You need to publish it in both instances. When you publish your customization, pages are copied from the customization package to the instance, database changes are made, the code responsible for handling the screen is injected into the instance, etc.

The database updating engine is smart enough to detect that the customization has been already applied, so don’t worry that the second publish will override schema changes.

View original
1 Attachments
Did this topic help you find an answer to your question?

3 replies

andriitkachenko
Jr Varsity I
Forum|alt.badge.img+6

Hi @pdeatherage 
You can quickly check whether or not both instances are using the same database:

  • Upload your customization at the first instance.
  • Open your second instance and go to the Customizations screen
  • If you can see the customization - yes, they use the same database.

It’s a quite common configuration - for example when a client wants to have an ERP for internal use and a Portal for their clients to inquire about information related to them.

However, one database doesn’t mean they share the logic!

What I mean by that - you uploaded customization to the database. But it’s “dormant”, lying like an archive waiting to be applied.

You need to publish it in both instances. When you publish your customization, pages are copied from the customization package to the instance, database changes are made, the code responsible for handling the screen is injected into the instance, etc.

The database updating engine is smart enough to detect that the customization has been already applied, so don’t worry that the second publish will override schema changes.

Andrii Tkachenko | Sprinterra | https://www.sprinterra.com/ | If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
darylbowman
aaghaei
Vignesh Ponnusamy
5 people like this
  • darylbowman
    darylbowman
  • aaghaei
    aaghaei
  • Vignesh Ponnusamy
    Vignesh Ponnusamy
  • Chris Hackett
    Chris Hackett
  • P
    pdeatherage
P
Freshman I
  • pdeatherage
  • Author
  • Freshman I
  • 4 replies
  • August 2, 2024

Hello @andriitkachenko,

Thank you for your reply. That answers a lot for me. The problem is, that once we install on the main server, the other server’s pages become completely white, so we can’t access the customizations anymore as it just loads a white screen.

andriitkachenko
Jr Varsity I
Forum|alt.badge.img+6

@pdeatherage The only odd thing I see in your customization - is configuration of one field in the Database script:

It looks like it was manually changed. However, I’m not sure it affects the system in any way.

Other than that - I’d double-check the version of dev and prod servers, to make sure there’s no big gap in versions. The customization shouldn’t affect other screens outside of the one you’ve changed, so I suspect there’s something wrong with the server itself.

It’s hard to give you something more meaningful with the information I have right now.

Andrii Tkachenko | Sprinterra | https://www.sprinterra.com/ | If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
Chris Hackett
P
2 people like this
  • Chris Hackett
    Chris Hackett
  • P
    pdeatherage

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved