G-Invoicing Keystore? Truststore? Huh?

Hi,

In order to successfully integrate EBS with the US Treasury G-Invoicing application using REST calls, proper digital certificate and SSL/TLS setup are required between the Oracle EBS and Treasury G-Invoicing application.

The Oracle EBS G-Invoicing integration solution requires configuration of the following:

Truststore Path (& Password)

Keystore Path (& Password)

Without much background on these concepts and minimal documentation available, we struggled for a bit figuring out what exactly these should represent and were unable to have much success with the EBS REST call authentication at first.  We had questions including: Is the keystore we created with the Treasury G-Invoicing cert the "Keystore", or the "Truststore"? Why is a separate "Keystore" and "Truststore" needed?  FRB's certificate/system-id doc mentions a keystore.p12, but is EBS looking for a .jks and/or .pfx (PKCS12) format? After a bunch of googling, coordinating with others having similar issues, lots of trial and error, consulting w/some other