Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

ra298

1 Rookie

 • 

18 Posts

8931

February 23rd, 2012 09:00

Trying to understand the PEA file

2 Centera's in different locations. One replicating to the other

We have a application using the Centera to store documents. The application is using a merged PEA file generated from both Centera's. I am trying to understand the relationship between the application and replication. Is replication using the same PEA file as the application?

I disabled delete replication and somehow this stopped replication all together. I do have support engaged but having a hard time with understanding the usage of the PEA file.

Thanks

Satish_Kutty

216 Posts

February 27th, 2012 02:00

Hi,

    A Pool Entry Authorization (PEA) file, generated while creating or updating an access profile, is a clear-text, XML-formatted, non-encrypted file which can be used by system administrators to communicate and distribute authentication credentials to application administrators. A PEA file is optional for profiles with non-encoded secrets (created using the File and Prompt options) but is mandatory for profiles with base-64 encoded secrets (created with the Generate option).

A PEA file contains the following information:

  • The element provides credentials which are not cluster specific. These credentials were originally designed as a fallback mechanism but are not being used in the current SDK. 
  • The element provides a cluster-specific set of credentials which only apply for the cluster on which the file was generated. The type tag is always set to cluster, the id tag specifies the unique ID of the cluster for which the profile can be used, and the name tag displays the profile name.
  • The elements contain the actual secret which was generated by CentraStar or entered by the system administrator for the profile. The id tag is always set to csp1.secret and the enc tag is always base64.

Regards

Satish.N.Kutty

East_TN_EMC

29 Posts

May 2nd, 2012 06:00

Hello,

The application would have one PEA file that has the merged authenication information from both the source and target Centera clusters for the profile that the application is writing to.

The replication subsystem would have a different PEA file containing the authentication information for the replication profile on the target cluster (typically configured as "repl" or "replication" profile).  You can determine which profile replication is using by issuing the "show replication detail" commands.

There is no relation between the application PEA file and the PEA file that replication would use to replicate the data.

When replication stopped after you changed the replicate-deletes option, what message did it give when it stopped?  That would be a good starting-point to determine what is happening.

Hope this helps.

Was this post helpful?

View All

No Events found!

Top