Confusion over usernames password for data aggregator install

[Anon Anon]

In the doco for the data aggreagator install it asks for two usernames and passwords. Page 49 / 50

The confusion:

DA username and password : the examples given are dauser & dapass - is this a new user that will be created now (so it can be anything) or is this one of the users we have setup previously (on what step was it setup)?
DA admin username and Password : under the description it says its the Linux user, under password it says its the internal db dradmin user, so which is it?

During the database create in the DR install it asked for a database password. I assumed it was using dradmin as the username during that process and your choice of password. Is this assumption incorrect?
In answer to my own question: does it just use the linux username as the username for the internal database admin user?

Doco need a lot of work in this regard. The way I would have written the manuals would be something along line of:

In DR install:

In our example we are logged on as sudouser "Bob"
When doing the create db step enter a database password. This will create an "internal" db admin user named "Bob" with the password you specified

In the DA install:

Step 10: Database user name , description this is a new general user Example: Fred (this will clearly indicated to installer this isn't Bob)
Database Admin name, description this the internal database admin user Example: Fred
Database Admin Password: description this is the internal database password you gave for the admin user, Bob, during database create. it is not the Linux user paswword that created the database

Hope you can help with my initial questions. Don't have the luxury of experimenting and am I tight deadlines

[Frank Tonjes]

Hi,

When installing the DA and you get to the part where it asks:

===============================================================================
Enter Data Repository Admin Username
------------------------------------

Data repository admin username is the database administration user account which was used to install the data repository.

Data repository admin username (DEFAULT: ): dradmin




===============================================================================
Data Repository Admin User Password
-----------------------------------

Data repository admin user password is the password specified while creating
the database after the data repository installation.

Please enter the data repository admin user password:



===============================================================================
The User is the name used when you created the linux account on the DR server.
The Password it wants here is the password you used when you created the database using the vertica /opt/vertica/bin/adminTools

This was a bit confusing in the docs.

Also, I would encourage people using IM2.0 GA to join the Polaris community. There are a lot of good posts there!

Regards.

Frank

[Anon Anon]

franktonjes wrote:

Hi,

When installing the DA and you get to the part where it asks:

===============================================================================
Enter Data Repository Admin Username
------------------------------------

Data repository admin username is the database administration user account which was used to install the data repository.

Data repository admin username (DEFAULT: ): dradmin




===============================================================================
Data Repository Admin User Password
-----------------------------------

Data repository admin user password is the password specified while creating
the database after the data repository installation.

Please enter the data repository admin user password:



===============================================================================
The User is the name used when you created the linux account on the DR server.
The Password it wants here is the password you used when you created the database using the vertica /opt/vertica/bin/adminTools

This was a bit confusing in the docs.

Also, I would encourage people using IM2.0 GA to join the Polaris community. There are a lot of good posts there!

Regards.

Frank

Thanks

In regards your statement about polaris community my comment is:
I don't agree with Restricted access communities. That defeats the purpose of having communities in the first place. The polaris community is still marked as restricted, which is stupid considering the GA nature of IM 2.0. You will find people view the polaris communtiy once it is not restricted. Its my belief useful posts should be moved here into Global IM community.

[Stuart Weenig]

In regards your statement about polaris community my comment is:

I don't agree with Restricted access communities. That defeats the purpose of having communities in the first place. The polaris community is still marked as restricted, which is stupid considering the GA nature of IM 2.0. You will find people view the polaris communtiy once it is not restricted. Its my belief useful posts should be moved here into Global IM community.
I agree with you. The difficulty is complex. First we have to convince CA to allow any content out of the Polaris community. They won't want to do this because that content might have intellectual content that CA wants to protect (which i understand to a point). If we were to succeed in doing that, they probably would only allow certain things that they approve. Then we'd have to get a resource on the CA side that would go through and approve the content. I'll bring it up at the next board meeting and request something like that of the CA guys. The worst they can do is say no.

[Anon Anon]

Thanks

[Anon Anon]

Stuart_Weenig wrote:

In regards your statement about polaris community my comment is:

I don't agree with Restricted access communities. That defeats the purpose of having communities in the first place. The polaris community is still marked as restricted, which is stupid considering the GA nature of IM 2.0. You will find people view the polaris communtiy once it is not restricted. Its my belief useful posts should be moved here into Global IM community.

I agree with you. The difficulty is complex. First we have to convince CA to allow any content out of the Polaris community. They won't want to do this because that content might have intellectual content that CA wants to protect (which i understand to a point). If we were to succeed in doing that, they probably would only allow certain things that they approve. Then we'd have to get a resource on the CA side that would go through and approve the content. I'll bring it up at the next board meeting and request something like that of the CA guys. The worst they can do is say no.

Dear all,

I agree, communities are meant to be open.

Polaris GUC is an exception and here is why. CA IM product team is using this as a place to collaborate on pre-GA development with customers and partners, and this involves sharing non-public information. It may help to think about this as a beta program. Access to this community is granted through CA Infrastructure Management Customer Validation Program and CA is welcoming all of its customers to join. If you request membership you will receive email response with instructions how to join. CA simply wants you to acknowledge the terms of this program, including NDA and non-production use restrictions. There are currently over 190 organizations that have joined this community, so it is in many ways more open than some public user communities.

Here is how the Welcome page of Polaris GUC describes it:


[color=#2705ff]
Welcome to the Polaris Global User Community (GUC), the forum for collaboration, where we share our experience and ideas to help the product team advance CA Infrastructure Management for its customers.

The name of this community, Polaris, comes from the code name for the original R&D project leading to CA Infrastructure Management 2.0.

CA Product Management Team coordinates this restricted GUC and works in close partnership with the public CA Infrastructure Management GUC board. While Polaris GUC is focused on collaboration around new development currently in progress, its sister public community is covering capabilities that have already been released to the market.

Please note, this community is restricted to customers and partners who have registered with CA Infrastructure Management Customer Validation Program. The membership is also open to all CA Technologies employees.[color]


I also totally agree we need to build more useful content about GA release of IM 2.0 here in the public community. Let's start using this GA release and share our experiences here.