Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SHARING] Change Management - Deployment from TEST to PROD

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SHARING] Change Management - Deployment from TEST to PROD
 Login/Join
 
Noveta
Member
posted
We are trying to get some procedures and best practices in place. I have read up a little on the Change Management Utilities.

1) I was interested in hearing more feedback if it is necessary to use the Change Management Utilities if our Production and Test environment is on the same server. Right now we are copying and pasting from one area to another area.

2) Should we have a Test environment and DEVL environment. I saw some developers use naming conventions differently from the files differently in TESTING ..is that a best practice.

Thanks any feed back is appreciated.

This message has been edited. Last edited by: Kerry,


7.6.2
 
Posts: 20 | Location: 7.6.2 | Registered: November 04, 2008Report This Post
CLH
Platinum Member
posted Hide Post
Hi, We use the change management utilities. Though our test and production environment are on 2 different servers. Everything has the same names in both environments. The developers can then use the change management extract utilitiy to create a zip file of the code they want moved. They mail that to the admins and the admins move the file to the production server and run the load. We started out with cutting and pasting but that caused issues down the road as the underlying names of the focexecs were getting changed. Then when referenced in and HTML screen or dashboard the Focexec would not be found. We had to do some clean up but now with the CM utilities names stay the same between servers and no more issues of not being able to find a called module.


Webfocus 8.0.7 on Windows
 
Posts: 176 | Location: Ohio | Registered: October 26, 2006Report This Post
Laure
Gold member
posted Hide Post
We also use the CM utility and find it works fine. We developed an in-house utility for zipping application objects and transfering them in a similar method, as the CM works for only MRE code.

We also go as far as only letting select individuals being allowed to migrate from a DEV to QA and then to PROD environments.


Laure

Prod: WebFOCUS 7.7.03 - MRE, BID, - WindowsXP - Oracle 9i, SQLServer, DevStudio 7.7.3 - Apache Tomcat , Output: HTML, Excel 2013 and PDF
 
Posts: 78 | Location: Florida | Registered: December 07, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SHARING] Change Management - Deployment from TEST to PROD

Copyright © 1996-2020 Information Builders