VisuaLizeFOCUS . Posted January 21, 2022 Share Posted January 21, 2022 How we can check WebFOCUS Repository version by looking the config files Link to comment Share on other sites More sharing options...
Doug Shartzer Posted January 21, 2022 Share Posted January 21, 2022 Its in edaprint on startup. theres also a version.cfg file in home/etc Link to comment Share on other sites More sharing options...
VisuaLizeFOCUS . Posted January 21, 2022 Author Share Posted January 21, 2022 I checked it gives the version of your WebFOUCS. In some cases it might happen that the version is latest but they are running on OLD Version of repository. Link to comment Share on other sites More sharing options...
David Hall 5 Posted January 21, 2022 Share Posted January 21, 2022 The WF repository layout structure and tables used varies between the various 8.x releases. There is a utility folder in the WebFOCUS folder on the WFC client that has a number of windows and Linux batch/script files. These are run during the migration process, but also can be run manually. You may want to look at these and see if any of them could assist in getting the information you need Link to comment Share on other sites More sharing options...
Toby Mills Posted January 21, 2022 Share Posted January 21, 2022 I dont know if youd see the repository version sitting in a config file. Perhaps theres something a log file though. The config files will basically just identify the database you want to use (like Oracle or SQL Server) to hold the repository. Youll have the database servers name and a user ID / password to connect with. But - that is just a pointer to hit the database. Inside the database is where the repository info will likely be. So a query would have to go off first to check for characteristics of the repository. I wish I knew of an easy place to go get a version of the repository just for informations sake, but I dont know how much you need it. I see youre going from 8105m to 82x. My guess is your concerned that your repository wasnt updated. The utilities/wfrepos/WFReposUtilCMDLine might be a good thing to check out if you havent already. Id bet that the event log would complain as soon as it starts up in 82x if your repository is still sitting at 8105m for some reason. You could test this by making a copy of your 8105m database and then pointing to it in your 82x environment. Try starting up the application and look at event.log. You wont hurt anything other than possibly your copied 8105m files. Id suggest opening a case if you really need to know how the repository version works. If you care to give us info on what the problem is that youre trying to solve or avoid, that might help us steer you in a better direction. Link to comment Share on other sites More sharing options...
Sarah Buccellato Posted January 31, 2022 Share Posted January 31, 2022 RJNegi, were the suggestions that David and Toby provided helpful Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now