Revision as of 01:53, 5 November 2015

1 Overview

Retrieving data from various sources is the first step in a MetaData process. There are various options to how data can be brought into bxp. This article discusses the various options and approaches used.

N.B. Please note that this list is for indication purposes only and other connectors and integrations are continuously developed.

2 Push or Pull

The first decision on the data is whether a primary approach of push or pull is going to be used.

• Push: An external system pushes the data into bxp
• Pull: bxp must to another system and pull out the data

There are different times where these approaches are appropriate the primary considerations are security.

2.1 Pull

2.1.1 Primary security considerations - Connectivity

There are different levels of encryption and security considered when considering the Push or Pull.

If security of the remote client is paramount, all solutions suggested will be Push. This allows the client to dictate the hows and when bxp gets its data.

If security measures are in place, bxp can log in to retrieve data. This is usually through one of three methods.

• SFTP file retrieval
• Email attachment retrieval
• API interaction

Where API interaction is required, the API documentation is supplied by the client and a connector is appropriately built. SOAP, XML, JSON, etc are all supported. For security, current client integration examples are not listed here.

bxp to retain its high availability cannot VPN into client infrastructures. VPN connections and their maintenance across the nTier of our web platform is unsustainable and can be easily replaced with PUSH sFTP solutions. Which All n One can provide support on.

2.1.2 Primary security considerations - Content Encryption

The next consideration is to what level is the data encrypted. Numerous options exist with the most common being AES256 encryption on zip files being transferred. Solutions also exist for PGP based encryption approaches. A case by case review is adopted to facilitate client capabilities and requirements.

2.2 Push

This is more generally used when security and automation capability is not yet at an automated enough level. bxp provides a number of mechanisms for data to be pushed into it.

• bxp API: An API for direct data injection Scenario_-_bxp_as_a_secure_Website_Data_Store
• sFTP: bxp can provide clients with an on demand sFTP account structure.
• The primary bxp interface: Over HTTPS a user can upload files into a bxp system
• All n One email account: All n One can provide an @allnone.ie email address external to the clients environment which bxp can retrieve emails and attachments from

3 Conclusion

All n One can facilitate a variety of retrieval and encryption approaches. The primary question becomes what is the most economic and practical approach to data transfer. This will depend primarily on the client capability and maturity. All n One's development teams would be delighted to discuss how we can help you securely get your data into bxp. Contact us on support@bxpsoftware.com to see how we can help you get your data into bxp.