Академический Документы
Профессиональный Документы
Культура Документы
1
Objectives
2
Integration Builder Administration
Contents:
Basic Administrative functions in the Integration Builder
Repository
Basic Administrative functions in the Integration Builder
Directory
Basic Administrative functions in the Integration Builder
Runtime
3
Integration Builder Administration
Architecture Overview
4
Integration Repository - Overview
Integration Builder
Pre-delivered
Integration Content
Integration Repository for mySAP solutions
Business Open for
Scenario Editor
Scenarios
collaboration
Business knowledge of non-
Process Editor BPEL
Processes
SAP systems, using
Mapping Editor Mappings XSLT open standards (e.g.
Java
WSDL)
Context
Condition Editor XPath
Objects Provision to
enhance XI design
Message WSDL
Interfaces time objects by
Message Types customers / partners
Data Type Editor Data Types (XSD)
Java based
graphical tools
Web AS
5
Integration Directory - Overview
6
Integration Builder Administration
Architecture Overview
7
Integration Builder Administration
From the Integration Builder Homepage, select the “Administration tab, you will
then be prompted to enter your user-id and password. This will then take you to
the – Repository, Directory , Runtime Tabs.
Under the Repository Tab, you will find the following major sections for
administration:
System Information
Administration of Properties
Administration of Locks
Caches
Java Web Start
8
Integration Builder Administration - Repository
System Information
9
Integration Builder Administration - Repository
General Administration of XID: Repository has three key sections which are
made up of application, server and system environment.
The application section highlights file access for system root directory and
transport directories for both export and import files.
The server section highlights general information on server ID, server version of
J2EE, memory and file access for local directories.
The system environment section contains information about Java Runtime
environment with version level, Java Virtual Machine with version level and the
operating system platform with an associated version level.
10
Integration Builder Administration - Repository
Administration of Properties
This provides you with a refresh capability for all applications for
ExchangeProfileR3PropertySource(dewall34, "IntegrationBuilder.Repository,
IntegrationBuilder, Connections, Default.XML, Default.DatabaseSettings, default").
11
Integration Builder Administration - Repository
12
Integration Builder Administration - Repository
Exchange Profile
This provides you with a shortcut to the exchange profile settings administration
for Adapter Framework, Application system, Connections, Integration Builder,
Integration Server and Runtime Workbench.
13
Integration Builder Administration - Repository
Administration of Locks
This area of administration provides you with Locks overview with respect to
removing selected locked objects set by users.
14
Integration Builder Administration - Repository
The steps outlined in the data migration tool section may only be performed when
carrying out an Integration Builder migration from XI 2.0 to XI 3.0. Both the
Integration-Repository and Integration-Directory will be affected during this
procedure.
The key migration steps included in this logical process are:
Export steps – Pending changelist (Checking to make sure that no changelist exists in the XI
2.0 system).
Import Steps
Cleanup Steps
15
Integration Builder Administration
Architecture Overview
16
Integration Builder Administration - Directory
Automatic re-initialization
This function will cause a re-initialization of the client at the next click on its start
link. All necessary resources will be collected and signed. A lock will be set, so
that only one re-initialization can happen at the same time.
Use this function if you are sure that no reconfiguration thread is currently running,
for example after a restart of the J2EE-server. If more than one re-
initialization thread is running, problems may occur.
17
Integration Builder Administration
Architecture Overview
18
Integration Builder Administration - Runtime
SLD Cache
When Integration Directory objects are activated, the changes are replicated
In the Integration Server runtime cache (accessed via SXI_CACHE)
In the CPA cache of each adapter engine (central and de-central)
• Information about the adapter engines is obtained from the SLD and therefore you
can use this option to refresh the SLD cache.
19
CMS and Changelist integration
When the CMS link is activated, all SWCV are marked automatically as transportable
via change lists.
This can be changed by setting the behavior per SWCV in the Administration part.
20
Summary
21