nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployment Agent Install

Alligator

We are planning on installing deployment agent to see if it may be a solution for several customer requirements. We intend to install the deployment agent on the same server as the asset server and web client, with the DA database on a shared database servers. Any issues we should know about?

Thanks.

Find more posts tagged with

Comments

msrinivas

Though not recommended you might be able to get away with it especially in a dev environment.

Please keep in mind that DA is not part of the base product and requires additional licensing.

Alligator

Not recommended to install it on the asset server or just not recommended?

Thanks for the heads up on the licensing.

Gary

lyman

Depending on how many assets you are processing, for performance reasons we generally suggest separate servers. Also that arrangement makes diagnosing problems somewhat easier should they arise. However, there are no architectural reasons arguing against except the finite pool of resources and so if you are satisfied with the performance especially if you intended to do this on a Development box, go ahead.

Cheers,

Lyman Hurd

sridharg

Just out of my experience - we had DA on the same server as asset server and the DA had many schedules to run , which created huge performance issue. This also created performance issue when not only browsing the MB server, but also when contacting MB through ECM from Teamsite. We had a bad time really.