WildFly Migration Issues

Special Notes for WildFly

Special attention should be paid when migrating WildFly server accounts.

This is due to changes in the WildFly file structure used by NGASI.

If the migration.json file is not created correctly, you will need to update the file with the correct values manually.

The correct form for the migration.json form is displayed below:

{
   "jdk" : {
      "name" : "JDK",
      "version" : "jdk1.8.0_60",
      "path" : "/usr/java/jdk1.8.0_60"
   },
   "server" : {
		"path": "/usr/coffeecp/appfiles/wildfly-10.1.0.Final.zip",
		"version": "10.1.0.Final",		
        "type": 2,
        "folder_name": "wildfly-10x",
		"name": "WildFly"         
   },
   "memory" : "-Xmx512000000 -Djava.awt.headless",
   "value" : "512",
   "ports" : {
      "ajp" : "4592",
      "shutdown" : "4595",
      "https" : "4593",
      "http" : "4594",
	  "mgt_http": "5067"
   }
}

The ports section of the json file will never need to be updated. Only the server and jdk elements may require updating.

Once you have updated the file, SSH to the server as root and follow the steps below

Change to the /usr/coffeecp/paths directory:

cd /usr/coffeecp/paths/

Issue the following:

php migration.php

The above PHP script should create any missing files for the user and you should now be able to proceed with migration.

If you have issues or questions, please contact support.

Up Next: Users Guide

CoffeeCP Users Guide