Usability Feature in PI 71 Development and Configtime

7/29/2019 Usability Feature in PI 71 Development and Configtime

1/18

Usability Features In SAP Netweaver PI 7.1 Development And Configuration Times

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

2007 SAP AG 1

Usability Features in SAP NetWeaver PI 7.1 Development andConfiguration Times

Applies to:SAP NetWeaver PI 7.1

SummarySAP NetWeaver PI 7.1 includes a wealthy set of development utilities that together with the runtime stabilityand performance make this SAP NetWeaver component the natural choice for your process integrationscenarios.

This document will detail some of those development and configuration time utilities -many of them newlyintroduced in PI 7.1- and show how they help to increase productivity or administration capabilities to supportlarge development teams.

You might be already familiar with some of them, but I think its worth taking a look.

Author: Daniel Horacio Bianchin

Company: SAP

Created on: October 2007

Author BioDaniel has been working with SAP technology since 1996, and in 1997 he joined SAP. Overthe last 10 years he has worked on more than 35 projects plus consulting, training andpresales activities.

At SAP, he started as an ABAP and RFC (C++) consultant later began to work with ALEinterfaces, doing quality assurance, development optimization, in-house softwaredevelopment and design, and then CRM Internet Sales implementation and interfacearchitecture design. After that, he has been leading development and integration teams usingSAP BC and XI. In 2005 he joined the SAP NetWeaver Regional Implementation Group.


2/18



2007 SAP AG 2

Table of ContentsUsability Features in SAP NetWeaver PI 7.1 Development and Configuration Times.................... 1 Applies to:........................................................................................................................................ 1 Summary.......................................................................................................................................... 1 Author Bio........................................................................................................................................ 1

Table of Contents ............................................................................................................................ 2 Introduction...................................................................................................................................... 3 Usability and Development and Configuration Administration ........................................................ 3

Objects Tree Filtering and Positioning ..................................................................................... 4 Folders in the Enterprise Services Repository and Integration Directory ................................ 7 Software Component Version Relationships.......................................................................... 10 Object search, usage reference and objects navigation........................................................ 11 Wildcards, context reference and Keyboard shortcuts........................................................... 13 Authorizations......................................................................................................................... 14 Lifecycle Management: Objects Activation............................................................................. 15 Local Objects.......................................................................................................................... 16

Summary........................................................................................................................................ 16 Keeping a simple virtual environment for each developer..................................................... 16 Customer Engagement Lifecycle support.............................................................................. 16

Related Content in SDN ................................................................................................................ 17 Copyright........................................................................................................................................ 18


3/18



2007 SAP AG 3

Introduction

Usability and Development and Configuration AdministrationGood development administration tools result in more stable software (reducing downtimes) and reducingmaintenance efforts.

Also a lack of administration tools makes a central development environment nearly impossible to use.

These tools are completely necessary in terms of eSOA, because the number of integration objects is big,and numbers of diverse organizational units that interact in a unique development and configurationenvironment are pretty heterogeneous.

Consider that PI 7.1 also introduces decentralized processing, what makes its processing capabilitiesunbound at runtime, so the possibilities that important companies share a global modeling, development andconfiguration environment across different subsidiaries, branched, etc., to later uniformly apply the patternsin are high.

Before starting with the list of items, it might be interesting to refresh the PI implementation methodology, soas to also to remember the steps and roles involved. Consider that this methodology is still not updated to PI7.1, but still useful as reference: http://service.sap.com/~sapidb/011000358700006503452006E .
http://service.sap.com/~sapidb/011000358700006503452006Ehttp://service.sap.com/~sapidb/011000358700006503452006E


4/18



2007 SAP AG 4

Objects Tree Filtering and Positioning

One important set of features is the objectstree and its positioning and filteringcapabilities.

J ust consider a list of software componentslike this one. Every time you start the ESRepository, you should scroll and open yourparticular software component and softwarecomponent version.

If the list keeps on growing, it is not unusable,but the time spent in positioning and thepossibility or error increases.

A nice feature to avoid it, is applying the filter

functionality. It allows you to select just the setof software component and softwarecomponent version you are interested in, in aparticular moment.


5/18



2007 SAP AG 5

Execute the function and simply unselect thewhole tree

Then, select the software components orparticular software component versions youare interested in.

As result, you get your virtual view of the

repository, at software component andsoftware component version level.

Another nice idea is to filter the object typesyou are interested in.


6/18



2007 SAP AG 6

Easily click on the objects you are notinterested in, and they will also be filtered fromthe tree for you.

Of course, the well known tree positioningcapability is still there


7/18



2007 SAP AG 7

For example, it is possible to select just theMessage Types, if you are not going to workwith any other objects..

By default, you will have your navigationconfiguration considered after IntegrationBuilder restart.

You can avoid it if you want.

Folders in the Enterprise Services Repository and Integration Directory

As you might have realized, inPI 7.1 the default objectgrouping by object types is notcreated until either an object of that particular type or a folderis created.

Folders are more flexible andallow you to structure in amore convenient way inaccordance with yourrequirements. Suppose youwant to create a business

object / object type hierarchy,or group determined datatypes under another particularfolder, everything is possible.

To create the folder, simplyright click on the parent object(namespace or folder) andexecute Create Folder, thenname it.


8/18



2007 SAP AG 8

Here you see a businessobject / object type hierarchy.

Also the service interfaces,since they share most of theobject types, are assigned tointermediate folders. That is,not only leaf nodes are allowedto contain objects.

There are two additional goodfeatures regarding folder in ESRepository and IntegrationDirectory.

One is the option to executemassive commands at folder

level for the objects contained. The other is the possibility towork with authorizations atfolder level, what increases thegranularity of roles.

Suppose only some roles areallowed to work on particularmapping objects, you justexecute Edit Authorization onthis folder and change them asrequired.


9/18



2007 SAP AG 9

In the Integration Directoryfolder are optional. You caneither show or hide them.

To manage your objects, youcan use folders, configurationscenarios or objects typegroupings.Objects types grouping havebeen available for a long type,

al

not include

thean

s

also configuration scenarios.

There have been a conceptuchange regarding objectsrepresentation in the tree; theydo not appear in the tree morethan once anymore. Thatmeans that configurationscenarios doreferences to objects and list

them in the tree, but rathershow them in a list in the mainscreen area when you openthe scenario.

Also the folders dont have areference to an object, but theobject itself is contained infolder. So if you try to copyobject from one folder toanother, the source folder doenot contain the objectanymore.

For that reason, it is a goodpractice to create common orbasis folders toaccommodate shared objectslike business systems,channels, or whatever makessense in your installation.

Later you will be able to givparticular aut

ehorization, for

example to administrators, towork on that folder andmaintain authenticationinformation, while other roleswill be able to deal with logicalrouting configuration only.


10/18



2007 SAP AG 10

As mentioned before theconfiguration scenario is notrepresenting the object list in the tree anymore.

To simulate that functionyou have to open the scenario

and detach the window.

referenced

ality

uk:

Configuration scenarios andfolders are not the same thing,there is a very good blog onSDN regarding folder, yoshould go and take a loo

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/7010

Software Component Version

This feature has also beenavailable for a while. It is thepossibility to describe

Relati

and somehow with themethodology too: (ref:https://weblogs.sdn.sap.com/

onships

relationships at SLD level. They are required if you wantto comply with the naming

pub/wlg/5356 )


11/18



2007 SAP AG 11

In the ES Repository, you

n.

one, youcan generate a new versionfor the root to include thenew functionality, while youkeep the other basisrelationships, in the sameversion as before.

will see the list of basissoftware componentversions, and will be able toselect object from themevery time you need

something for your rootsoftware component versio

Version handling is anotherpowerful feature here; if youupgrade a basis

Object search, usage reference and objects navigation

In an eSOAarchitecture, youneed powerfultools to manage allthe objects. One of the tools is the wellknown SAPWhere-Used List

It allows you

to see where aparticular object isreferenced,directly orindirectly also.


12/18



2007 SAP AG 12

Another tool is theIt issearch utility.

verycomprehensible,supports wildcardsand extended

attributes.

Both the Where-used List and the

S Repository

fromthe listed object toits definition.

You simplydouble-click on it

S Repository

fromthe listed object toits definition.

You simplydouble-click on it

search utility(actually, most of the Eand IntegrationDirectory objects)support thenavigation

e Eand IntegrationDirectory objects)support thenavigation

And you get therequested object ina new tabstrip.


13/18



2007 SAP AG 13

Wildcards, context referen

more importantof objectsty error prone to

of similarve to

tter to simplyith key

ce and Keyboard shortcuts

Wildcards becomewhen the numberincreases. It is pretreceive a long listingobjects from where you hachoose one. It is berestrict the search winformation first.

Then, using the dropdothe mouse or simplykey from your ke

wn box withusing the F4

yboard you get thelist of objects.

The search criteria will be shownfirst and then the results from whereyou can type an addition searchcriterion or easily double-click onthe desired entry.


14/18



2007 SAP AG 14

Besides the Tabular Searchtabstrips there is anotherHierarchical Search just in caseyou need to know the objectclassification information fo

r the oneyou are looking for.

Authorizations

It waspossiblebefore todefineauthorizationsat object levelfor particularroles. Thisfunctionalityhas beenenhanced inthis version tobetter supportlargedevelopmentteams.

As shownbefore,folders alloyou to groupand handleauthorizationson thegranularitylevel thatbetter fits youneeds.

w


15/18



2007 SAP AG 15

Lifecycle Management: Objects Activation

on butive objects versions, allll see the active version if

the opportunity to modifye version while a previous

while (withouton).

Integratiwork with inacother users wiavailable.So it gives youa new inactivone is used in the meancreating a new versi

ilder objects allow you to

Inactive versions can be transferredamong system users.

Select the change list you are interestedin, and transfer the inactive versions toyour own user.

The activation can be executed from

different places, you can right-click onthe inactive object and choose theoption.


16/18



2007 SAP AG 16

Also the activation is present in theobject display or modificationfunctionality.

Of course it is still possible to select youchange list and do the massive activationas before.

Even when it wont be probably available wlater using CTS+to include most of SAP Ndifferent tec

ith the first PI 7.1 general availability release, it will be possibleetWeaver objects in a common transport orders instead of using

hnologies for each. For example, Enterprise Services Repository objects will be transportedtogether with ABAP mapping classes

Local Objects

Local objects allowyou to createsoftware componentsfor ES Repositorytesting proposes, youdont need to createthe object in SLD.

You directly createthem from thegeneral objectcreation form.

Summary

Keeping a simple virtual environment for each developer

For sure the list of available utilities (considering the new ones included) will simplify development andmaintenance. Consider how easy it is to select objects form a list of five, instead of browsing long listing of objects with nearly the same name! Also, the functionalities are completely intuitive and dont require furtherexplanations to understand how to use them.

Customer Engagement Lifecycle support

Usability, simplification, naming, methodology, stability, scalability, performance, etc. Yes, there are manyfactors to take into account when you choose your process integration application, and development and


17/18



2007 SAP AG 17

configuration topics are not the exception. A well understood eSOA methodology strategy requires powerfultools and the evolution of the Integration Repository (the ES Repository) and Integration Directory have the

la

SDNtps://weblogs.sdn.sap.com/pub/wlg/5356

capability to handle

Related Content in Folders:

rge eSOA implementations.

ht

implementation: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/7010 PI scenariosaver PI 7.1 Overview: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6204 SAP NetWe


18/18



CopyrightCopyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and P owerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,Netfinity, Tivoli, Informix, i5/OS, P OWER, P OWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OS F/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, MassachusettsInstitute of Technology.

J ava is a registered trademark of Sun Microsystems, Inc. J avaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.

These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied

warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that mayresult from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within thesematerials. SAP has no control over the information that you may access through the use of hot links contained in these materials anddoes not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to beused in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errorsor damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Usability Feature in PI 71 Development and Configtime

Documents

Transcript of Usability Feature in PI 71 Development and Configtime