O V E R V I E W Axway 5 Suite 16 October 2015

Transcription

1 O V E R V I E W Axway 5 Suite 16 October 2015

2 Copyright 2015 Axway All rights reserved. This documentation describes the following Axway software: Axway 5 Suite No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, Axway. This document, provided for informational purposes only, may be subject to significant modification. The descriptions and information in this document may not necessarily accurately represent or reflect the current or planned functions of this product. Axway may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this document. Axway does not warrant that this document is error free. Axway recognizes the rights of the holders of all trademarks used in its publications. The documentation may provide hyperlinks to third-party web sites or access to third-party content. Links and access to these sites are provided for your convenience only. Axway does not control, endorse or guarantee content found in such sites. Axway is not responsible for any content, associated links, resources or services associated with a third-party site. Axway shall not be liable for any loss or damage of any sort associated with your use of third-party content.

3 Contents Preface 5 Who should read this document 5 Axway 5 Suite documentation 5 Axway user forums 6 Training services 6 Support services 6 Accessibility 7 Screen reader support 7 Support for high contrast and accessible use of colors 7 What's new 8 1 Introduction to Axway 5 Suite 9 2 Governing the flow of data 11 Participant management 12 Identity and access management 12 Onboarding 12 Partner and community management 13 Interaction management 13 Data flow management 14 Design and development 14 Configuration and deployment 14 Monitoring and control 15 Operations management 15 Event management, monitoring, and analytics 15 Policy management 16 Axway 5 Suite Governance API 16 2 Axway 5 Suite reference solutions 17 3 API Management 19 API Management use cases 19 API management for digital business 19 API-centric application integration 20 Mobile back end 20 SOA/XML gateway 20 Identity federation 21 Axway 5 Suite Overview 3

4 API Management products 21 4 Managed File Transfer 23 Managed File Transfer use cases 23 Application-to-application transfers 24 Business-to-business Internet-based transfers 24 Human file transfers 24 Managed File Transfer products 25 5 B2B Integration 29 B2B Integration use cases 29 Business-to-business integration 29 Application integration 30 SOA/mobile integration 30 Infrastructure consolidation and modernization 30 B2B Integration products 31 6 Axway Cloud 35 Axway Cloud services 36 Axway Cloud B2B Service 36 Axway Cloud MFT Service 36 Axway Cloud API Service 37 Axway Cloud Global Traceability and Compliance Service 37 Axway Cloud in action 37 Cloud API management 37 Cloud integration brokerage 39 Cloud managed file transfer 39 Hybrid cloud 40 Appendix: Axway 5 Suite products 41 Glossary 50 Axway 5 Suite Overview 4

5 Preface This document describes Axway 5 Suite and how different products in the Suite can be combined into reference solutions. Who should read this document This document is intended for enterprise architects, chief information officers, and anyone who wants to learn about Axway 5 Suite and how it can help organizations govern the flow of data. Axway 5 Suite documentation The Axway 5 Suite documentation set includes the following guides: Axway 5 Suite Overview Provides an introduction to Axway 5 Suite and describes how the products in the suite can be used in reference solutions to solve integration problems and govern the flow of data. Axway 5 Suite Supported Platforms Lists the different operating systems, databases, browsers, and thick client platforms supported by each product in Axway 5 Suite. Axway 5 Suite Interoperability Matrix Provides product version and interoperability information for products used in an Axway 5 Suite reference solution. Axway 5 Suite Interoperability Guide Provides interoperability concepts and procedures for a subset of Axway 5 Suite products. Axway 5 Suite Upgrade Guide Provides upgrade information for a subset of Axway 5 Suite products. Axway 5 Suite reference solution guides provide conceptual information about the reference solution, and information about use cases, how the products work together, and so much more. B2B Integration Concepts Guide Financial Integration Concepts Guide Managed File Transfer Concepts Guide Accounting Integration Concepts Guide Note A complete documentation set for each product is available on Axway Sphere at Axway 5 Suite Overview 5

6 Preface Axway user forums Post comments and questions to the Axway user forum: Training services Axway offers training across the globe, including on-site instructor-led classes and self-paced online learning. For details, go to: Support services The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements. support@axway.com or visit Axway Sphere at Axway 5 Suite Overview 6

7 Accessibility Axway strives to create accessible products and documentation for users. This documentation provides the following accessibility features: Screen reader support Support for high contrast and accessible use of colors Screen reader support Alternative text is provided for images whenever necessary. The PDF documents are tagged to provide a logical reading order. Support for high contrast and accessible use of colors The documentation can be used in high-contrast mode. There is sufficient contrast between the text and the background color. The graphics have the right level of contrast and take into account the way color-blind people perceive colors. Axway 5 Suite Overview 7

8 What's new This release of the Axway 5 Suite Overview contains the following changes: Reorganization of the chapters on the reference solutions The previous release was published on 12 February Axway 5 Suite Overview 8

9 Introduction to Axway 5 Suite 1 Axway 5 Suite is the next generation of the Axway product portfolio. The product offerings enable complete lifecycle control and optimization of all information exchanged both within the enterprise and externally. Axway 5 Suite delivers a comprehensive way to manage and govern APIs and complex data flows. It enables companies to integrate across enterprise systems, B2B communities, and the cloud to enable mobile applications and provide end-to-end visibility. The ability to better govern their flows of data can help enterprises: Meet the challenges of growth, innovation, and differentiation in today's market Optimize costs through consolidation and modernization Meet compliance requirements For Axway, governing the flow of data means managing data exchanges between participants in the context of a given business interaction. It is through this context that enterprises can prioritize processing and act on the data appropriately. To govern business interactions effectively, three key questions must be answered: Who interacts with whom? When data is exchanged, the sender's or recipient s identity is typically validated and their rights checked. For example, to determine if this business document from a certain partner is expected at this time. Participant interactions must be monitored and participant information kept up to date. In particular, it is vital to manage certificates. For more information, see Participant management on page 12. What interaction is taking place? Axway 5 Suite Overview 9

10 1 Introduction to Axway 5 Suite After participants have been identified, the type of interaction that is taking place must be defined. An interaction can include not only the exchange of data, but the processing of that data. For more information, see Interaction management on page 13. Is the interaction taking place as expected? A successful interaction is one that behaves in accordance with its definition and the required constraints. To ensure an interaction is successful, enterprises enforce policies and rules, and leverage key performance indicators (KPI), alerts, dashboards, and reports. For more information, see Monitoring and control on page 15. With Axway 5 Suite, the enterprise can govern the flow of enterprise data by: Controlling identity and access management Onboarding and connecting participants to business interactions Managing the configuration and deployment of business interactions Integrating complex data flows Enforcing policies and ensuring that agreements are met Monitoring and securing business interactions The following diagram illustrates the functional architecture of Axway 5 Suite. This architecture is well-suited to the following types of projects: Replacement Replace FTP infrastructure, VANs, homegrown solutions, and obsolete products. Consolidation Consolidate B2B infrastructure or channels. Provide a file transfer or integration shared service for applications or a file transfer shared service for people. Provide single window functionality. Integration Integrate suppliers, customers, and applications; provide SOA/API mediation; integrate accounting services, EDI, cloud, and mobile. Governance Manage onboarding, data leak prevention (DLP) on human-triggered flows such as s and files, migration from one system to another, identity validation, and identity bridging. Axway 5 Suite Overview 10

11 Governing the flow of data 2 For Axway, governing the flow of data means managing the exchange of data in the context of a given business agreement. Such agreements, referred to as business interactions, consist of the exchange of business information between two parties according to a service level agreement (SLA), and may take place regardless of whether the parties are able to exchange data electronically or are only able to use paper forms. With Axway 5 Suite, business interactions are realized by data flows, which are simply the way in which interactions are conducted in an electronic fashion through the sequencing of data exchanges. Instead of focusing on a file transfer, or a business relationship, the focus is on the data flow itself: the entities that are involved, the data exchanged, and the context of the business process. Beyond just the exchange of data, Axway 5 Suite offers a set of Unified Flow Management capabilities that span the entire life of a data flow, including: Managing the lifecycle of all entities whose interactions comprise the data flow, irrespective of what those entities are people, enterprises, or applications Maintaining a repository, at both design time and runtime, that describes the end-to-end data flows between these entities Provisioning the configuration parameters of infrastructure middleware components, whatever their nature Enforcing corporate policies on all data flows to ensure compliance with business SLAs, regulatory mandates, security rules, and so on End-to-end monitoring across all data flows, including alerting, reporting, dashboard rendering, analytics, and more Easy-to-consume governance APIs to automate partner and flow creation from any application: mobile, social media, cloud, or custom web applications The following diagram shows the products that provide Unified Flow Management functions in Axway 5 Suite. Axway 5 Suite Overview 11

12 2 Governing the flow of data Participant management The interacting parties, or participants, in the business interaction may be applications, enterprises, or people, and the interaction may be within a single organization, or may span multiple organizations. Participant management functions in Axway 5 Suite include: Identity and access management Onboarding Partner and community management Identity and access management Identity and access management (IAM) is about managing the authentication and the authorization of users. The user can be a person, an application, a system, or other entity. A core IAM capability for human users is single-sign on (SSO), which enables logging in once for all services, whether onpremise, in the cloud, or via a mobile device. Central Governance is the internal enterprise IAM for the products and services it manages. It provides a central repository, identity broker, and security audit point. These enable administrators to manage security, customize policies, and connect to existing systems such as LDAP directories and SSO providers. Central Governance also provides products with the security functions necessary to exchange documents securely. Onboarding Onboarding is the end-to-end process by which participants register with Axway 5 Suite so that they may take part in interactions. Onboarding has two main phases: Enrollment The collection and review of data from participants. Typical onboarding starts with a request for information needed to interact with a participant, such as FTP communication parameters or EDI document formats required. The enrollment process includes review and approval of the participant's information before moving to the provisioning phase. Provisioning The configuration of middleware. The information collected during enrollment is used to configure Axway gateways. Tests are conducted to ensure successful deployment. In Axway 5 Suite, Application Studio is used to create applications that automate the onboarding business process. When built by Axway and delivered as a sample, these applications are called reference applications. Applications built in Application Studio can be adapted and expanded to meet various business needs. Axway 5 Suite Overview 12

13 2 Governing the flow of data Partner and community management A community is a collection of participants that interact with each other based on business agreements. For example, a community could be a group of retail stores or the set of suppliers to a manufacturer. The finance control staff spread across a large multinational corporation could also be considered a community. Communities can include internal participants, external participants, or a mix of both. In Axway 5 Suite, partners and communities are managed in the following ways: Enterprises as partners in B2B interactions are managed in each gateway Applications as participants in A2A file transfer integration are managed in Central Governance for Transfer CFT People as partners in ad hoc interactions are managed in the gateway Interaction management An interaction between participants consists of: The source participant The destination participant The type of interaction The associated interaction attributes (including SLA and other contextual information needed for the middleware system to properly complete the interaction) Interactions can be simple or complex, depending on execution constraints, the number of steps required (such as archiving, logging, encryption, sequencing), and the workflow, which might require a human decision. For example, a warehouse sends an advance ship notice to a distributor. Each step of this interaction is defined in a data flow repository so that the enterprise has a clear map of the data exchanges. This data flow repository connects flows of data directly to enterprise processes. Interaction management functions in Axway 5 Suite include: Data flow management Design and development Configuration and deployment Axway 5 Suite Overview 13

14 2 Governing the flow of data Data flow management To effectively govern flows of data, there must first be a user application describing flows and their attributes. This definition is used by the runtime engines to execute a specific data flow or business interaction. Flow information typically includes: The sending partner and the receiving application, or vice versa The business document of the interaction and its business semantics, which define the document type, such as a purchase order, and its format, such as an X.12 or EDIFACT message The related agreement, which defines what to do with this document Design and development Because an interaction can involve more than just sending data, a design and development environment is needed to build complex interactions. This environment must enable the design and deployment of maps, processes, forms, and workflows, and it must support the development of custom code, scripts, and programs. In Axway 5 Suite, the design and development products are: Mapping Services Map design and development tool for B2Bi and Integrator. Mapping Services enables the creation and test of mapping flows. After a flow is created, it can be deployed to the runtime environment where it is used to transform the messages exchanged between participants. Mapping Services comprises a development environment, Map Designer, and a simulation engine for testing in-process data maps, the DML Map Engine. API Gateway Policy Studio Policy design and development tool for API Gateway. Developers can use pre-built filters to create policies to perform API integration, transformation, governance, and security tasks. API Gateway includes an extensive library of pre-built filters to cover the most common use scenarios, third-party technologies, and standards. Application Studio A rapid development environment for building web applications that implement business processes, as well as an execution environment. These applications are typically available to business users through a web portal. Configuration and deployment Governing flows of data requires managing the configuration and deployment of middleware at two levels: Runtime All systems must be configured to deliver the expected quality of service (QoS) in terms of availability, scalability, and performance. Data flow or business interaction The description of the data flows and all their related artifacts, such as maps and processes, must be deployed to the systems, which use this configuration information at runtime to execute the exchange of data. Axway 5 Suite Overview 14

15 2 Governing the flow of data For design-time configuration, such as mapping, the design products provide deployment capabilities. Other configuration, such as tuning, is either done at runtime within the system itself, or alternatively using Central Governance for those products that it manages. Monitoring and control Monitoring and control services of Axway 5 Suite ensure that interactions take place as expected, and that appropriate warnings are provided when exceptions occur. To determine an interaction's success at operation time, it is necessary to: Have visibility over the execution of the interaction Know what policy is enforced to ensure the interaction takes place as expected, according to the definition and SLA Activate the right alerts Activate the correct rules to meet the business purpose Monitoring and control functions in Axway 5 Suite include: Operations management Event management, monitoring, and analytics Policy management Operations management Each product provides its own operations management console, but Axway 5 Suite also provides common administration features. Central Governance provides the following monitoring and administration features: Centralized operations management To start and stop products and view their logs End-to-end centralized supervision of data flows Out-of-the box alert management to track any problem linked to products or data flow processing, including a subscription mechanism for alert notifications Out-of-the-box web dashboards to get a global view of data flow activity Centralized log access Provides a single access point for all useful product logs Event management, monitoring, and analytics A key aspect of unified flow management is visibility, and within visibility, the primary objective is to capture events and to assign business relevance to them. Given an event warehouse with attributes that permit business interpretation, rules can be defined and events correlated to trigger other events or alerts. This event warehouse can be used to build and generate dashboards and reports. Axway 5 Suite Overview 15

16 2 Governing the flow of data In Axway 5 Suite, Central Governance provides event management, monitoring, and analytics. It monitors interactions at two levels: System engines Ensures engines are up and running, tuned to deliver the right performance, configured to guarantee high availability and scalability when needed, such as at peak times, or when a system failure occurs. Business interactions Provides appropriate visibility to users about what is occurring, such as alerts when a flow is interrupted or policy enforcement actions. The visibility capabilities of Central Governance are powered by a fully embedded instance of Sentinel. Sentinel is also available as a standalone product to cover cases where Central Governance is not used. Product features: Enable users to view and react to events within the network by collecting information about the products, as well as business and technical process events. Include a sophisticated set of graphics display tools that can be used to generate personalized business and technical views of principal processes. Enable users to create preprogrammed automatic responses to specified conditions. Enable auditing of actions occurring within the ecosystem. Policy management Policy management can be added to complement an existing infrastructure in order to meet compliance requirements. Compliance can take many forms: it can range from compliance with customer SLAs, to regulatory mandates, corporate security policies, enterprise directives, and so on. For policies to be operationally enforced, there must be a means to define rules that can be assessed by runtime engines, which can report discrepancies from the expected behaviors. Policies may differ from one data flow type to another. For example, policies on are different from policies on APIs. API Gateway provides policy enforcement on web services, XML flows, and API message flows. API Gateway Manager enables the management of policies created using Policy Studio. Axway 5 Suite Governance API Axway 5 Suite Governance APIs are easy-to-consume APIs that can automate partner and flow creation from any application: mobile, social media, cloud, or custom web applications. API Manager provides an API Catalog where Axway 5 Suite Governance APIs are centralized, unified, and documented. The API administrator can control developer access to the API Catalog and can set security profiles and traffic controls (quotas) to define how APIs can be consumed at runtime. API Portal allows developers to register APIs and their associated documentation and to test and subscribe to APIs. It also enables developer collaboration via forums and blogs. Axway 5 Suite Overview 16

17 2 Axway 5 Suite reference solutions Axway 5 Suite reference solutions 2 A reference solution is a set of products which, when used together, solves a specific integration problem. reference solutions may be combined to meet complex business needs. API Management API Management is the process of publishing, promoting, and managing application programming interfaces (APIs) in a secure, scalable environment. It includes the definition and documentation of the API to facilitate the consumption by application developers. The API Management reference solution consists of three core products: API Gateway The runtime gateway that proxies APIs and enforces policies on client application requests. API Manager The web-based API administration and partner management product that is layered on the API Gateway. API Portal The self-service portal that enables client application developers to browse and consume APIs for use in their applications. The API Portal enables engagement with both internal and external application developers to promote APIs for consumption. See API Management on page 19 for more details about this reference solution. Managed File Transfer The primary function of Managed File Transfer is to transport data according to a defined quality of service, such as guaranteed delivery, transfer acceleration, bandwidth control, and so on. This function is provided by Transfer CFT. Other products are added depending on the implementation architecture. For example, in a centralized implementation architecture, a gateway, such as SecureTransport, must be included, and an endpoint may be added. The security function associated with data transportation involves ensuring data confidentiality and integrity. This capability is referred to as encryption/decryption and/or signature/signature validation. In Managed File Transfer, this functionality is provided by Transfer CFT or SecureTransport. See Managed File Transfer on page 23 for more details about this reference solution. B2B Integration The B2B Integration reference solution is a combination of products used for the exchange, transformation and processing of standardized electronic business documents between the enterprise's B2B community (customers, suppliers, financial institutions, and regulatory bodies) and Axway 5 Suite Overview 17

18 2 Axway 5 Suite reference solutions internal applications, bringing visibility to transactions and increasing B2B process reliability. This reference solution is recommended when the integration project concerns a business-tobusiness integration problem where the integration flows can be standardized around a generic EDIlike integration process and where the data flow management the definition of what must be performed when receiving a document from a business partner can also be standardized around a generic data flow repository. B2Bi provides a dynamic integration process (DIP) as a standard integration process to process any data flow, as well as a data flow repository and the associated user interface to configure the data flow integration process. See B2B Integration on page 29 for more details about this reference solution. Axway 5 Suite Overview 18

19 API Management 3 The API Management reference solution enables organizations to quickly expose enterprise APIs in a secure and managed way to a wide variety of internal and external API consumers. API Management provides organizations with the ability to: Implement a policy-driven approach for security and traffic control to protect APIs Publish and promote APIs via an enterprise API Catalog, thereby controlling the API lifecycle, API virtualization, who can discover APIs, and with what policy each API can be used Allow internal or external application developers to self-register through a portal, discover APIs, and subscribe to them Perform mediation between various API formats and protocols Integrate with corporate IAM systems Leverage pre-built visibility with metrics and analytics to monitor API usage and troubleshoot issues API Management use cases The API Management reference solution addresses the following use cases: API management for digital business API-centric application integration Mobile back end SOA/XML gateway Identity federation API management for digital business Organizations face agility challenges to adapt their information systems to new digital business initiatives that require leveraging not only web applications, but also mobile, social media, and increasingly connected "things." APIs are key to enabling this agility by providing high performance, as well as a secure and universal way to expose the business to any device, business partner, and end-consumer. API Management allows organizations to quickly expose existing applications to the digital world: For the API provider, it accelerates how the enterprise can design, publish, mediate, control, and monitor APIs via the easy-to-use API Catalog. Axway 5 Suite Overview 19

20 3 API Management For the consumer, whether internal or external to the enterprise, it facilitates how application developers register and then discover, consume, and monitor the use of APIs. At runtime, it enforces security policies, performs identity bridging, mediates protocols and formats with excellent performance and high availability, and provides out-of-the-box visibility. API-centric application integration Integration needs in the digital world are evolving: Most applications provide integration services via REST or SOAP, reducing integration complexity Most new applications are cloud applications, and this raises new security challenges Most integration scenarios are executed in real time with a user expecting a response in a few hundredths of a millisecond Users interact more and more with mobile apps or connected "things" To meet these new integration challenges, lighter integration approaches have emerged, such as NoESB or LightESB. These focus on: light mediation, security, realtime integration, and ubiquitous access mechanisms via REST/JSON APIs. API Management offers an API-centric approach to application integration. With a much lower total cost of ownership (TCO) than ESBs, API Management enables the enterprise to mediate protocols and formats, perform light orchestrations with unique performance, and provide security and outof-the-box visibility. The API Catalog allows secure and easy consumption of simple APIs from the integration IDE, as well as by any developer who needs to connect to internal or cloud applications, thus removing the bottleneck of current integration approaches. Mobile back end Lines of business want to develop innovative mobile services and mobile applications that will ensure customer loyalty, reinforce their brand, and provide differentiation. The challenge to build rich mobile application is often to connect them to existing applications that support the enterprise core business processes. API Management allows an enterprise to rapidly and securely expose business applications via APIs for consumption by mobile applications built internally or by a community of mobile developers. APIs are managed in the API Catalog, and are easy to consume by mobile developers. Identity federation allows mobile application users to connect to a variety of IAM systems, and security policies enforce corporate policies. SOA/XML gateway Web Services must be exposed more and more at the edge of the enterprise for consumption by partners, cloud applications, or even connected "things." When exposing those Web Services Axway 5 Suite Overview 20

21 3 API Management through the DMZ, security, traffic control, and monitoring are critical. Implementing appropriate rules in applications or ESBs not designed for Web Services exposure will result in less agility, increased complexity, and security concerns. API Gateway in the API Management solution is a powerful SOA/XLM gateway that is designed to run securely in the DMZ. It enables the enterprise to quickly implement policies for security and traffic control with out-of-the-box visibility. SOA/XML gateway customers progressively evolve towards the full API Management solution for digital business. Identity federation Systems and protocols used to manage identities and authorizations are becoming more and more complex as organizations grow, IT systems proliferate, and more employees, partners, or endconsumers connect to cloud, mobile, and on-premise enterprise applications. This situation results in the lack of single-sign-on for users, the need to manage multiple passwords, and the inability to comply with enterprise security policies. API Gateway in the API Management solution allows an enterprise to implement SSO in heterogeneous environments and is a powerful security policy enforcement point. It integrates with corporate IAM systems, performs on-the-fly mediation between any authentication and authorization protocols, and applies security policies. API Management products The following diagram shows the required and optional products of this reference solution. API Gateway API Gateway is the runtime gateway that proxies APIs (REST/JSON or SOAP) and enforces policies on client application requests. Axway 5 Suite Overview 21

22 3 API Management API Gateway provides both security and integration: In the DMZ, it provides a first level of defense with authentication, authorization, and attack protection (from DOS attacks, injection, and malicious code, and so on). It also provides traffic control and quota management. Behind the DMZ, it acts as a service gateway or light integration solution providing service virtualization, protocol mediation, format mediation, and composition of services. API Gateway is designed to support realtime request/reply and send/forget integration scenarios. It supports a large set of communication protocols, as well as JavaScript and XSLT for mappings. It can mediate any authentication/authorization protocols and integrates with corporate IAM systems. API Gateway is delivered with an Eclipse IDE, Policy Studio, that is used to visually define policies, as well as API Gateway Analytics for pre-built visibility with web dashboards. API Manager API Manager provides web-based API administration and partner management capabilities layered on API Gateway. API Manager provides an API Catalog with life cycle management. The web UI also enables an administrator to manage partners that consume APIs and set the appropriate levels of security and quotas. API Portal The self-service API Portal enables client application developers to register, discover, and subscribe to APIs for use in mobile, social media, web, or traditional applications. API Portal enables engagement with both internal and external application developers to promote APIs for consumption. It also enables new go-to-market channels in the digital economy. Application Studio Application Studio is used to enrich API Manager and API Portal with custom workflows that automate the onboarding process of API consumers and the lifecycle of APIs. Application Studio provides visual definition of custom forms and of activities, automated or human, required in this custom workflow. Sentinel Sentinel provides visibility to enterprise data that flows through Axway 5 Suite products and other connected systems. In this reference solution, Sentinel provides: Customizable web dashboards and reports to monitor API usage (when API Gateway Analytics pre-built web dashboards do not meet the needs) A customizable event repository to track any business information from API consumers, their consumption of APIs, and the APIs themselves Axway 5 Suite Overview 22

23 Managed File Transfer 4 The Managed File Transfer reference solution is the combination of products used to transmit data securely from one or more sources to one or more destinations when the data payload is unchanged. Examples of these types of data exchanges include large CAD/CAM design files between manufacturing partners, commercial or legal documents, such as contracts or mortgage documents, and nightly product price updates from corporate headquarters to retail locations. The management of data transfer involves: Guaranteed data delivery Transfer acknowledgment, both at a technical or middleware level and at a business or application level Reporting during the transfer Ensuring that the transfer contract is fulfilled, for example, meeting time constraints Intrusion prevention Performing actions either before or after the file is transmitted Real-time visibility on file transfer activity Historically, FTP has provided businesses with an inexpensive and simple method for transferring files. However, as the number, size, and type of exchanged files expands and business needs have become more complex, FTP no longer meets most organizations' needs. Managed File Transfer provides features that FTP lacks, including but not limited to: Guaranteed delivery with file integrity checking, automatic transfer restarts, and checkpoint restarts Broadcasting and flexible end-to-end acknowledgment and routing Bandwidth control and file transfer acceleration options Parallel transfers and transfer prioritization Transfer hub capabilities enabling intermediate transfers Centralized monitoring of all transfers Managed File Transfer use cases Managed File Transfer addresses the following use cases: Application-to-application transfers Business-to-business Internet-based transfers Human transfers Axway 5 Suite Overview 23

24 4 Managed File Transfer Application-to-application transfers Application-to-application (A2A) transfers involve the exchange of files between applications that produce and consume files. It defines the way Managed File Transfer interfaces with applications at both ends of the transfer and the process step. To achieve this level of integration, data flows are defined that specify: How the source application indicates that a file is ready for transfer and how the file transfer agent picks up the file from the source application How the destination application is notified that the file has arrived and how the file transfer agent delivers the file to the destination application The level of security to apply The actions to launch on transfer success, transfer acknowledgment, and exceptions A2A transfers can be local or can take place between remote locations, such as stores, factories, sites, and data centers of a single enterprise. Business-to-business Internet-based transfers Business-to-business refers to the exchange of B2B business documents, such as purchase orders, payments, invoices, shipment notices, CAD files, and claims. In Managed File Transfer, the role of the B2B gateway is to: Handle all levels of security required to exchange data through a public network Handle compliance with all standard protocols required to communicate with any partners Manage the routing of flows between the internal application and the partners The key difference between this type of data flow and business-to-business integration is that there is no change to the data payload. A typical B2B exchange in a Managed File Transfer reference solution involves integration with a partner's internal system or application. The incoming file is received in the DMZ, then sent to the corporate network gateway, which then routes it to the enterprise's back-end application. Alternatively, the outgoing file is moved from the enterprise's business application to the B2B gateway, which then sends it through the DMZ to the external partner. Human file transfers Human-to-human and human-to-system (H2*) transfers involve a person in an ad hoc manner. Typical exchanges involve people who need to work together, or people who need to download or upload files consumed or produced by enterprise information system applications. H2* data flows have some unique characteristics: They are initiated or acted upon by people through a user interface, such as a mail client, web portal, or within a business application. As a result, when people upload or download a file, they Axway 5 Suite Overview 24

25 4 Managed File Transfer want to know in real time if the file is transferring correctly and when the transfer is finished. This requires constant reporting about the file transfer's progress by the gateway back to the user interface. Because the files are manipulated by people, they run the risk of getting corrupted, getting infected by a virus, or being inadvertently transferred to a competitor. As a result, these file transfers require tighter scrutiny. Corporate policies related to anti-virus, anti-spam, edge protection, data loss prevention, and data leak protection must be enforced to protect the enterprise. Managed File Transfer products The following diagram shows the required and optional products of this reference solution. The following descriptions provide information on the product roles within the reference solution. Transfer CFT Transfer CFT is a transfer exchange system that enables reliable and secure internal file transfers between applications. Transfer CFT isolates the logical and business characteristics of a flow from its physical characteristics. Transfer CFT can be used in a distributed, centralized, or combination implementation. When an exchange with an external partner is required, Transfer CFT transfers the file to a gateway, which assumes responsibility for transmitting the file outside the enterprise firewall. Axway 5 Suite Overview 25

26 4 Managed File Transfer API Gateway API Gateway is a comprehensive platform for managing, delivering, and securing enterprise APIs, applications, and consumers. In this reference solution, it can be used to manage web services and APIs exposed by Transfer CFT, SecureTransport, or third-party products. API Manager API Manager provides web-based API administration and partner management capabilities layered on API Gateway. API Manager provides an API Catalog with life cycle management. The web UI also enables an administrator to manage partners that consume APIs and set the appropriate levels of security and quotas. API Portal API Portal is a self-service portal that enables client application developers to browse and consume APIs for use in their applications, whether they be mobile, social media, web, or traditional applications. API Portal enables engagement with both internal and external application developers to promote APIs for consumption. It enables new go to market channels in the digital economy. Application Studio Application Studio is a rapid development environment for building web applications that implement business processes. It uses a model-driven, visual development approach, and applications developed in Application Studio can be easily branded to meet customer needs. These applications are typically available to business and technical users through a web portal. Application Studio is also a scalable application execution environment. It can be deployed on premise or in a private cloud for both development and execution. Reference applications are high quality samples that address common use cases, such as partner onboarding, and can be adapted and extended to meet specific business needs. In this reference solution, Application Studio may be used to build applications for onboarding of participants to SecureTransport. These onboarding applications can call SecureTransport's native REST APIs, either directly or via an instance of API Gateway, to provision partner definitions as part of a customer-specific workflow. Central Governance Central Governance provides a set of services for Axway 5 Suite products. For all products, Central Governance provides IAM and visibility services through embedded editions of PassPort and Sentinel. Global management of user identity and rights, providing a central control point for security enforcement End-to-end centralized supervision of data flows, consistent with definitions in the repository Axway 5 Suite Overview 26

27 4 Managed File Transfer Out-of-the-box web dashboards to get a global view of data flow activity, as well as the ability to create custom dashboards For Transfer CFT, Central Governance also provides product configuration, flow definition, and deployment services. Global data flow repository, providing end-to-end data flow definitions, from business application to infrastructure level Automatic discovery of products to be managed Centralized management of product configuration and deployment for highly distributed environments through mass processing capabilities that include groups and configuration policies Centralized day-to-day operations management: to start and stop products and to view their logs Out-of-the box alert management to track any problem linked to products or data flow processing, including a subscription mechanism for alert notifications Communication gateways In this reference solution, a communication gateway is responsible for securely transmitting files between internal applications and partners. Axway 5 Suite has several high-performance gateways, each with its own differentiated characteristics. The choice of gateway depends on the project requirements. SecureTransport Multi-pattern gateway with ad hoc capabilities that supports both system-tosystem data transfers and person-to-person transactions Gateway System-to-system gateway that supports financial service industry (FSI) protocols such as SWIFT Composer Composer is an integrated development environment (IDE) that enables the user to configure visibility services. DMZ proxies Two DMZ proxies are available in this reference solution. Both are used to protect data exchanges between a communication gateway and external participants. SecureTransport Edge is part of and is used with SecureTransport. Secure Relay is used with Gateway. Axway 5 Suite Overview 27

28 4 Managed File Transfer Endpoints Endpoints are lightweight products that participants use when they cannot invest in a complete exchange solution. They enable participants to connect and interact with the hub. Secure Client is the endpoint in this reference solution. TrustedFile TrustedFile encodes and decodes files in S/MIME, CMS, OpenPGP, XML Signature, XML Encryption, and XAdES (BES and EPES) format. These standards secure data at rest, independently of the data communication method. TrustedFile security functions are based on the following security techniques: symmetrical and asymmetrical encryption, digests, signatures, certificates, acknowledgements, and proofs. TrustedFile provides off-line security operations (encryption, decryption, signature, signature validation). TrustedFile is a standalone product, but is also embedded in Transfer CFT. Axway 5 Suite Overview 28

29 B2B Integration 5 The B2B Integration reference solution is a combination of products used for the exchange, transformation and processing of standardized electronic business documents between the enterprise's B2B community (customers, suppliers, financial institutions, and regulatory bodies) and internal applications, bringing visibility to transactions and increasing B2B process reliability. This reference solution is recommended when the integration project concerns a business-tobusiness integration problem where the integration flows can be standardized around a generic EDIlike integration process and where the data flow management the definition of what must be performed when receiving a document from a business partner can also be standardized around a generic data flow repository. B2Bi provides a dynamic integration process (DIP) as a standard integration process to process any data flow, as well as a data flow repository and the associated user interface to configure the data flow integration process. B2B Integration use cases B2B Integration addresses the following use cases: Business-to-business integration Application integration SOA/mobile integration Infrastructure consolidation and modernization Business-to-business integration Business-to-business integration refers to the handling of B2B business documents, such as those used in the order-to-cash or the purchase-to-pay scenarios. These documents include purchase orders, payments, and invoices. B2B integration can take multiple forms but is not limited to: Extension of an ERP or of a business application Extend an existing business application so that it can exchange business documents with other enterprises. B2B Integration solves this integration problem by providing a logical central connection point though which these integration data flows can be connected, secured, managed, and monitored. B2B Integration provides application connectivity, data format translation, and simple SOA mediation. Partner-to-partner integration (service provider) Support the trading and integration between partners facilitated by service providers. B2B Integration provides the backbone for transfer and transformation services between the participants in the service provider's community. It provides a logical central exchange point with a wide range of support for protocols and formats through which these partners' flows can be connected, secured, managed, and monitored. Axway 5 Suite Overview 29

30 5 B2B Integration Customer/partner integration Enable the enterprise to communicate securely with customers and partners in a variety of network environments. B2B Integration uses a hub-and-spoke distribution model to solve this integration problem by providing a system of connections in which all traffic moves along spokes connected to the hub at the center. Endpoints act as the spokes, connecting securely and directly to the B2Bi Server. Supplier portal (WebEDI) Enable partners who lack the resources to purchase B2B technology to interact with the ecosystem by offering a portal application that provides standard EDI business processes allowing these partners to exchange business documents. This type of portal is also referred to as a self-service portal. Application integration When an enterprise integrates its many varied applications in a disorganized manner, without following a structured Enterprise Application Integration (EAI) strategy, the number of point-topoint connections grows quickly and unmanageably. The result is a complex structure of application dependencies that is difficult to maintain. B2B Integration solves this spaghetti integration problem by providing a logical central connection point (hub) through which these integration data flows can be connected, secured, managed, and monitored. SOA/mobile integration B2B Integration supports complex flow integration patterns via APIs (REST or SOAP) in combination with API Gateway. Incoming API requests are sent to B2Bi triggering the execution of a defined and reusable service definition. If necessary, the result from the transformation is sent back to API Gateway to be used as a response for the original incoming request. In such cases, API Gateway provides key services such as throttling, caching, and full security. Infrastructure consolidation and modernization As value-chain complexity has increased in the last few decades, the volume of documents exchanged electronically in various formats has grown. This has resulted in an increase in the number of systems used to handle integration exchanges. Mid- to large-size companies typically use several systems to support multiple document standards and protocols. The larger the organization, the greater the number of systems in place, and the higher the cost and complexity to maintain them. A single reference solution can replace multiple incompatible systems, and handle all transactions with suppliers, customers, and other trading partners. This simplifies the corporate application landscape and reduces cost, as well as operational and compliance risk. Infrastructure consolidation and modernization is a generic use case of a hybrid nature.the consolidation and modernization can apply to products in one or more areas including those mentioned in the other use cases, such as application integration, business integration, and so on. Axway 5 Suite Overview 30

31 5 B2B Integration B2B Integration products The following diagram shows the required and optional products of this reference solution. The following descriptions provide information on the product roles within the reference solution. B2Bi B2Bi is the central product of the reference solution. It is the runtime engine for transport and document processing. It provides a wide variety of communication and transformation services for exchanging standardized electronic business documents. These services include: Standard B2B protocol support Translation and transformation Trading partner management End-to-end visibility PKI infrastructure for certificate management Administration and operations B2Bi owns the definition of the B2B integration data flows, which includes all the information required to execute the data flow management process for a particular document. The information in the data flow definition includes: The sending partner and the receiving application, or vice-versa The business document of the interaction and its business semantics, which defines the Axway 5 Suite Overview 31

32 5 B2B Integration document type, such as a purchase order, and its format, such as an X.12 or EDIFACT message The related agreement, which defines what to do with this document B2Bi is pre-loaded with a dynamic integration process, which provides standard stages: parse, detect, split, map, envelope, and so on. These standard process steps are overridden during runtime operation using the configuration parameters read from the data flow registry/repository. In this way, a standard process may be configured to support a variety of similar, but different configurations without heavy customization. API Gateway API Gateway provides an API interface to the B2Bi functionality and, when used with Application Studio applications, plays a vital role in the onboarding of new participants in B2Bi. Additionally, API Gateway can provide a policy layer for B2Bi, enabling the user to define policies, resulting in more control, visibility, and security. In B2B Integration, API Gateway can also be used to: Secure inbound flows Process B2B API flows Better integrate with back-end systems API Manager API Manager provides web-based API administration and partner management capabilities layered on API Gateway. API Manager provides an API Catalog with life cycle management. The web UI also enables an administrator to manage partners that consume APIs and set the appropriate levels of security and quotas. API Portal API Portal is a self-service portal that enables client application developers to browse and consume APIs for use in their applications, whether they be mobile, social media, web, or traditional applications. API Portal enables engagement with both internal and external application developers to promote APIs for consumption. It enables new go to market channels in the digital economy. Application Studio Application Studio is a rapid development environment for building web applications that implement business processes. It uses a model-driven, visual development approach, and applications developed in Application Studio can be easily branded to meet customer needs. These applications are typically available to business and technical users through a web portal. Application Studio is also a scalable application execution environment. It can be deployed on premise or in a private cloud for both development and execution. Reference applications are high quality samples that address common use cases, such as partner onboarding, and can be adapted and extended to meet specific business needs. Axway 5 Suite Overview 32

33 5 B2B Integration Central Governance If Transfer CFT is part of a B2B Integration solution, the Sentinel and PassPort editions embedded in Central Governance should be used to provide IAM and Visibility services. Otherwise, the use of the standalone editions of Sentinel and PassPort is recommended. For a description of the features, see Central Governance. Composer Composer is an integrated development environment (IDE) that enables the user to configure visibility services. Mapping Services Mapping Services provides an environment for developing and deploying message-transformation components. Mapping Services is used to create and test message-processing sequences (map flows) that can contain one or more maps. After validation of a map flow, it is sent to the runtime environment, where it can be used to transform the messages exchanged between participant applications and trading partners. PassPort PassPort provides identity and access management services, as well as SSO and user access audit functionality. Although most products have their own user administration in stand-alone mode, PassPort can provide centralized user administration for all products. When a user attempts an action requiring authorization, such as logging on, the product sends a request to PassPort through its API. PassPort approves or denies the request and responds, with the result that the user can either perform the action, or is blocked. Secure Relay Secure Relay is used as a DMZ proxy in this reference solution. It is used to protect data exchanges between the gateway and external partners. Sentinel Sentinel provides visibility to enterprise data that flows through Axway 5 Suite products and other connected systems. In this reference solution, Sentinel provides visibility in the following areas: Message-processing lifecycle information System status information Axway 5 Suite Overview 33

34 5 B2B Integration Business visibility: For example, the mapping flows can extract business data (order item count and price, invoice total amount, fees, and so on) from the payload and send them to Sentinel where business indicators can be displayed to the user. Axway 5 Suite Overview 34

35 Axway Cloud 6 Axway Cloud comprises the cloud managed service offerings within Axway 5 Suite. Axway Cloud services are designed to complement the traditional software products of the Suite, which are deployed by enterprises in environments they directly control: on premise, in virtual environments, in private clouds, under third party hosting, and so on. Enterprises can choose to use Axway Cloud services on their own, or in a hybrid fashion, combining cloud with on-premise products in a natural way. Most Axway Cloud offerings are powered by products from the Axway portfolio, so their capabilities are familiar to existing users of Axway software. Some Axway Cloud services are powered by thirdparty service providers, but are brokered through Axway Cloud for use as part of the Suite. This approach extends the reach of Axway Cloud to areas where cloud-based services are natural, while retaining seamless hybridization across the Suite. The Axway Cloud Services model relieves enterprises of the need to install, configure, operate, and maintain the infrastructure and software components supporting the solution. Browser-based management and end-user interfaces provide immediate access to the product capabilities. Some enterprises may also want to augment the cloud service with Axway Cloud Managed Services. The Cloud Managed Services team assumes day-to-day application administration, participant management, and other routine product support activities, freeing the enterprise to focus on the business. Axway Cloud Managed Services can also be used to operate on-premise and hybrid implementations. Axway 5 Suite Overview 35

36 6 Axway Cloud Axway Cloud services This section describes the Axway Cloud services. Axway Cloud B2B Service Axway Cloud B2B Service, a cloud-based integration broker, provides B2B integration services. It provides security services, protocol mediation, data mapping, and application integration services. These services are extended with: dashboard and visibility interfaces; community management and on boarding services; and brokering of cloud APIs to provide interfaces to mobile devices. In hybrid implementations, connections between Axway Cloud and the on-ground environment can be implemented using API Gateway, Transfer CFT, a virtual private network (VPN), or any of the integration protocols supported by the Axway Cloud B2B Service. Axway Cloud MFT Service Axway Cloud also includes Axway Cloud MFT Service, a managed file transfer service. Axway Cloud MFT Service provides file integration services, both automated and interactive, that connect people, applications, and devices to each other. Axway Cloud MFT Service includes visibility and file tracking services, as well as security services like PGP (Pretty Good Privacy). Axway 5 Suite Overview 36

37 6 Axway Cloud Axway Cloud API Service Axway Cloud API Service (Cloud API) provides a cloud-based API gateway with elastic scaling to securely integrate and provide consistent policy across SaaS, social, mobile, SOA, and B2B access points to enterprise applications. Cloud API can be the single front-end interface to your enterprise APIs, or it can broker external APIs, applying elastic scaling, usage reporting, analytics, throttling, and full management of the API lifecycle as a cloud service. Cloud API comes packaged with a wide set of common enterprise IAM, cloud, and social filters and tokens, LDAP, Active Directory, SAML, OAuth, OpenID, and other standards to bridge between identity requesters and providers. Custom filters can also be designed for non-packaged application integration, or other unique security policies. Axway Cloud Global Traceability and Compliance Service Axway Cloud Global Traceability and Compliance Service is a tiered cloud offering targeted specifically at pharmaceutical manufacturers and third-party logistics (3PL) companies that need to comply with serialization and pedigree regulations. A company's applications are connected securely to the event acquisition API of the cloud service for tracking supply chain events in a standard EPCIS repository. The cloud service creates and stores the required pedigree for all products shipped up and down the supply chain and transmits with associated certificate and chain-of-custody to distribution partners via a robust embedded B2B gateway. Based on Axway s Track and Trace solution, the cloud service shields customers from the underlying application setup and operation, and offers a focused self-service and easy-to-integrate manufacturing line and edge interface with serial number generation based on open standard web services and business protocols. Axway manages the B2B gateway portion and associated partner management. Users of the service are provided access to search and monitor events and pedigrees through a web browser interface, and an API to retrieve pedigrees in PDF format for audit purposes. The Axway Cloud Global Traceability and Compliance Service is designed to provide an entry-level configuration for mid-market companies, and tiered configurations to support business growth. Axway Cloud in action The following examples demonstrate how Axway Cloud services can more effectively solve integration problems and provide more business value than a pure on-premise solution. Cloud API management This example illustrates the use of Axway Cloud API Service as the front end to an enterprise s internal services, exposing a secure, scalable API that is the enabler of a mobile application partner program. Axway 5 Suite Overview 37

38 6 Axway Cloud A retail pharmacy chain provides digital services, such as photo printing and prescription management, which it wants to expose externally to open new business channels, increase revenue streams, and reach new consumers who don t normally patronize their stores. Rather than undertake in-house mobile development, the company prefers to enable business partners and trusted mobile app developers to create new interfaces for them. The company would receive a portion of the revenues and monetize the apps produced. However, the company's internal applications are not mobile ready, and their IT team doesn t have the security expertise or the scalability to support any type of mobile campaign. Axway Cloud API Service provides an ideal front-end solution. It connects through VPN and secure web services on the back end, and converts and exposes these services as REST APIs to the front end (the mobile and cloud application side). Through this gateway, security and throttling policies are consistently applied, ensuring that all traffic is authorized and does not overwhelm the back-end systems. Internal management interfaces allow the company to publish new APIs as these services grow and evolve. An external portal allows business partners to register and learn about the company's API offerings. All these capabilities are available through a highly scalable and elastic cloud service that adjusts to the waves and troughs of business activity through the APIs. Axway 5 Suite Overview 38

39 6 Axway Cloud Cloud integration brokerage This example illustrates how Axway Cloud B2B Service provides integration services between onpremise business applications and partner applications. An expanding beverage distributor has outgrown its legacy technologies used to integrate with suppliers and customers. The enterprise is also incurring costs and risks with missed electronic exchanges, which negatively affect business. They recognize that infrastructure management is not their core competency and want to leverage the expertise, robustness, and flexibility of an Axway cloud offering. Axway Cloud B2B Service connects their internal applications to various communities via appropriate business protocols, allows flexibility in partnership interactions, and provides new opportunities for business-process automation. By using Mapping Services, the company is able to support any format in order to connect disparate applications or support nonstandard needs from certain key customers. Cloud managed file transfer This example illustrates how Axway Cloud MFT Service can rapidly enable secure and managed file transmission across a widely distributed global network. A global provider of supply chain logistics services needs to exchange digital files securely with business partners around the world at customs checkpoints. New locations must be added to the network quickly, and from regions all over the world that may have different levels of IT and security Axway 5 Suite Overview 39

40 6 Axway Cloud capabilities. The corporate side of the company must receive these files securely and reliably and centrally monitor all transmissions. Axway Cloud MFT Service enables this electronic exchange of documents in a way that is secured, tracked, and stored on reliable cloud storage provided by Amazon. The corporate business users access the files from the cloud using the Secure Client endpoint. Files are purged from cloud storage after a specified number of days. The service is fully managed by Axway, and corporate management receives regular activity reports for tracking and billing. Hybrid cloud This example illustrates how cloud-based community management services complement an onpremise integration environment. A healthcare organization uses Axway B2Bi to provide a secure exchange platform to its business units. This platform enables the organization to enforce HIPAA regulations and security best practices and centrally monitor exchanges company-wide, while phasing out existing FTP systems. This platform is very effective in meeting their business goals. Yet, because this company grows frequently by acquisition and interacts with many external partners, it faces the challenge of managing new and ever-changing data transfer requirements with tens of thousands of participants, both internal and external. Application Studio cloud services provide the organization with a self-service portal to standardize and automate the management of their extensive partner network, and at the same time reduce errors and maintenance costs. These cloud services are integrated with B2Bi and API Gateway. Axway 5 Suite Overview 40