TIBCO BW Administration is for User Management,Resource Management and Application Management
User Management -Managing authentication, roles, and users.
Resource Management -Managing machines, applications, and deployments.
Application Management -Creation, configuration, deployment, and monitoring of applications.
Roles and Responsibilities
Various roles are recommended during a BW development project i.e.Domain Administrator,Project Administrator,Building of actual BW solution
User Management -Managing authentication, roles, and users.
Resource Management -Managing machines, applications, and deployments.
Application Management -Creation, configuration, deployment, and monitoring of applications.
Roles and Responsibilities
Various roles are recommended during a BW development project i.e.Domain Administrator,Project Administrator,Building of actual BW solution
Domain Administrator will Configures domains and grants access to different projects and runtime components.
Project Administrator responsible for maintaining a specific server-based project and maintains project templates, common services, global variables, shared resources, and shared schemas.
Developer Builds the actual BW solution.Release / Test / Deployment Engineers optional roles responsible for testing, building EAR files, and deploying EAR files.
TIBCO Administration Domain
A collection of users, machines, and services managed by a TIBCO Administration Server and secondary servers may be added.Here cannot run a master and secondary on the same machine.
TIBCO Administration Domain
A collection of users, machines, and services managed by a TIBCO Administration Server and secondary servers may be added.Here cannot run a master and secondary on the same machine.
Multiple administration domains may exist on one server.Each domain must have an associated master server.Stores user and group information in the domain data store.This can also sync with LDAP for users and groups and supported LDAP servers include SunONE Directory Server, NovelleDirectory, and MS Active Directory.
By default, all machines that belong to a domain are expected to be on the
same network subnet.This can use RVRD if access across subnets is required.
Administrator Users and Roles
Maintain ACL’s by specifying users, roles, passwords, and authorization
levels.Administrator access is given on a per-UI element basis.i.e. Read, write, and administer access.
same network subnet.This can use RVRD if access across subnets is required.
Administrator Users and Roles
Maintain ACL’s by specifying users, roles, passwords, and authorization
levels.Administrator access is given on a per-UI element basis.i.e. Read, write, and administer access.
If using LDAP, you cannot create/rename users or change passwords in the
Administrator GUI.
– Performed through the corporate LDAP.
– Exception: May change the password for the original admin user.
Changing the original admin password also involves using the Domain Utility
on every machine in the domain.
– Ensure that the Administration Server is running!
Members of a child role are automatically members of each parent role.
Administrator GUI.
– Performed through the corporate LDAP.
– Exception: May change the password for the original admin user.
Changing the original admin password also involves using the Domain Utility
on every machine in the domain.
– Ensure that the Administration Server is running!
Members of a child role are automatically members of each parent role.
