Thread: existing 3.2 software in 4.0 cluster

I guess this should have simple answer and I just missed it some how (though I have a vague idea I've seen it written possible somewhere), but my question is as follows:

I've got existing service/client software (C++) running on 3.2 cluster. Can I deploy it without recompilation to the 4.0 cluster?

My attempts produce following error:

The Session Director for the SOA Middleware cannot be located by the grid or the grid simulation component. Details : vem_locate(vemHandle<0074BC80>, name<SD_SDK>, clientInfo<0012E094::00000000) returned "1 : Bad arguments for APIs"

Thanks,

Gennadiy

Hi Gennadiy,

Yes you can run your 3.2 client/service binaries under 4.0. The only issue is that you must load the Symphony 4.0 libraries in your client and not the 3.2 libraries. You don't need to re-compile your application, unless you need the new features in 4.0.

1. Deploy your 3.2 service package into the 4.0 cluster using the 4.0 Migration Wizard or soamdeploy (4.0).

2a. If using soamdeploy, you need to modify the <SOAM> version= value in your application profile from 3.2 to 4.0. Don't change the <Profile> version.

2b. Register the modified application profile using soamreg

3. Install the 4.0 package on you client machine. Ensure to source the 4.0 env on linux or start the 4.0 cmd prompt on windows.

4. run your client.

- Ajith

Originally Posted by rogeeff

I guess this should have simple answer and I just missed it some how (though I have a vague idea I've seen it written possible somewhere), but my question is as follows:

I've got existing service/client software (C++) running on 3.2 cluster. Can I deploy it without recompilation to the 4.0 cluster?

My attempts produce following error:

The Session Director for the SOA Middleware cannot be located by the grid or the grid simulation component. Details : vem_locate(vemHandle&lt;0074BC80&gt;, name&lt;SD_SDK&gt;, clientInfo&lt;0012E094::00000000) returned "1 : Bad arguments for APIs"

Thanks,

Gennadiy

I figured out my problems. The reason for the error was that 3.2 SymDE libs where in client directory and picked up instead of those of SymDE 4.0.

Great! Thanks for the update - Ajith

Originally Posted by rogeeff

I figured out my problems. The reason for the error was that 3.2 SymDE libs where in client directory and picked up instead of those of SymDE 4.0.