Contact Office: One Microsoft Way, Redmond, WA 98052-7329, US Tel: +1 425 882 8080 Other Offices: Offices in more than 100 countries Website:
www.microsoft.com Twitter: @Microsoft Contact: Colin Kerr (worldwide industry solutions manager for core banking & payments) Email:
colin.kerr@
microsoft.com Founded: 1975 Ownership: Listed on Nasdaq Number of staff: 99,000 – number working on payments-related solutions not specified Number of clients: Microsoft claims 12,500 BizTalk clients Principal partners: A broad range of product and services providers Payments products: Microsoft BizTalk Server, BizTalk Accelerator for Swift Categories: Messaging
MQ Series. When implemented with value-added services built on top, it provides a stack that meets the requirements of banking customers.
In the context of the industry-wide trend towards SOA, the modelling of processes – often referred to as ‘orchestration’ – is receiving a lot of attention and Microsoft is one of the heavyweights seeking to forge a place in this arena with BizTalk. In reality, when Microsoft talks about orchestration today, it is still primarily concerned with connecting to legacy systems through adaptors, and then transforming and distributing the resulting messages to connect these legacy systems with delivery channels and front-end systems, across different technology platforms. However, BizTalk has had capabilities added that reflect
a shift in emphasis from pure EAI to a ‘business user’ or, in Microsoft parlance, ‘information worker’ centric approach. Those capabilities include the Business Rules Engine (BRE), which enables rules-based routing of messages, and the Business Activity Monitoring (BAM) function, which enables business users to see what is happening in terms of typical performance indicators: the BAM framework in BizTalk Server provides the ability to open a window into running business processes and message flows. BAM provides business analysts direct visibility into transactions and messages – an area that has traditionally been closed to them. There has been some BizTalk adoption by parts of the
financial services community, especially with respect to the work Microsoft has done on the Swift Adaptor. Some cases are ‘clean sheet of paper’ projects which have benefited from a quick, relatively low cost implementation as was the case with a new clearing system in Serbia and an RTGS interface at Shamrao Vithal Co-operative Bank (SVCB), see below. MS BizTalk Server runs on Windows Server, using SQL
Server. Written in .Net, more than 350 industry interfaces are available, for common applications, technology adapters and industry protocols such as EDI (Edifact and X12), HIPAA
202
and HL7 and Swift. The A4 Swift offering includes support for FileAct, InterAct, MQ Series, AFTP, File and so on. Microsoft’s many partner solutions extend this number of interfaces still further. The solution is included in the MS BizTalk Server product and licence and so shares the same technical characteristics. The BizTalk Server product provides messaging and
orchestration services. These services include connectivity and integration to disparate systems, data normalisation, co-ordination of communication between systems, BAM and a business rules engine. BizTalk Server 2010 with BizTalk Accelerator for Swift provided financial institutions with a set of Swift solutions including: Banking solutions for payments and cash management; capital market solutions for trading, treasury, custody, and corporate actions; corporate solutions for payments (including supply chain transactions), receipts, cash management, and treasury; and exceptions and investigations. BizTalk Server 2013 was particularly focused on cloud
computing (connecting to the cloud and running in the cloud). Microsoft also claimed improved performance and simplified development and management. The current version is BizTalk Server 2016 and is
Microsoft’s enterprise integration server for orchestrating various applications and services. In late 2017, schemas used with BizTalk Server were made available as open source code. However, the company confirmed that only certain components of the code will be open, and these modifications will not be supported officially in later releases. In June 2017, Microsoft also announced that Azure BizTalk
Services will be most likely discontinued by May 2018. Azure BizTalk Services was used to address messaging transport complexities for premises-based enterprise applications, such as Oracle EBS, or SAP systems, as well as SQL Server. Now, Microsoft wants organizations to shift to using its Azure Logic Apps and Azure App Service Hybrid Connections.
Payment Systems & Suppliers Report |
www.ibsintelligence.com
company details
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176 |
Page 177 |
Page 178 |
Page 179 |
Page 180 |
Page 181 |
Page 182 |
Page 183 |
Page 184 |
Page 185 |
Page 186 |
Page 187 |
Page 188 |
Page 189 |
Page 190 |
Page 191 |
Page 192 |
Page 193 |
Page 194 |
Page 195 |
Page 196 |
Page 197 |
Page 198 |
Page 199 |
Page 200 |
Page 201 |
Page 202 |
Page 203 |
Page 204 |
Page 205 |
Page 206 |
Page 207 |
Page 208 |
Page 209 |
Page 210 |
Page 211 |
Page 212 |
Page 213 |
Page 214 |
Page 215 |
Page 216 |
Page 217 |
Page 218 |
Page 219 |
Page 220 |
Page 221 |
Page 222 |
Page 223 |
Page 224 |
Page 225 |
Page 226 |
Page 227 |
Page 228 |
Page 229 |
Page 230 |
Page 231 |
Page 232 |
Page 233 |
Page 234 |
Page 235 |
Page 236 |
Page 237 |
Page 238 |
Page 239 |
Page 240 |
Page 241 |
Page 242 |
Page 243 |
Page 244 |
Page 245 |
Page 246 |
Page 247 |
Page 248 |
Page 249 |
Page 250 |
Page 251 |
Page 252 |
Page 253 |
Page 254 |
Page 255 |
Page 256 |
Page 257 |
Page 258 |
Page 259 |
Page 260 |
Page 261 |
Page 262 |
Page 263 |
Page 264 |
Page 265 |
Page 266 |
Page 267 |
Page 268 |
Page 269 |
Page 270 |
Page 271 |
Page 272 |
Page 273 |
Page 274 |
Page 275 |
Page 276 |
Page 277 |
Page 278 |
Page 279 |
Page 280 |
Page 281 |
Page 282 |
Page 283 |
Page 284 |
Page 285 |
Page 286 |
Page 287 |
Page 288 |
Page 289 |
Page 290 |
Page 291 |
Page 292 |
Page 293
