PEGA returns search results from another PEGA instance on the same server
Hello,
We're seeing a strange behavior when using the native PEGA search features (in a search input box on our Front-End UI).
First, I have to talk about our current configuration.
We have one server with multiple PEGA instances deployed on it. Let's say:
- /home/instance1/pega/...
- /home/instance2/pega/...
We've noticed that when searching for work-objects in the search box on instance1, we're seeing work objects from instance1 (as expected), but also from instance2 (not what we expect). When we try to open objects from instance2 in our instance1, we get an error message because the work-object cannot be found (as expected, since the object doesn't exist in instance1).
In our indexation screen (Designer Studio-->System-->Settings-->Search), each instance has its own Node ID and Index File Directory, so there's no reason for the search results to "collide" with another PEGA instance.
We know that there is a way to configure the server XML files so that we restrict the IP addresses that we can connect with, but since all our instances are on the same server, we can't use that.
Has anyone encountered this problem before? We really think this is a problem linked to the indexing, because originally we were trying to reduce the amount of work-object types returned in search results, yet we still see work-objects from another instance.
We're using PEGA 7.1.8.
Thanks for your help.
Hello,
We're seeing a strange behavior when using the native PEGA search features (in a search input box on our Front-End UI).
First, I have to talk about our current configuration.
We have one server with multiple PEGA instances deployed on it. Let's say:
- /home/instance1/pega/...
- /home/instance2/pega/...
We've noticed that when searching for work-objects in the search box on instance1, we're seeing work objects from instance1 (as expected), but also from instance2 (not what we expect). When we try to open objects from instance2 in our instance1, we get an error message because the work-object cannot be found (as expected, since the object doesn't exist in instance1).
In our indexation screen (Designer Studio-->System-->Settings-->Search), each instance has its own Node ID and Index File Directory, so there's no reason for the search results to "collide" with another PEGA instance.
We know that there is a way to configure the server XML files so that we restrict the IP addresses that we can connect with, but since all our instances are on the same server, we can't use that.
Has anyone encountered this problem before? We really think this is a problem linked to the indexing, because originally we were trying to reduce the amount of work-object types returned in search results, yet we still see work-objects from another instance.
We're using PEGA 7.1.8.
Thanks for your help.
***Updated by moderator: Lochan to close post as per originator's request***
PEG
GB
Hi Paul,
I regularly have several servers running on the same machine. But I don't believe I've encountered this problem before.
Are these two different pega instances running on different database instances (or at least schemas)?
Also can you confirm which version of Pega you are using?
Thanks
Laurence
SopraSteria
FR
Hello Laurence,
Thanks for the reply.
In this particular configuration, we have 1 server hosting the database for all instances. Each PEGA instance has its own independent database instance, so they're completely isolated from one another (separate tablespaces, separate schemas, separate connexion details, etc).
It should be noted that we do, for some instances, dump databases to import rules & data to other instance (for bug testing, etc). But in this case, neither instance1 nor instance2 share a dump (or one being a copy of the other, through a dump), so we don't see how this could be a misconfiguration (although it probably is one... somehow).
We're using PEGA 7.1.8 (edited main post to add this).
Regards.
Pegasystems
US
>>>We have one server with multiple PEGA instances deployed on it. Let's say: - /home/instance1/pega/... -
>>> /home/instance2/pega/...
I use the tomcat server, and for one PEGA instance, I deploy prweb plus the prsysmgt plus the prhelp.
If I want MULTIPLE PEGA instances, I copy the entire tomcat server folder, and change the port numbers in that second folder, and I make sure I change certain folder references in the tomcat set up files such as the pega temp folder so that each folder has its own.
But I haven't tried deploying MULTIPLE PEGA instances under one tomcat server. Is that the sort of thing you are doing? If so, would it be easy for you to try it similar to my way just to see if it resolves the issue? /Eric
SopraSteria
FR
Hi Eric,
Sorry for the late reply, it doesn't look like the mail notification system for new replies is working..
I forgot to specify this, but yes, we actually have independant web-servers for each instance too. We really went all the way with independance, as we need to be able to add/remove them as necessary.
The only thing the instances have in common is pretty much the server address (not the port, which is used to differentiate instances), everything else is separate/isolated.
Pegasystems
US
If each node has its own index folder, but one node is seeing work objects from the other node, then it sounds like both nodes has assocations with the same work object database, so you should check for that.