Setting Up Administrator and Owner Accounts | Operating System | Superuser

Please download to get full document.

View again

of 7
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report
Category:

Documents

Published:

Views: 6 | Pages: 7

Extension: DOC | Download: 0

Share
Related documents
Description
Setting Up Administrator and Owner Accounts
Transcript
  Setting up administrator and owner accounts When you run the IBM® InfoSphere® Information Server installation program, you mustspecify the user names and passwords for administrator and owner accounts for the program. In some circumstances, the installation program can create these accounts for you, but depending on your system administration policies, you might want to create these user IDs and passwords on each of the tier computers before you install InfoSphere Information Server. About this task reating administrator and owner accounts before you install InfoSphere Information Server ensures that operating system policies, such as re!uiring a password change at the first login, do not interfere with the installation program use of the accounts.reate the accounts as local operating system accounts, lightweight directory access protocol #D$%&, accounts, or 'IS accounts. ImportantIf you use #D$%, %$M, or 'IS accounts, you must create these accounts before you run the InfoSphere Information Server installation program. (he installation program cannot create these accounts. When you create the accounts, record the user ID and password for each user. If you choose to not use the default user IDs, the names that you choose must be distinct fromeach other in the same way that the default user IDs are. Procedure ).*n the operating systems where you install InfoSphere Information Server, ma+e sure that the user who installs InfoSphere Information Server can log in using the following accounts. (he user must log in using one of these accounts to install InfoSphere Information Server.  Table 1. User accounts that are required to install the product Operating systemAccounts  $I®#inu-Solaris  The root user account.   Table 1. User accounts that are required to install the product Operating systemAccounts Windows A user account in the local Administrators group. This account must be one of the following types: o A local account that is directly assigned to the Windows local Administrators group. o A domain account that is directly assigned to the Windows local Administrators group. .$I Solaris #inu-/ *n the operating systems where you install each engine tier, create the following additional accounts and record the passwords.'oteIf your installation does not include an engine tier, you can s+ip this step.  Table 2. Accounts that you create for an engine tier (A! olaris#inu$% Account descriptionDefault user namePrimary groupSecondary groupNotes® Administrator for the InfoSphereInformation Serverengine dsadm dstage  &ou customi'e this group to apply to your security model. This user performs administratie tas)s* such as adding new pro+ects and de,ning their properties. To run  +obs* create a separate user with the deeloper role. This account must be an account on the local operating   Table 2. Accounts that you create for an engine tier (A! olaris#inu$% Account descriptionDefault user namePrimary groupSecondary groupNotes® system. During installation time, you cannot specify a Lightweight DirectoryAccess Protocol LDAP! account as the engine administrator account. 0.reate the following database schema accounts based on your product set and record the passwords.'oteWhen using a DB® database, these accounts are operating system accounts. When you use a DB database for the repository, the DB database uses the operating systemauthentication for connection re!uests. (here are no specific group membership re!uirements for these accounts.  Table -. atabase schema accounts that you create on the metadata repository tier ProductsAccount descriptionDefault user nameNotes /equired for all products0etadata repository owner xmeta Important o not specify the 2 instance owneror administration serer user for this user name./equired taging area xmetasr Important   Table -. atabase schema accounts that you create on the metadata repository tier ProductsAccount descriptionDefault user nameNotes for all productsuser This user name must be dierent fromthe user name that you specify for theowner of the metadata repository ($meta%. The $metasr schema must bein the same database as the $meta schema. o not specify the 2 instance owner or administration serer user for this user name.nformation Analy'er3wner of the nformation Analy'er analysis database iauser Important o not specify the 2 instance owneror administration serer user for this user name.4uality tage53wner of the 4uality tage tandardi'ation /ules esigner database srduser Important o not specify the 2 instance owneror administration serer user for this user name. f you are installing the repository tier* this  must be createdbefore or during installation. f you usethe atabase upport scripts to createyour metadata repository database* do not create this user  before installing nfo phere nformation erer. 6roide the user  and password for the srduser during installation. cripts to con,gure this user and its tables will be generated
Recommended
View more...
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks