Infor Cloverleaf Integration Services 6.1.2 now available

[Rob Abbott]

Infor Cloverleaf Integration Services 6.1.2 now available

​The Infor Cloverleaf Integration Development and Product Management Teams are pleased to announce Infor Cloverleaf Integration Services 6.1.2.  This release

Rob Abbott
Cloverleaf Emeritus

Topic

[Bob Schmid]

Robb,

In order to solve our symlink issue with adv security and also to take a smaller/simpler” step to get there as opposed to 6.2.1……I think we are going to try to upgrade to 612 in the near term.

Running AIX 6.1.9

Any implications gotchas in terms of converting:

CL 611 to 612? including considerations for GM and advanced security?

We are running GM 6.1

Main reason to upgrade to 6.1.2 is the following:

Mercy leadership wanting adv security installed ASAP…”ROI”

We use symlinks from one site to another extensively…..which is (as I understand it) not supported by security under cl 611

upgrading to 612 would allow us to continue with symlinks pointing  from one regional site to another regional site in Cloverleaf.  True?

Would CL 612 w / Advanced security also allow us to point outside of Cloverleaf to different vg’s?  (not critical but curious to know)

Thanks for your advice.

Bob

[Bob Schmid]

During the period in that we are cl 612 in test and 611 in production…?

Are there any constructs not compatible with each other?

ie Can I  cutover a 612 NetConfig to a 611 environment?..or a 612 xlate to a 611 environment

plan would be:

1. install 612 server&client overtop test 611…….testout

..and then install in live. (probably 2-4 weeks)

Bob

[James Cobane]

Bob,

I think you may run into Client GUI issues when trying to connect a 6.1.2 client to a 6.1.1 server.  While the configuration files (Xlate, formats, Tables, etc.) are likely interchangeable/portable, using the Client GUI may be problematic when connecting to a lower versioned server.  Just my $.02

Jim Cobane

Henry Ford Health System

[Bob Schmid]

….and it is an unfortunate design… 6.1.2 being in same root as 6.1.1…I don’t recall this being an issue ever before…in upgrading..it does not give us a technical “path” for first testing and then cutover to prod.

Bottom line…not ready for 6.2

being told 6.1.2 and 6.2 hold resolution to Security shortcomings…ie symlinks…addressed in 612.

Bob

[Author]

Replies