Unicenter ca-xcom data transport for windows

Ensure you have the correct version of XCOM. If you are installing it on a desktop you need the professional edition. XCOM must be installed via the console or terminal services using the console switch i. XCOM will not install via a standard terminal server window. If the installation process does not start automatically, start it by running the 'setup.

Step 5: Ensure the 'Anyone who uses this computer all users ' radio button is selected, and click 'Next'. If a different installation directory is chosen then record it for later use. Once the installation directory has been set, click 'Next'. Step When the installation is complete, select the 'No, I will restart my computer later' radio button and click 'Finish'.

This is a system level account i. Windows or Unix account. Once GnuPG has been installed you need to generate a public key and private key. You will give the public key to partners you will exchange files with. Both keys will be kept in your private and public key rings. Your private key ring will only contain your private key. Your public key ring will contain your own public key and the public keys of any other business partners such as Westpac who will provide your with their public key. Note that the pubring and secring are stored in the following locations.

GPG2 knows these locations via the registry. Once the public and private keys are generated you need to export your public key and provide it to Westpac or any other business partner you will be exchanging PGP encrypted data with. Westpac will provide you with their public key to import into your public key ring. This is Qvalent's public key. This is a 2-step process. You firstly import the key then you digitally sign it to indicate that you trust the key. To verify the key was added to the keystore correctly, list the public keys in the public keyring.

You should verify at this step that the Qvalent key is valid and that the key you are signing with is the key generated in the previous section. If you are confident of this, enter Y to sign the key. Before doing this please confirm the following:. Then you can not establish a connection so consult with your network personnel. This could mean one of a couple of things.

If you are connecting to the TEST environment ssiw. Westpac has no firewall restrictions on connections from the internet to its test environment. If you are connecting to production, then you must provide Westpac with your production IP address as you must open your own firewall and Westpac need to open there's as well.

The IP address must be provided 5 days in advance before the go live date. From a batch file you should always check the error level after the xcom call to ensure that the transfer was successful. Sample pseudo code for the batch file would be:. This will be due to either a network issue, or the external system's XCOM client service not running. To debug the issue edit the xcom.

This will cause the DOS box to stay on the screen when the batch file runs when a file is received. Log into the server using the console and you will be able to see what is causing the error in your batch file. Try logging into the server using the just created XCOM user to ensure that there was no typo's with the username or password. If you do not use this you will receive an "error setting the remote user id" from Westpac as your xcom server will be passing its domain name with its user name and Westpac will reject it.

This is a compatibility issue between GPG2 and eBusiness server and can be ignored. The important line to note is "Good signature from x01" This tells you that the file has not been tampered with.

This will automatically answer 'Yes' for most questions GPG2 prompts for i. Westpac always encrypts files that it is sending to customers with both the customers public key and Westpac's public key.

This allows a customer that is having difficulty decrypting a file it may have become corrupted in transit to send it back to Westpac to test decrypting it. When GPG2 encrypts a file it generates a random session key and uses this random key to do the actual encryption.

It then encrypts this session key with the recipient's public key and appends this data to the encrypted file. As Westpac always encrypts an outbound file with its own public key, the session key is also encrypted with Westpac's public key and this data is also added to the encrypted file.

So encrypting with additional public keys only makes the file slightly larger. By doing this either the recipient or Westpac can use their private key to decrypt the session key which inturn is used to decrypt the file. The information contained in this publication is provided for learning purposes only and is subject to change.

Revisions may be issued from time to time that encompass changes or additions to this module. This is a guide only and it is not comprehensive. It does not impinge on or overrule any formal arrangement you may enter into with the Bank. The Bank and its officers shall not have any liability for any losses of any kind incurred in connection with any action, inaction or decision taken in reliance on the information herein or for any inaccuracies, errors or omissions.

Sign in. The intended audience of this document is: Server administrators who wish to use the provided command line scripts, and Software developers who wish to implement this messaging protocol in their software. Security All files transferred must be encrypted and digitally signed between Westpac and the customer's site.

Initial key exchange To set up the XCOM transfer the customer will: Provide Westpac with the PGP public key used to verify the digital signature of the data file that is transferred between the customer and Westpac. Banking policy mandates that any file written to a hard drive in an untrusted zone a server connected to an external network must be PGP encrypted and digitally signed. Provide a username and password for Westpac to log onto the customerr XCOM server if Westpac is required to push files back to the customer.

Provide the customer with Westpac's PGP public key. This would be used by the customer to encrypt a file that is sent to Westpac this customer signs the file with their private key. Agree with the customer on the file naming convention and directory paths.

Pushing a file to Wesptac To push a file to Westpac the sending site carries out the following steps: Encrypts the data using Westpac's public key and signs the encrypted data with it's private key. The file is then given to the XCOM client for transmission. Westpac detects the arrival of the file. The digital signature is checked against the customers previously supplied PGP public key. Once the security aspects of the file have been verified, it is then processed.

Once the file has been processed, it will be deleted from the incoming directory on Westpac's XCOM server. Westpac pushing a file to the customer For Westpac to push a file to the customer the following steps are carried out: Westpac encrypts the data using the customer's public key and signs the encrypted data with it's private key. Once it is connected the file is transferred to the customer's XCOM server into the agreed directory. The customer detects the arrival of the file.

The digital signature is checked against Westpac's previously supplied PGP public key. If this matches then the file is decrypted using the customer's private PGP key.

Jun 28, by Jay Zelnick. Jun 08, by Lynn Williams Original post by pawan modi. Jun 08, by Beverly Perez Original post by pawan modi. Jun 07, by Lenn Thompson. Jun 01, by Joseph Reilly. Mar 25, by Mark Hunter. Mar 05, by Jay Zelnick. Mar 04, by Joseph Reilly. Feb 18, by Nancy Lipp. Feb 01, by Lenn Thompson. Dec 01, by JeanSebastien Petit. Nov 18, by Angelica Giraldo. Nov 02, by Joseph Reilly. Oct 12, by Jay Zelnick. Sep 15, by Jay Zelnick. Jul 21, by Chandrasekaran Venkataraman. Jul 08, by Mark Hunter.

Jun 09, by Joseph Reilly. Jan 16, by MaxField. Dec 31, by Shivaramakrishna Chakravarthula. Nov 18, by Joseph Reilly Original post by rstil. Oct 07, by James Craig. Jun 20, by Lenn Thompson. Jun 18, by Lenn Thompson. Jun 12, by Steve Marsden.

Feb 11, by vetriii. Nov 15, by benamiy. Nov 14, by benamiy. Nov 11, by benamiy. Nov 06, by Nancy Lipp. Sep 27, by Shivaramakrishna Chakravarthula. Sep 20, by Legacy User. Sep 20, by Legacy User Original post by Lean Sep 19, by Lean Mar 09, by Legacy User. Feb 02, by Nancy Lipp Original post by haopi Dec 29, by Legacy User. Dec 20, by Beverly Perez Original post by Norma.

Dec 03, by benamiy. Nov 16, by Legacy User. Sep 29, by Shivaramakrishna Chakravarthula. Aug 02, by Shivaramakrishna Chakravarthula. Jun 30, by Nancy Lipp. Jun 30, by Legacy User. Jun 08, by Legacy User. Apr 05, by Nancy Lipp Original post by steveschwartz. Feb 07, by Nancy Lipp. Dec 27, by Legacy User. Dec 15, by Legacy User. Nov 24, by Shivaramakrishna Chakravarthula.

Nov 17, by Nancy Lipp. Sep 09, by Legacy User. Jul 22, by Machhindra. Jul 14, by Beverly Perez. Jul 08, by Kenneth Vollmer. Jul 07, by Legacy User. May 26, by Nancy Lipp. May 20, by Legacy User. May 12, by Legacy User. Dec 09, by Machhindra.