how is carrier if i learn SAP XI as i am having currently J2EE experiance ?

Question

currently i am working in j2ee technologies and how it will be if i shifted to SAP XI and search for new job in any of the locations in USA. how it refelects my carrier?

Answer 1

You should go for SAP Netweaver first and then XI. There are a lot of J2EE elements in SAP Netweaver where you can learn a lot and then move easily to XI

You can download netweaver and evaluate it for free

http://help.sap.com/saphelp_erp2005vp/helpdata/en/ee/275c42b4e05542e10000000a1550b0/frameset.htm

Process Integration (PI) Locate the document in its SAP Library structure
Purpose

With the usage type PI, you can integrate applications from one or multiple systems. SAP NetWeaver differentiates between the following areas:

● Cross-system application integration, which does not focus on individual end-user actions. Applications can be company-internal, cross-company, SAP or non-SAP applications. The SAP NetWeaver usage type PI incorporates all functions that were previously a part of SAP Exchange Infrastructure (SAP XI).

● The modeling, administration, and automation of user-driven processes within SAP systems. From a technical viewpoint, a core function of the runtime is that you can save the state of a previously-modeled process and call it up at a later stage, if the process is to be continued as a result of a particular action or event. Since the execution of processes can be useful when integrating applications across system boundaries (without user actions), relevant functions within SAP NetWeaver are reused for this purpose. Together, the functions referred to here are known as Business Process Management.
Design
Internal Company and Cross-Company Application Integration

Applications in a heterogeneous system landscape run on a variety of different systems and platforms.In the long run, it is not cost-effective to integrate all these systems by using point-to-point connections because developers and consultants would need to analyze the implementation in each individual system to get a clear overview of the entire process. As a result, the architecture for application integration in SAP NetWeaver focuses on storing the relevant application integration information centrally. The following figure provides an overview of how to integrate applications with SAP NetWeaver.

This graphic is explained in the accompanying text

The knowledge required to integrate applications is known as collaboration knowledge. To develop and configure this knowledge centrally, developers and consultants work with the Integration Builder. Developers use this tool to define the design of cross-system applications in the Integration Repository. At a later stage, consultants configure this content in the Integration Directory, tailoring it to the particular system landscape of the customer. The System Landscape Directory acts as a central information database, from which the relevant products and systems of the system landscape can be queried for development and configuration purposes, and at runtime.

At runtime, the Integration Server analyzes the data from the Integration Directory and the System Landscape Directory to process and forward messages from senders. In this way, you can develop applications that integrate SAP applications, external applications, marketplace applications, and middleware components from third-party suppliers. The architecture supports the integration of both internal company and cross-company applications.

For more information about architecture, see Structure linkOverview.
Business Process Management

Along with functions from other usage types, Business Process Management covers the modeling, administration, and automation of both more complex cross-system (unbounded) processes and processes embedded in an SAP application within a system. SAP NetWeaver uses the same BPM runtime to execute both unbounded and embedded processes: In the context of unbounded processes, it is known as the Business Process Engine, in the context of embedded processes, it is known as the Workflow Engine.
Unbounded Processes

In the case of complex cross-system processes, stateless processing of messages with the Integration Server is sometimes not sufficient. Developers create integration processes in the Integration Repository to be able to correlate messages and execute more complex processes by means of loops. At runtime, the Integration Server executes these processes on the Business Process Engine and stores information about processes that have already been started and those that are not yet complete.

This graphic is explained in the accompanying text

To send messages from an integration process, the Business Process Engine works closely with the Integration Engine of the Integration Server. When the Integration Server sends messages using an adapter, the Integration Engine works closely with the Adapter Engine.

For more information, see Structure linkIntegration Processes (ccBPM).
Embedded Processes

Using workflows in SAP NetWeaver, you can define user-driven processes and connect existing SAP applications to each other. A simple example of a workflow is the automated processing of a leave request: An employee creates a leave request which is then sent to the relevant manager. If the manager approves the request, the employee receives a corresponding notification and the leave is recorded in the system. The manager can also reject the leave request. You model the process flow and subsequent steps of user actions by using a model, which the Workflow Engine processes at runtime. Unlike unbounded processes, processes defined by using workflows are embedded in an SAP system.

This graphic is explained in the accompanying text
Integration

The usage types Application Server ABAP (AS ABAP) and Java (AS Java) are prerequisites for the usage type PI. The following tables provide overviews of other usage types used in conjunction with the usage type PI.

Development Infrastructure (DI)

Area


Uses

Application Integration


To connect J2EE applications to the Integration Server.

To transport objects from the Integration Repository or the Integration Directory by using the Change Management Service (CMS).

Enterprise Portal (EP)

Area


Uses

Business Task Management


To define and execute collaborative tasks in the portal. Collaborative tasks are less complicated than workflows and they are designed to meet the needs of employees who do not have a technical background but who want to simplify their day-to-day procedures.

For applications that are not used on a regular basis, you can apply guided procedures, which guide the end user through the necessary actions step-by-step.

The universal worklist in the Portal provides you with an overview of processes and enables you to track the status of workflows, collaborative tasks, and guided procedures.

Answer 2

? i circulate to be gaining information of it for the time of my freshman year, and human beings are asserting that its confusing. properly i'm from India, in particular Tamil Nadu, so on the 2d i'm attempting to evaluate Tamil!!! i've got been gaining information of all of it my existence, yet i'm nonetheless no longer fluent sufficient.