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; } } }

Solaris: Base server not same as TS?

miletwo

Hi all,

Just curious if anyone has ever tried running a OD Base on a different box than the host TS? We're finding an increased amount of traffic to our TS box and thinking of putting some similar smaller apps (like OD) onto another box that way the TS GUI can be dedicated to users, OD and Control Hub, and possibly search on another box (with nfs mount or something).

Any thoughts?

It will probably just create bunch of headaches but theoretically should help to spread the load around, yes/no?

Thanks, Jeremy

Find more posts tagged with

Comments

civ3

Hi

I'm interested in this too. Never tried before. I think it depends on the type of deployment configurations your site have. It should be fine if they are file system based and no metadata is involved.

Regards,
civ3.

Adam Stoller

Hi all,

Just curious if anyone has ever tried running a OD Base on a different box than the host TS? We're finding an increased amount of traffic to our TS box and thinking of putting some similar smaller apps (like OD) onto another box that way the TS GUI can be dedicated to users, OD and Control Hub, and possibly search on another box (with nfs mount or something).

Any thoughts?

It will probably just create bunch of headaches but theoretically should help to spread the load around, yes/no?

Thanks, Jeremy

I believe that the general recommendation is that (for Production usage) ControlHub (which has it's own internal TS server) and Search be put on a distinct server from the primary TS server - if you do that, then having OD Base on the same server as TS should not be an issue.

If you want to further segment OD from TS, you could probably do it, but you might run into issues if you try to utilize TS features within OD (like edition differences, or source-side DNRs that run TS CLTs, etc.)