Could anyone please help me with steps to upgrade "My WebMethods Server" from 10.1 to 10.5 using/applying patches/fixes?
Upgrade document is clear enaough if you read it all but just in case you want to play safe, this is how I’ve done it:
1- Install DBConfigurator to new location (If you are performing upgrade on the same machine).
2- Install Update Manager.
3- Install latest fixes for DBConfguratior.
4- Run the latest db scripts. (If you installed the scripts already, perform migrate operation after installing fixes for DBConfguratior).
5- Perform Installation of the new version.
6- Shutdown both old and new instances. Run the migrate utility from the new installation.
7- Migration utility will ask for old version installation directory. (Or you can have an export of the old version as a zip file).
8- Follow the steps guided by migration utility, It will ask couple of questions which you can answer by typing Y or N.
9- If everything goes OK, you should be getting the message below. (Might be different for newer versions.)
Failed migrations
None
Migration successful. Exiting the migration utility.
*** End Integration Server Migration ***
10- Validate the scripts you are using for startup have the new installation directory. I faced a couple of problems with that.
Bonus : Make sure the extendend setting about java compiler have the right path for the jvm. watt.server.compile=…\jvm\jvm\bin\javac -classpath {0} -d {1} {2}
Related
I am trying to run Pentaho Data Integration (ver. 8.3) in my Windows machine and it is not working.
These are the steps I tried to make it work:
Tried rebooting the machine without success.
Also tried to run the Spoon.bat command directly from the directory where Pentaho is located, but it did not work.
Checked if my java installation changed since the last time it worked, it did not, what can be happening?
In a support chat I read someone was able to fix the problem by clearing the cache, but did not explain how to do it, how do I clean the cache?
Have you installed >jdk java 1.8 environment?
And you should open powershell or other terminal to check: java -version
These are the steps to clear the cache in a Windows environment:
Go to C:\Users\youruser.kettle
Look for the file db.cache-* (I have PDI version 8.3, my file is named db.cache-8.3.0.0-371)
Edit the file with any editor (i.e. Notepad) and erase all content
It worked for me!
First, you should run .\data-integration\set-pentaho-env.bat; It will set pdi environment. The most important is the Java HOME, and JAVA Version. PDI 8.3 can only run in JAVA 1.8 and above.
I am new to Linux and non-Microsoft web development (long time MS developer). I am making some kind of fundamental mistake when I install Linux programs but I don't know what.
I am trying to install spring-boot-cli for use to make a Java microservice. I am just trying to learn how. I followed the installation instructions I found here, ending up using the SDKMAN installation method: https://docs.spring.io/spring-boot/docs/current/reference/html/getting-started-installing-spring-boot.html
When I try to run spring --version, it says spring is not installed. When I go back and try to install it again, sdk says, "STOP! this is already installed."
I am having a similar problem with Maven. I try to run command line commands and it is not recognized, but it claims it is installed.
a bit unusual but at the terminal type:
> which spring
and then
> $PATH
should give you a starting point.
How do you upgrade MongoDB on Windows server? Running the Windows installer for the new version only installs a new copy of MongoDB and ignores the existing copy.
Edit:
First start the cmd.exe in admin mode and cd to the location of the old installation, for standard installations:
cd C:\Program Files\MongoDB\Server\3.2\bin
Stop all applications, which are accessing mongodb, then enter
mongod --remove
Then install the new mongo db, copy the mongod.cfg file from 3.2 to 3.4 directory. When you had one, otherwise follow the installation instructions for setting up the new service. This update worked fine for me, all data available, I didn't need to use this features switched off.
I upgraded from version 3.6.0 to 3.6.2 just today and below are the steps involved:
Download the latest version from the [mongodb wesbite][1].
When downloading is complete, stop any running instance of mongodb by typing 'Ctrl+C' on the command console.
Run the installation file and it automatically installs the new version at the same path as the previous version (at C:\Program
Files\MongoDB\Server\3.6).
Start the database server by typing 'mongod'.
All previous databases will be accessible to you.
Windows MongoDB major version upgrade can be performed easily in-place , here i am describing the steps to upgrade MongoDB 4.2 to 4.4 with existing data directory. You can follow the same for any version upgrade.
We will use the Windows command prompt to perform all steps below:
For safety take a backup of existing DB, provide a path to backup them
cd C:\Program Files\MongoDB\Server\4.2\bin
mongodump -o D:\DB_backup
Stop all the application writes and shutdown the MongoDB service
type "services. msc" and hit Enter or press OK
Services -> MongoDB Server -> Right click & stop
Install the new MongoDB mongodb-windows-x86_64-enterprise-4.4.8-signed.msi file msi package by using GUI provide the old exixting directories. Meanwhile rename directory from 4.2 to 4.4
Data dir - D:\MongoDB\Server\4.4\data
Log dir - D:\MongoDB\Server\4.4\log\
This will replace all the bin files with older version ones and MongoDB will be started automatically.
Finally , move to the bin directory, run mongo.exe client and check the DB availablity
cd C:\Program Files\MongoDB\Server\4.4\bin
On windows pro.
It worked for me like below:
Install new version without uninstalling existing.
Stop the mongodb service.
Copy data folder from previous mongo to new mongo folder.
Repair new mongo installation.
Uninstall previous mongodb.
So I upgraded to MacOS Sierra and now whenever I try to do anything in my working copy I get the error that it
"is too old (format 29) to work with client version '1.9.4 (r1740329)' (expects format 31). You need to upgrade the working copy first."
When I run svn upgrade, as it suggests it says
"Can't open file /.svn/entries: No such file or directory"
Any suggestions will be greatly appreciated!
Open Terminal
go to error folder. ex : cd svn/project/game
command write only "svn upgrade"
Your problem is that the version of the SVN client got upgraded locally; whereas your local working copy (and the server) didn't change! Now the new client is unable to work with the existing working copy.
Now you have three choices:
You can try to get your new SVN client to accept the existing working copy
You downgrade your local SVN client to the previous version
You throw your existing repositories away and start with fresh checkouts
For option 1, you might look here or there.
For option 2, this might help.
Option 3; I guess, is the one-line-no-brainer which maybe costs you download time, but should come with the least amount of "you spending your time" debugging this (unless you got a ton of uncommitted changes sitting in your current repositories). But of course, you would first try to create a new checkout with the new client, before throwing the old directory away.
I solved my problem by doing the 'svn upgrade' on the 'cd' of root folder of the project
An update was downloaded automatically by my 2.6.3.RELEASE Build 201411281425.
STS (Spring Tool Suite) asks to install it and when I click on the pop-up window it does some things and then stops with the following message which seem to indicate that it wants to delete itself.
I can understand why this fails but I am not sure why STS would think that this was possible.
I could not find any instructions about manually installing the zip file that is available as a download as an alternative way to upgrade my installation.
How do I fix the automatic install or manually install the zip?
(I am on Windows 7)
Error message:
An error occurred while uninstalling
session context was:
(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall,
operand=[R]org.springsource.sts.ide.executable.win32.win32.x86_64
3.6.3.201411281415-RELEASE-e44
--> null,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file C:\RAMDrive\spring\STS.exe failed.
File that was copied to backup could not be deleted: C:\RAMDrive\spring\STS.exe
Start the STS you want to upgrade and before you click on "Check for Upgrades", with STS still running, rename the STS.exe file you just started, to something else, like "STS_old.exe". That should do it.
The message sounds strange, I've never seen this before. To install a fresh copy of STS, just download the ZIP file from the download page (the one that matches your operating system and pick the right 32bit or 64bit one, depending on your OS and the JDK you are using). Then unzip, and start STS.exe. That's it.