as we want to migrate our ACS4 from one platform to another we need to operate two ACS4 instances with two fulfillment services parallel for a limited period of time. We are using dedicated hardware for each instance and want to operate them on different individual URLs.
Can we simply create a second P12 certificate and add the new URL via operatorClient using the same AdobeID as we are using for the first instance?
Or might this affect our first instance, so that we would need a second AdobeID for the second instance?
If you are truly migrating and plan to do a database migration, then your best bet is to keep the OperatorURL then same. For testing I would suggest pointing at the new server via an entry in your hosts file (on the client, not the server).
Does Adobe permit clustering the fulfillment/packaging/admin .war applications, so to have fault tolerance? Seems like if you wanted to have two web front-ends, handling only one environment, that's purely a implementation design detail.
I could see if someone wants to have two distinct ACS4 exclusive environments, handling different content and different customers.... but if one wanted to make the web services highly available, does Adobe require the purchasing of additional licenses?
The original post was about doing migration, which is different than running in a HA environment.
For running ACS4 in a clustered scenario, have a load balancer point at individual nodes.
Have the nodes all provisioned with the same operator URL (which should be the public URL for the cluster), and key.
Have a seperate Database server (clustered, replicated, etc as your situation requires) that all of the nodes talk to.
As for what it's going to cost you, that's between you and Adobe or you and the SI partner. However I haven't heard of any them charging different fees for this, unless you have them do the hosting.
Europe, Middle East and Africa