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

Access to iwcommon, iwlscsauth and iwsitepub

anjanas

TS732, Linux

-----------------

In our tightly controlled system, we are not granted access on server and upon request, we will get restricted access. Do we ned access to these databases as developer and Production support team ?

Do I require a database while installing TS ? I was going through one post and it stated "I am installing TeamSite with MySQL database". If I am not using database while installing TS, it will still install.

Where can I find information about iwcommon, iwlscsauth and iwsitepub ? These are the databases in a database where content is getting deployed. One of my colleue is asking to get acess to these databases and I am curious to know about this. I checked all manuals, but could not find these terms in any doc.

Please explain about these databases.

thanks

Find more posts tagged with

Comments

Adam Stoller

Generally, you do need the databases to do the installations, and you will need some form of service account set up and used during the installation process that will then be used by the product to access the databases - but you should not generally, as an individual, need to access those databases - at least not iwcommon - I'm a bit less sure of the iwlscsauth and iwsitepub databases, though I think those too would be accessed internally using the service account configured during installation time.

Rick Poulin

As fish said, you don't need user access to those schemas -- you only need a service account that has rights to create objects and execute normal CRUD ops.

Only the sitepub database is optional (and generally not needed). The others are required and you can't go further in the installer without them (it will validate that it can connect using the given values).

Generally speaking, if you do need a database for custom data, you're better off storing that in a different schema to avoid any conflicts with IW objects and future updates, and you can manage access rights to those as necessary for your development lifecycle.

anjanas

rpoulin wrote:
As fish said, you don't need user access to those schemas -- you only need a service account that has rights to create objects and execute normal CRUD ops.

What is service account ? Any business user access OR developer access to TS is service account ?

rpoulin wrote:
Only the sitepub database is optional (and generally not needed). The others are required and you can't go further in the installer without them (it will validate that it can connect using the given values).Generally speaking,

So, when I start installing TS, do iwcommon and iwlscsauth get installed by itself OR do I need to install it separately ? I never saw anything as iwcommon or iwlscsauth on the server where TS is installed. Everything I saw is iwserver, iw-store and file system. Where is iwcommon or iwlscsauth located ? Is it on runtime environment , where LSCS is installed (which is different server) , where odreveiver is installed? If so, then how does it interfere with TS installation , which is installed on server where business users access and where odbase is installed ?

Thanks

Adam Stoller

A service account is an account that the SysAdmins setup, which run on the OS and are used to communicate with "services".

Have you read through the installation manuals? That should answer most of your questions regarding what is needed during the installation process.

Rick Poulin

anjanas wrote:
What is service account ? Any business user access OR developer access to TS is service account ?

A service account is a third type. It's a "normal" database user, except it's only used by system services, NOT users or developers. In theory, the only person that needs the password for that account is the person who installs the IW software, and only for the purposes of the install.

To answer what I think was part of the second question, these databases are auto-populated by the installer, which is why the service account needs rights to create objects and why developers should never need to go in there manually.