Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
two base and one reciver
kannan_r
Hi
we have a existing prod teamsite server ( base 1 ) which deploys to production web server ( rcvr 1 )
Now we have installed a new teamsite server ( base 2 ) which will still deploy to same production server ( rcvr 1 )
both teamsite servers one running 6.5 and second running 7.2 will be used in parallel for next few months, after which 6.5 will be retired.
was able to configure newly installed TS to deploy to reciver 1. Same virtual directories. At present I don't see any issues.
Question: will this cause any issue while OD is doing some internal checks ? should i expect somekind of problems deploying to same path from two different base servers ?
Find more posts tagged with
Comments
ISCBorisB
should i expect somekind of problems deploying to same path from two different base servers ?
You may certainly have problems with two or more
overlapping
deployments to the same target location.
This becomes especially sensitive if deployments are transactional. Transactional processing balances
up to three versions of the same File simultaneously (file itself, iwold and iwnew). All this may be completely
messed up with overlaps.
Auli2
I agree with Boris.
If you can post the problem statement then may be someone can suggest a better approach.
OS_BIRT_4.2.2_TopDateAsDefault.rptdesign
kannan_r
Issue description
1 .Existing Teamsite server 6.5 will be retired after 7.2.1 takes over
2. New Teamsite server 7.2.1,currently being installed and configured.
Existing DB,web servers will continue. Our Team does not have access to production IIS.
An overlap of 3-4 months where both servers will be used for UAT,SIT etc.
End users will have access to any one server alone at any given point. Only the development team will have access to both servers. Users will not even be aware of second server most of time.
There will be a small window when each individual site will be migrated,during which except myself+my team no user will have access.
I dont want to run into some strange problems with deployment,since targets overlap.
Certainly we can avoid near simultaneous deployments from both base servers.
Hope I dont run into strange deployment issues,during the short downtime period for migration
Thanks
ISCBorisB
You should be all right as long as multiple deployments to the same location do not overlap.