Problem with 2 SC-projects on the same server

Applications Database Connections
#1

Hello,
I have two different SC-projects running on the same production server.

Project A uses connection namedAxxxx
Project B uses connection named Bxxxx

Both application have nothing to do with each other.

I open A in Browser … A starts … then in the explorer site I gave in the web site of B.

B will not start but give an error message that connection Bxxxx is unknown.

If I close my browser… open it again … call B everything works…

So the first start of A produces an error when starting B.
The reason may be that the session id is not changed and the internal variable of SC from project A are disturbing the start of B

Any idea how to avoid this problem ??

Best regards
Uwe Pfeiffer

#2

I think it’s a problem of the cookies. Sounds like a serious problem here. I think that if you clear cache before you start app number two it will work right.

#3

Hello,
yes a problem of cookies or of session id.
But with this error it’s not pssible to open 2 SC-Projects at the same time…in the same browser…
I think the developers should think about it…

Other code generators use a prefix for every project just to avoid this error…

Best regards
Uwe Pfeiffer

#4

I verified the same issue, have two application on my companies intranet site and tried to access one and then open the other.
Connection Error also…
NEVER would have guessed it would have been,
Opened a chat with support and they asked me to verify that my VPN into network could have been issue (Wasnt)
Will let you all know anything more once I get done with support.

Kev

#5

Well it’s not a bug but a design error. It’s not logical to open two projects at the same time, but if you need to do so you might consider using two different browsers, i.e. Internet Explorer and Firefox. They maintain their own cookies. Not nice, but a work-around.

#6

Albert,
Your missing the point…
Try this…
Open an application not local a deployed app ( I use security, so I will use this as an example.)

  1. Login
  2. Exit
  3. Go and open another application.

For example
I have a customer application in my project called Purchase Orders, which I have on an intranet site link.
I go into the application and do anything.
I exit the application and choose an application that I have in my Payroll project which I have on an intranet site link.
When I click on the link to sign into the payroll app

Two separate projects nothing related.

Connection ERROR

#7

Hello Guys,

If you are working with multiple projects deployed on the same server, instead of deploying projects one by one (apart), therefore having multiple prod environments on the same server. When deploying multiple projects on the same server, you should deploy on a single prod environment.

regards,
Bernhard Bernsmann

#8

So what your telling us if I have created 20 projects, with 20 or so applications all with their own security, connection settings, users that I should put all of them into a single project and deploy from there?

That cannot be what you mean

#9

Not at all. Sorry for not being clear :stuck_out_tongue:

I meant that for deploying multiple separated projects on the same server, it is recommended to have a single PROD ENVIRONMENT (not a single project), and from this unique PROD environment, you will be able to create connections, and access any settings to every single project you may have on the server.

Advanced Deployment: http://downloads.scriptcase.com.br/downloads/v6/manual/en_us/webhelp/manual_mp/30-Publicando_Aplicacoes/02-avancada.html

If you run into any issues while deploying, please get in touch with our support. Our chat is active on workdays from 8:00am to 6:00pm, and our ticket system is always available.

regards,
Bernhard Bernsmann

#10

This is something I for sure will run into. Am I correct that you will deploy all your projects under the same libs? Sharing the lib stuff for sure will limit needed system resources but might have issues on a new scriptcase release. Then you can only deploy if you have regenerated all applications and deployed them. As the amount of data is pretty large, this might become a problem. Other issue is that we like to test our release on every deployment, which will limit our human resources. First we need to test all our apps and then deploy. Need to think about that… I think it’s cheaper to make multiple url’s on the server? What if you use subdomains?

#11

Hello Albert,

you are right… that’s the reason for I develop each SC project with it’s own libary path. So I’m more flexible.
And there are so many issues coming with every new version of SC that I will never public all projects with the same library.

Perhaps a special prefix (like XXY_) for each project, so that all internal project variables of SC do not disturb each other…because the all are name
XXXY_nm… XXXY_nm…

As i said… that’s the way other companies solved this problem …

Best regards
Uwe

#12

I was told that they couldnt replicate on their servers so must be ours…

I am calling BS

I really think “all of us” need to test this.

I was thinking of opening the project that doesnt use the connection and just creating one.
But how do I just deploy a connection and not everything else…

#13

Not sure if I undertood this thread correct, but I am having same question atm. 1 Project using a TestTable during development, when deployed uses a LiveTable…I thought there is a way of changing the connection during deployment, but now I have to change connection with project before I can deploy. Not sure if this is the issue here. But this would mean I have to change connection with each single app???

#14

Are you confirming you are having the same issue??

#15

Ok guys I have figured out a workaround and tested it and I no longer get the errors.

For each project you have on the server go into the _lib directory and configure the production server for each connection.
For me it wasnt that bad. I had 5 projects deployed.

Here is what I will be doing going forward.
I will create in any new or existing projects all connections that I will use all connections (STUPID and TIME CONSUMING)

So If I after I deploy the application to the server I will have to set the connections but at least they will be there.

But like I said, they are saying it isnt their problem.
But this does fix the issue.

Yeah go ahead and comment…

#16

I don’t understand your solution I’m affraid. Did you deploy all application with their own full lib? I always edit connections on the production server, you simply have to… What am i missing?

#17

Albert
Ok let me try and explain
Lets say I have 3 separate projects deployed to the same server and if I log into Project A exit the project and then go to Project B in the same browser I get the error of connection not found

Project A uses a conn called conn_A
Project B uses a conn called conn_B
Project C uses a conn called conn_C

What I did was create a conn_A,B and C in each project setup in the prod environment

That way if I switch to any project the connection will be there

This all because support says not our problem

As I stated before BS

Kevin

#18

Hello Mr. Drent,

You can upload each project separetely even though they share the same production environment.

@everyone, Try making an advanced deployement, or creating subdomains to assure this issue will not happen on your deployed projects.

regards,
Bernhard Bernsmann