Re: The DataSource with the JNDI name: contentDataSource
could not be

:-p 
If you go to each Managed Server on the console, you can see the Service tab and
then go to JDBC.  Under JDBC you can see all the pool connections.  Instead of
localhost they should be pointing to the specific hostname or ip address of the
adminserver and the pointbase port on that server (9093 by default) so the EAR
files can be correctly deployed and then the JNDI Tree will look exactly the
same on both servers.  Change all the connection pools to use the specific
hostname instead of localhost.  Hope this works for yo