IBM software for business process integration. IBM business process integration software IBM WebSphere Process Server integration server

More meanings of this word and English-Russian, Russian-English translations for the word "IBM WEBSPHERE" in dictionaries.

• IBM - Airport Name: Kimball Municipal Airport Airport Location: n.a IATA Code: IBM ICAO Code: KIBM
  Airport Code English Dictionary
• IBM — abbreviation or noun (-s) : an intercontinental ballistic missile
  Webster's New International English Dictionary
• IBM - internationally acclaimed computer company, producer of home computers and related software and equipment (first incorporated as IBM in 1924 with ...
  Dictionary of English language- Editorial bed
• IBM - ■ abbreviation International Business Machines.
  Concise Oxford English vocab
• IBM - IBM trademark BrE AmE ˌaɪ biː ˈem ˌ IBM com ˈ patible
  Longman Pronunciation English Dictionary
• IBM - IBM /ˌaɪ biː ˈem/ BrE AmE trademark International Business Machines; the world's largest computer company, based in the US, which …
  Longman Dictionary of Contemporary English
• IBM
  English basic colloquial vocabulary
• IBM - abbr. International Business Machines.
  Concise Oxford English Dictionary
• IBM - abbr. International Business Machines.
  Oxford English vocab
• IBM-SuperZap
  
• IBM - International Business Machines
  FOLDOC Computer English Dictionary
• IBM - (in full International Business Machines) a US company that was the first to develop computers successfully. IBM computers ...
  Oxford Guide to British and American Culture English vocabulary
• .IBM — Electronic Arts Deluxe Paint Archdos Compressed File (IBM internal file)
  Computer Abbreviations English vocabulary
• IBM - GL International Business Machines Graphics Language
  Computer Acronyms English vocab
• IBM - Inferior But Marketable; It "s Better Manually; Insidious Black Magic; It" s Been Malfunctioning; Incontinent Bowel Movement; and a near- infinite number …
  Jargon File English vocabulary
• IBM - International Business Machines Corporation, a giant present and historic leader in mainframe and PC computing. …
  Jensen's Technology English Glossary
• IBM - See International Business Machines (IBM).
  Josh's Network English Glossary
• IBM - International Business Machine (IBM home page)
  Acronyms - Misc English vocab
• IBM - IBM
  
• IBM - abbr. from International Business Machines "International Business Machines" (computer manufacturing company)
  Big English-Russian Dictionary
• IBM - IBM
  American English-Russian Dictionary
• — IBM WebSphere
  
• IBM - IBM
  Russian-American English Dictionary
• IBM
  English-Russian-English Dictionary of General Vocabulary - Collection of the best dictionaries
• IBM - IBM
  
• IBM - IBM
  English-Russian-dictionary - Bed release
• IBM - = International Business Machines _n. "International Business Machines" (computer manufacturing company)
  Muller's English-Russian Dictionary - 24th edition
• IBM - ibm (international business machines) - . international business cars
  English-Russian dictionary on computers
• IBM - ARCHDOS: Compressed file archive (Internal IBM only)
  Russian-English Edic
• IBM - abbr. from International Business Machines, IBM is a manufacturer of hardware and software, as well as its own trademark(web site: http://www.ibm.com)
  English-Russian Dictionary of Computing and Programming
• IBM - (International Business Machines Corporation) IBM Corporation is one of the oldest computer companies in the world. The world leader in computer technology and ...
  English-Russian dictionary terms and abbreviations on BT, the Internet and programming

The whole complex of IBM software belongs in general to the category of "middleware" (middleware), which means it is aimed at solving integration problems in various aspects of this problem - integrating data, people, applications, resources, processes. In a narrower sense (referring to IT infrastructure), this class of tasks is targeted by the WebSphere family of products. Given the needs of today, IBM has revised its portfolio software products on the WebSphere platform to better address the business needs of building service-oriented architectures (and thus on-demand businesses) and has launched a range of new software products and services.

In this article, we'll look at the IBM WebSphere Business Integration* product line, which includes Business Modeler, Integration Developer, Enterprise Service Bus, Process Server, Business Monitor, Message Broker, MQ, and Partner Gateway. This software covers the entire spectrum of business integration tasks - from application linking to process automation. List it functionality includes the following:

• modeling of corporate business processes;
• integration of processing tools;
• connecting customers and business partners;
• end-to-end monitoring of business processes;
• performance management and business process optimization.

*For information integration solutions from IBM, see "IBM WebSphere Information Integrator - On-Demand Data and Content Integration", "BYTE/Russia" No. 6"2005.

WebSphere Business Modeler

WebSphere Business Modeler 6.0 is based on Eclipse and includes tools that enable business analysts to graphically model business processes. During simulation, the system captures repeating "patterns" - a set of operations necessary to achieve a business goal. Formalization and subsequent application of templates allows you to optimize and automate the relevant business processes.

The tool can model business processes, business elements (documents and products), resources (personnel and physical assets), and structural relationships between organizational elements. It allows you to analyze the listed processes and elements, and then include them in the simulation model.

When working in a WebSphere Business Modeler environment, you can select an appropriate user profile that specifies the level of detail you want when working with models. The Basic Profile (Basic Business Modeling) is intended for business analysts working with a high-level representation of a business process model. The intermediate profile (Intermediate Business Modeling) assumes more detailed description the technical details of the model, including the business rules and business logic that apply to model elements. The top-level profile (Advanced Business Modeling) is aimed at developing detailed models of business processes on the basis of which software applications are created.

When building business processes, various technological modes are used.

Mode based on BPEL technology. A business process represented in BPEL format is imported into the WebSphere Studio Application Developer Integration Edition tool, with which it will be created programming code application that implements this process.

Mode based on FDL technology. FDL business process descriptions are used in the WebSphere MQ Workflow solution as the basis for workflow automation.

Operational mode. This technology mode allows you to set a higher level of detail than the previous two.

WebSphere Integration Developer

The combination of WebSphere Integration Developer with other IBM tools on the one hand and WebSphere Process Server and Application Server on the other provides a platform for business integration projects and is ideal for implementing flexible environments based on service-oriented architecture (SOA). Version 6.0 of the product is built on the Eclipse 3.0 platform and implements the concept of role-based development. Optionally, this environment can be integrated with the IBM WebSphere Business Modeler 6 business intelligence tool and with the IBM Rational Application Developer 6 J2EE and Web solution development tool.

This software allows you to simplify your IT infrastructure by presenting existing IT systems as service components for reuse and efficiency. It gives developers of integration projects the ability to create complex business solutions with minimal skills, providing a single tool for describing all processes based on standards.

WebSphere Integration Developer includes testing, debugging, and deployment tools for developing solutions. The reuse of components is made easier by online modules and libraries. It also includes out-of-the-box constructs for building dynamic processes, including business rules, business state machines and selectors, events, and role functions for tasks. The product is installed on WebSphere Process Server.

WebSphere Enterprise Service Bus

The Enterprise Service Bus (ESB) is a flexible communication infrastructure for integrating applications and services that reduces the number and complexity of interfaces between system components. The ESB distributes messages between services, converts transport protocols and message formats between a requester and a service, and manages business events from different sources.

ESB allows organizations to focus on core business objectives rather than the IT infrastructure required to tie programs together and add new services or change existing ones with little or no impact on existing services. It provides data movement between applications, data format recognition, intelligent routing, and conversion of XML data formats. With it, you can use WebSphere MQ as a framework for communication between applications, as well as other communication protocols such as JMS or HTTP.

WebSphere ESB is built on top of WebSphere Application Server. The product can be used with WebSphere Integration Developer or with Rational Application Developer (if you need to write Java code). To build a single enterprise service bus, IBM offers the IBM WebSphere Message Broker solution in addition to the ESB.

WebSphere Process Server

SOA and Web services are rapidly becoming standard tools for building integration applications. Customers are increasingly convinced that loosely coupled SOA-based integration applications deliver a high degree flexibility and agility, which in turn reduces time to market, reduces total cost of ownership and reduces risk.

Built on WebSphere Application Server V6, IBM WebSphere Process Server provides customers with a wide range of capabilities to help solve modern integration challenges, including business process automation. It is fully compliant with IBM's WebSphere Integration Reference Architecture. Process Server also includes the WebSphere Integration Developer tool.

Building an effective SOA solution requires both a generic component call model and a generic data representation. The WebSphere Process Server solution meets both of these requirements. The technological basis of the universal call model is implemented in the form of the so-called service component architecture (Service Component Architecture, SCA), and the technological basis of the universal data representation is business objects (Business Object). When using SCA, all integration artifacts are described as service components with detailed interfaces. In addition, the concept of a module is implemented in SCA, which allows you to combine service components and perform its further detailing and encapsulation.

WebSphere Integration Developer includes an Assembly Editor tool that allows the developer to combine various components into a module and specify which service interfaces the module will use to communicate with external consumers. Services can be imported components such as Java Beans and Web services, as well as service components provided by WebSphere Process Server. The modules are then interconnected to form a complete integrated solution.

The SCA concept allows the developer to implement the integration logic inside the respective modules. With this approach, changing the service component inside the module will not affect the other modules that are part of the integration solution, since the interface of the changed module remains the same. This approach works throughout the entire WebSphere Process Server solution. In this solution, all integration artifacts (processes, business rules, personnel tasks, etc.) are represented as components of SCA services that can run both in synchronous and asynchronous mode. This creates a very flexible environment. For example, you can easily replace any module containing a personnel task (for example, the module for obtaining approval) with a module containing a business rule. If the module interface remains the same, then new module is installed and automatically connected to all modules interacting with it, without requiring any changes in the latter.

A business object is an extension of a Service Data Object (SDO) that provides an abstraction layer for accessing data. Unlike SDO objects, a general-purpose means of representing heterogeneous data (this can be data described as a JDBC ResultSet, XML Schema, etc.), business objects include several extensions that play an important role in integration solutions and are used to more a detailed view of the data exchanged between the services of the SCA architecture. In particular, extensions include metadata such as change history, information about the context of certain information (dates updated, created, deleted), etc.

Although SCA and business objects are new concepts, their implementation is based on existing standards. For example, the interfaces of any SCA service component are described using WSDL or Java interfaces, and business objects are described using XML Schemas (XSD).

In WebSphere Process Server, all key connection services are implemented using a native JMS provider that provides full interoperability with existing WebSphere MQ-based networks, support for Web services, and Java 2 Connector Architecture 1.5 (see figure).

WebSphere Process Server architecture.

The Common Event Infrastructure (CEI) provides event capture that can be used to monitor applications using IBM WebSphere Business Monitor or other IBM products.

Various service components operate on top of the production infrastructure and SOA core in a WebSphere Process Server solution. Provisioning services include components required for any integration solution, such as data transformation and synchronization services.

Interface mappings. In many cases, the interfaces of existing components match each other semantically, but have a different syntax. Interface mappings allow such components to be invoked by broadcasting the appropriate calls.

Business object mappings are used to convert a business object from one type to another.

Relations. A business integration scenario often involves accessing the same data (such as customer records) used by multiple back-end systems, such as ERP and CRM. A common problem when synchronizing business objects is that different back-end systems use different keys to represent the same object. A relationship service can be used to establish a correspondence between identical objects in different server systems.

Selectors. These components provide dynamic selection and invocation of different services using the same interface. For example, the "Customer Support" business process can involve different options for personnel tasks - for holidays and for normal working days.

WebSphere Process Server supports the main components summarized below.

Business processes. They are based on the mechanism business process management WS-BPEL compliant, the fourth release of the business process "master" running at the top level of the WebSphere Application Server architecture. WS-BPEL compliant models can be created using the WebSphere Integration Developer tool or imported from a business a model created with the WebSphere Business Modeler tool.

Staff Tasks in a WebSphere Process Server solution, these are self-contained components by which employees are assigned a specific job or some other service is invoked. In addition, the Human Task Manager tool allows you to describe special tasks and track their progress. Existing LDAP directories (as well as OS repositories and WebSphere user registries) are used to obtain personnel information.

The transfer of personnel tasks to the following hierarchical levels is supported, including through notifications by e-mail and after the expiration of the priorities. WebSphere Process Server includes an extensible Web client that can be used to work with jobs and processes.

Business state machines(Business State Machine) is one of the ways to model a business process. This method allows an organization to describe its business processes using states and events, which in some cases is easier than modeling business processes using graphs.

Business rules is a means of implementing and tracking business policy by exposing a business function to the outside. This mechanism provides dynamic changes to the business process to improve the efficiency of the business environment. To develop business rules, there is a tool based on the Eclipse platform. WebSphere Process Server also includes a real-time Web-based business intelligence tool that updates business rules as needed without disrupting other services.

All WebSphere Process Server features are configured and administered using special extensions to the WebSphere Application Server Administrator Console and various configuration tools.

WebSphere Process Server leverages the power of an application server to manage transactions, security, clustering, and workload to provide a highly scalable and reliable business integration environment. It also provides full support for ACID transactions when implementing business processes, both short (one transaction from start to finish) and long (many transactions). The product also includes recovery tools - Recovery Manager and Recovery Console. If an application fails while running, Process Server allows the administrator to apply the appropriate procedures to the failed application through the Recovery Console.

The WebSphere Process Server solution provides many opportunities for integration. In addition to importing/exporting native objects (SCA components, Web services, JMS and Enterprise Java Session Beans), this solution provides first-class compatibility with existing WebSphere MQ-based applications. In addition, two types of WebSphere adapters can be used - adapters for certain products (for example, Siebel, SAP, PeopleSoft) and for certain technologies, for example, for relational databases or text files.

WebSphere Business Monitor

The product displays real-time event data related to IBM WebSphere MQ Workflow. Notify and alert key users to help you continuously improve business processes. The solution consists of two main components: the Workflow Control Cockpit and the Business Control Cockpit.

Customizable dashboards are implemented as intuitive WebSphere Portal pages with scorecards, key indicators performance and arrow indicators. Built-in business intelligence tools support multidimensional analysis and reporting.

Analytic components control existing business processes as specified by the business user. At the same time, WebSphere Business Monitor allows you to integrate advanced business intelligence tools with business processes. The user can filter reports, and the Adaptive Action Manager component initiates selected actions or sequences of actions in real time based on established rules and policies.

The product includes IBM WebSphere Business Modeler Basic 6.0 - a modeling, verification and documentation tool for business units and individual users. At the same time, WebSphere Business Monitor can work with WebSphere Business Modeler Advanced, which supports Business Process Execution Language (BPEL) and Workflow Definition Language (FDL).

WebSphere Message Broker

This broker extends the messaging functionality of WebSphere MQ to include routing, transformation, and publish/subscribe messages. Message Broker provides a runtime environment to support message flows. These flows consist of a node graph that implements the necessary processing for application integration and can perform a variety of functions, including the following:

• routing messages to multiple destinations based on message content or message header (one-to-many and many-to-one topologies are supported);
• converting messages to different formats, which allows different applications to exchange messages;
• completion of message content during transmission (for example, by searching a database performed by a message broker);
• storage of information extracted from messages in the process of their transfer to the database (using a message broker);
• the publication of messages and the use by subscribers of criteria based on subject or content to select messages to receive;
• interaction with other connection support mechanisms, such as MQSeries Everyplace;
• extending the core functionality of WebSphere MQ Message Broker with Java and C/C++ pluggable nodes;
• handling message content across a range of message domains, including the XML domain, which handles self-defined (or generic) XML messages, the Message Repository Manager (MRM), which handles predefined message sets, and the unstructured data (BLOB domain).

WebSphere Message Broker provides scalability options in the form of message flow copies and execution groups, and simplifies the integration of existing applications and Web services by transforming and routing SOAP messages, and by logging Web service transactions. It also acts as an intermediary between Web services and other integration models and provides integrated WebSphere MQ data transport for enterprise, mobile, broadcast, real-time data and telemetry endpoints. The Message Broker Toolkit for WebSphere Studio is based on Eclipse.

WebSphere Business Integration Server works with two different but compatible integration brokers: WebSphere InterChange Server and WebSphere Message Broker. The integration systems that these two brokers use are quite different. WebSphere InterChange Server is a process integration engine. Its main purpose is to streamline interactions between applications, and to do this it needs to maintain state information and implement concepts such as compensating transactions and dynamic cross-references. WebSphere Message Broker, in turn, offers services for connecting applications. They usually act as an intermediary between applications, providing fast data routing and transformation. Both products are able to work with each other without problems. WebSphere Message Broker can act as an intermediary, providing services for communication between applications and WebSphere InterChange Server.

WebSphere Message Broker supports an extensive list of operating systems (Windows Server, AIX, HP-UX, Solaris, Linux for Intel, Linux for zSeries, and z/OS) and uses a DB2 database as a repository for storing configuration information. In addition, both brokers use a database to store the information they need to process messages. The following databases are supported: IBM DB2 UDB Enterprise Edition, IBM DB2 UDB for z/OS and OS/390, Oracle, Sybase Adaptive Server Enterprise (ASE), Microsoft SQL Server. Configuration Manager and Message Broker Toolkit for WebSphere Studio are only supported on Windows platforms.

IBM WebSphere MQ

WebSphere MQ is IBM's advanced queuing and messaging middleware. This solution can be deployed on a wide range of platforms and operating systems. It allows programs to communicate with each other over a network of disparate components such as processors, subsystems, operating systems, and communication protocols. WebSphere MQ gives you the ability to:

• connect any commercial system that exists today (supports more than 35 platforms);
• cope with network disruptions - important data is always delivered;
• provide guaranteed one-time delivery;
• integrate heterogeneous "islands" of automation;
• maintain time-independent communication;
• maintain high throughput (customers process more than 250 million messages per day);
• perform SSL communication.

WebSphere Partner Gateway

This software is a consolidated business-to-business (B2B) communication gateway that allows you to extend process integration beyond the enterprise and reduce the cost of B2B integration. The solution integrates external processes and partner communities with the company's internal processes and infrastructures, providing extensive partner profile management and simple, reliable and secure B2B messaging.

This product is the next version of WebSphere Business Integration Connect V4.2 released under a new name, inheriting all its features. Partner Gateway provides a single B2B partner management environment that supports traditional data formats and EDI and XML based messaging protocols for B2B integration such as AS1, AS2 and RosettaNet. The product allows the company to respond more quickly to changes in external conditions. As a result, business processes - fully integrated both inside and outside the company, with key partners, suppliers and customers - can quickly respond to any customer requirements, market opportunities and external threats.

WebSphere Partner Gateway V6.0 is available in three editions: Express, Advanced Edition, and Enterprise Edition. Express is a central B2B gateway that supports HTTP, HTTPS, and AS2 communication and up to five external connections. The Advanced Edition is designed to integrate large business communities and is licensed for a certain number of external connections. Finally, the Enterprise Edition is the central B2B gateway for integrating large business communities with unlimited external connections.

The Advanced and Enterprise Editions introduced with this release of the software have a number of features: built-in support for EDI (Electronic Data Interchange), a graphical drag-and-drop mapping tool, an additional RosettaNet Partner Interface Process (PIPs), enhancements regarding usability and performance, the ability to install on WebSphere Application Server 6.

This article details the product deployment process IBM WebSphere Application Server V8.5 for distributed environments ( distributed environments), on the example of MS Windows Server 2008 R2 Enterprise.

The IBM WebSphere Application Server deployment process is divided into two stages: 1. 2. Create profiles ( profiles) that define the WAS execution environment Let's look at both stages in more detail.

Setting the basic math of the product

Starting with WAS V8.0, installing the application server and related products ( supplements) occurs with the help of IBM Installation Manager(IM). The innovation applies to all platforms. That is, you first need to install IBM IM, and then use it to install other products.

The IM tool comes with the product distributions, and the installation files for WAS and related products themselves are packages for IM placed in archives - vaults.

First, install IM, to do this, unzip it and run install.exe. The IM installation process is simple, and boils down to the usual switching between installer dialogs, no extras. There are no options or hidden settings here. After installation, you will be prompted to launch IM, which will bring up its main window, shown below.

If you immediately select “ Install“, then we will see an empty window, that is, IM does not yet know what packages you have to install. Therefore, you need to specify the location of the repository of software packages, after unzipping the distributions. It is better to do this as follows: unzip all WAS product files into a separate directory, and Supplements archives into another.

To add a software package repository to the “ File“ should select item “ Options…“:

In the window that appears, in the section “ Vaults“, you must press “ Add Repositories":

Then specify the full path to the file diskTag.inf the first disc of the packages to be installed. The remaining disks of distribution kits will be “picked up” by IM itself, due to the fact that they are unzipped into one directory.

After completing the steps described above, in the main window of IM, select the item “ Install“, as a result of which we will see a list of all products available for installation.

Select IBM WebSphere Application Server and click “ Further“, after which we get to the page with license agreements.
We agree to all the conditions, click " Further“, and select the installation directories, click “ Further“.
You will be prompted to select language packs, English is always selected, by default:
The next step presents additional options settings, such as: JVM bit depth, full or liberty profile, etc.
Select the required options and then click " Further“ and get to the window with the final information on the installation:

We check the final information on the installation and, if everything is correct, click “ Install“. After successfully installing the selected packages, the window shown below will appear.

This completes the first phase of IBM WebSphere Application Server deployment. IM prompts you to run the profile management tool WebSphere Customization Toolbox 8.5. You can do this now, right after installing the packages, or you can do it later.

Create a profile (profile)

Profile (or profile) is a set of settings that define the WAS execution environment.

You can create a profile in two main ways: using the tool WebSphere Customization Toolbox or through command line using manageprofiles.bat(manageprofiles.sh). In this article, we'll look at creating a profile through the WebSphere Customization Toolbox. The main window of the tool is shown below:

Press the button " Create“, after which you will be prompted to select a profile type:

When you select a profile type, its description is displayed below. However, often the description is not informative, and the situation is aggravated by the translation into Russian. Understanding the concept of WAS, its components, and the interaction between them is very important to correctly create a target environment. These issues will be discussed in more detail in a separate article, in the section “ History and Basics“. At this stage, it is important to understand what WAS architectural configuration you need to deploy:

• Standalone (Base)– standalone server environment. A configuration without scalability, fault tolerance, and suitable for debugging and testing. It is a separate application server with a repository of configuration files and application data, as well as an administrative console.
• Network Deployment (ND)– distributed server environment. Here "distributed environment" means the use of several application servers, usually located on different servers. A production configuration that provides scalability, resiliency, and high application availability. ND is a collection of application servers located in nodes (Nodes) managed from one point - the deployment manager (Deployment Manager), located within the same administrative domain - cells (Cell).

The process of creating profiles is almost the same for all types. If you are going to deploy the configuration Network Deployment, I advise you to first create a deployment manager profile ( Deployment Manager), then create node profiles, and only then, using the WAS administrative console, create application servers and clusters. Therefore, in this article, we will only consider creating a deployment manager. To do this, select the type Control“ and press “ Further“. In the type " Control“ Three kinds of profiles are available: Network Agent, Deployment Manager, and Job Manager. Choose " Deployment Administrator“ and press “ Further“.

It is better to choose advanced profiling, in which case you will be able to specify the names of WAS components, ports, installation directories and other additional options yourself. For profile " Deployment Administrator“In the next step, we specify whether to expand the administrative console or not. Of course, for the convenience of working with WAS, leave this option activated and click “ Further“.

At the next stage, specify the name of the profile and the directory where the profile is located, click “ Further“:
Then, following the naming rules, specify the host name, host (server) name or IP address, cell name, and then click “ Further“:
Specify whether to enable administrative protection, enter the login / password of the administrator and click “ Further“:

The next section is about a security certificate, which you can either create or import. Usually, when deploying WAS, a new certificate is created, so select the appropriate option and click “ Further“:

Ist eine Produktlinie der Firma IBM, die unterschiedliche Software für Anwendungsintegration, Infrastruktur (z. B. Transaktionen und Warteschlangen) und eine integrierte Entwicklungsumgebung umfasst. Bekannte WebSphere Produkte sind unter anderem ... Deutsch Wikipedia

WebSphere is a family of software products from IBM. WebSphere is often referred to as the name of one specific product: WebSphere Application Server (WAS). WebSphere belongs to the category of intermediate middleware ... ... Wikipedia

WebSphere is a family of software products from WebSphere Application Server (WAS). WebSphere belongs to the category of middleware middleware that allows applications to e-business(e business) work for ... ... Wikipedia

Developer IBM Environnements Java EE ... Wikipedia en Français

Est une marque du groupe IBM. Le nom de Websphere renvoie généralement à la plate forme applicative WebSphere Application Server (WAS). Sommaire 1 La plate forme applicative 2 Les produits Websphere 3 WAS ... Wikipedia en Français

WebSphere MQ, anciennement MQ Series est une famille de logiciels, développé par IBM depuis 1992. Websphere MQ est un service de messagerie inter applicative (ou MOM pour Message Oriented Middleware), c est à dire qu il permet la communication… … Wikipédia en Français

Logo WebSphere ist eine Produktlinie der Firma IBM, die unterschiedliche Software für Anwendungsintegration, Infrastruktur (z. B. Transaktionen und Warteschlangen) und eine integrierte Entwicklungsumgebung umfasst. Bekannte WebSphere Product ... ... Deutsch Wikipedia

IBM WebSphere MQ family of networking software open source MQSeries: IBM renamed it in 2002 to associate with the Message Oriented Middleware product line. It allows independent and possibly working not ... ... Wikipedia

- ● np. m. tm. APPLI Plateforme logicielle d IBM. La page de présentation du truc est un exemple de propagande marketing sans intérêt ne permettant absolument pas de savoir exactement ce que fait le bidule … Dictionnaire d "informatique francophone

WebSphere es una familia de productos de software propietario de IBM, aunque el término se refiere de manera popular a uno de sus productos específicos: WebSphere Application Server (WAS). WebSphere ayudó a definir la categoría de software… … Wikipedia Español

WebSphere ist eine Produktlinie der Firma IBM, die unterschiedliche Software für Anwendungsintegration, Infrastruktur (z. B. Transaktionen und Warteschlangen) und eine integrierte Entwicklungsumgebung umfasst. Bekannte WebSphere Produkte sind… … Deutsch Wikipedia

Books

• Domain-Oriented Design (DDD). Structuring Complex Software Systems, Eric Evans. The classic book by E. Evans covers the most general, strategic range of issues related to object-oriented software development. This is processing and structuring ... Buy for 5445 rubles
• Enterprise application integration templates. Design, Build, and Deploy Solutions, Hop Gregor, Woolf Bobby. The book "Enterprise Application Integration Patterns" explores strategies for integrating enterprise applications using messaging mechanisms. The authors consider patterns ...