SAP XI Architect role

[Former Member]

Hi SDNers

I learned from the blogs & threads by fellow sdners about role of XI Architect

Can any one provide a real time scenario from a stage where XI Architect collects the requirements from Business Analysts to final stage where the Architect defines the architecture(technical specs) for scenario to be developed by developers.

Any documents or weblinks which shows how data, information about the systems involved is gathered, how critical decisions are made about architecture from the initial stage to final stage would be very helpful

Cheers

Guru

[Former Member · Accepted solution]

Hi Guru,

u can fallow below steps

<u><b>Methodology Steps</b></u>

The steps (1) through (4) can be viewed as prerequisites. They can be completed before the XI system is even installed onsite. This will greatly reduce the implementation time. Typically these are also the most time-consuming steps of the project. Multiple tasks can be done in parallel. This should be reflected in the project plan.

<b>1. Scenario Analysis</b> •

Description of the business scenario to be implemented.

• What types of backend systems are involved (mainframe, SAP, etc.)?

• Is this a new development or a replacement for an existing interface?

Deliverables

• High-level scenario description.

• Description of existing scenario implementation, if applicable.

• Description of XI-based scenario.

Resources

• Technical architect

• Functional architect

• XI product expert

Corresponding XI Activities

• Create entries in System Landscape Directory, as appropriate.

<b>2. Interface Analysis</b> •

Is the interface synchronous or asynchronous?

• Does the interface require a technical or application acknowledgement?

• For each interface, identify the outbound and inbound messages.

• Determine data structures for each message type, as applicable.

• Determine flat file format or database structure.

• Determine IDoc / RFC / BAPI structure.

• Determine XML data structures.

• Provide data samples for each message type.

Deliverables

• Inbound/outbound message structure definition

• Data samples for each message

Resources

• Technical and functional analysts for each system to be connected

Corresponding XI Activities

• Create interface objects in Integration Repository.

<b>3. Mapping Definition</b>

Based on deliverables from Step 2, identify mapping rules between each pair of interfaces. This activity typically requires the involvement of business analysts who have knowledge of the business semantics of each interface.

Deliverables

• Mapping specification including source fields, target fields, and transformation rules. Typically this is delivered in the form of a spreadsheet.

Resources

• Functional analysts for each system to be connected

Corresponding XI Activities

• Choose implementation technology for mappings (graphical tool, XSLT, Java).

• Implement mapping based on business rules defined in Step 3 and interface samples and metadata defined in Step 2.

<b>

4. Preparation of the Environment</b>

A test environment must be defined. If B2B integration (across the firewall) is involved, then network connectivity issues need to be addressed. This may include the configuration of proxies, reverse proxies, or other devices located in the DMZ.

Preparation of the test environment includes, of course, the installation and basic post-installation steps of the XI system.

If the scenario is to become productive, then a promote-to-production strategy must be defined and the XI environment must be replicated accordingly (i.e., DEV, QA, PRD).

Deliverables

• XI system is installed.

• Test environment is ready.

• Network connectivity is established between XI and all participating systems.

<b>5. Configuration</b>

There are two parts to the configuration step: backend system configuration and XI configuration.

• Prepare backend applications for message exchange. The backend systems need to be configured to send and receive messages to/from XI. This configuration must be such that the application can produce or receive data samples such as the ones delivered in Step 2.

• Based on deliverables from Steps 1, 2, 3, configure XI objects in Integration Directory.

Deliverables

• Backend systems are ready to produce and consume messages as defined in XI scenario.

• XI system (Integration Directory) is configured.

Resources

• Technical specialists for each system to be connected

• XI specialist

<b>6. Testing</b>

The end-to-end scenario can be tested with different data sets. The testing environment has been prepared beforehand and network connectivity issues have been resolved.

Deliverables

• Sign off on scenario.

Resources

• Technical and functional analysts

• XI specialist

Cheers,

Raghavesh

[prabhu_s2]

just to brief the role:

the SAP XI Architect / Specialist is responsible for the successful delivery of SAP NetWeaver XI solutions . They perform technical tasks including analysis, architecture, design, testing, product installation and support of complex SAP NetWeaver XI solutions to meet client requirements. The Architect/Specialist also manages client relationships within the context of the technical development role.

[Former Member]

Hi Guru

FYI...As per SAP

XI Architect:

- Focus on experience on previous projects

- Convert business/functional requirements in technical specifications

- Prepare the solution Roadmap

- Design the integration process

- Pass technical specification to XI developers

XI Developer:

- starts from technical specification

- create design and configuration objects- execute unit tests

- support integration/stress tests

- document the developments

XI Administrator:

- Install and configure XI server

- Create SLD objects.

- Schedule and check maintenance jobs (archiving, deletion, tuning)

- Assign user roles/auth.

- Create CMS Transport Track

XI Consultant:

depending on the role it could be a developer, an architect or an administrator but generally it is an architect with developments skills as well, and overall a great experience.

These are the things you can ask the client to get the requirements

1) What is the problem? This will give answer for why they are going for XI? Here try to

Understand the business as well as integration? Where XI come into the picture?

2) Total number of systems involved in integration? That is their SLD? Details?

3) Scenario’s (interfaces)? Total? What kind of? But here once again this is depends on project

Some times client will give this (or) based on the requirement you people have to decide?

It is fully depends …..!!!! take care

4) Then based on the scenario you need to get the full information ....this is

place where you can ask all the questions …from scenario to scenario ….get all the details as

mentioned below

apart from the basics try to ask some thing technically

5) Are they providing any XSD,WSDL, documents, Naming conventions..etc

6) Protocals related like http, ftp, smtp, soap....

7) If file related then CSV, Fixed....like that delimiter specific details ….very imp this one

😎 If R/3 present then ....it is Idoc, Rfc, BAPI,....any proxies and webservices for

direct communication ....etc

these are the basic things for XI integration project and after that every thing is specific to

scenario’s

Same time check in the SDN with key word “XI Requirements “

I hope this will help you to face the client but before that try to understand the client business and systems…..!!!!(Imp)

-

---

Mainly provide the solution for Problem

Based on the requirement identify the scenario's, complexity etc....

that depends on the project mostly Architect need to prepare the high level design document but some times detailed TD also

I hope this will anser your question

regards

prasad

[prabhu_s2]

Guru

To know more abt the role of XI architect may be u can luk into the job portals...becoz there is the place u can exactly know what the industry requires from an xi archietect.