SMP 3.0 cluster: Deployment (publish) of Agentry is incomplete.

[Former Member]

Hi Experts.

We have installed a Test environment of SMP 3.0 (SP04 PL01) in a Production setup.

We have one Oracle DB server and two SMP 3.0 application servers in SMP cluster.

I have created a "Hello World" Agentry Application and deployed in one of the cluster instances.

After a few seconds, I see the Application on the other cluster node.

But if I inspect the file system (<SMP_HOME>\configuration\...) not all files are deployed on the second instance.

It is only Agentry.ini and a few other files.

I can correct this by doing a publish directly on the second node, but is this really per design ?

Or is it a bug in SMP ?

Does anybody have experience or knowledge in this area ?

Thanks.

Søren Hansen

[Former Member · Accepted solution]

Did you a Agentry Development or Agentry Production Logic?

Only Agentry Production Logic is supported for SMP Cluster.  (Note, the Agentry.ini on Agentry Production logic is not used as it is store in the database)

Stephen

[Former Member · Accepted solution]

Hi Steve.

I was not aware of this limitation. But my application does indeed contain a development application logic. I will publish it as a production instance instead and let you know the result.

Thanks,

Søren Hansen

[Former Member · Accepted solution]

Hi Steve.

I have now tested this and can confirm this to be correct

When publishing a production version of the application, the cluster handles the deployment among the nodes correctly.

Thanks again.

Søren Hansen