[windup-dev] EAP6-EAP7 migration

[Eduardo Martins]

> On 10 Sep 2015, at 02:38, Ondrej Zizka <ozizka at redhat.com> wrote:
> 
> Eduardo,
> 
> is it possible to do a system call (instead of direct API usage) to run a generated CLI script and let AS deal with it?
> Or a system call to boot the controller, and then use the REST API?
> 

Suppose you could do that, and the development of such functionalities would be less effort than developing the rules to handle the migration of 3 subsystems, then before you could invoke :migrate you would still need to parse and transform the old subsystem XML into management ops, i.e. need all EAP subsystem parsers. And you would also need to somehow transform the :migrate result into high level Windup report entries (targeting the source of migration, the XML).

If you are trying yo avoid the XML rules with XSLT, due to XSLT complexity, an alternative would be Non XML Windup rules using a generic XML API, integrating the code logic of :migrate ops, which is short and not very complex. IMHO much less effort than what you propose above.

> The reason for that is, that AFAIR, fiddling with standalone.xml was officially deprecated way of configuring EAP, and the recommended, forward compatible way, was officially CLI commands.
> Is that still the case?
> 

Recommended != mandatory, we certainly need to cover the migration of XML server configs, it’s the basic EAP config process, and is supported by Red Hat.

—E