1

Welcome to this SAP Presentation.

Supportability features and considerations when using SAP NetWeaver

Gateway Productivity Accelerator for Microsoft or GWPAM for short, will

be covered

2

The following agenda topics will be covered:

Logging

o Installation/Un-Installation

o Plug-In for Microsoft Visual Studio

o Generated Application

o Tracking call in Gateway

o Additional GWPAM Logging Options

Project Objects

Troubleshooting

o Entry in Project Templates is Missing

o Browse SAP Services Option is Missing

o Content Type in Microsoft Outlook is Missing or Empty

o “FindRibbons” task could not be loaded

o Multiple App.config in a solution

3

The “GWPAM Visual Studio Add-on” has logging features which can help trace errors that may

occur during the usage of the tool.

If you install the GWPAM Visual Studio Add-On via the command line instead of executing the

‘Setup.exe’, you are able to control the location of the logs for the installation process.

1. Create a text file in a location where you want to store the logs

2. Navigate to the folder C:\Windows\system32 and open the command prompt from that

location

3. Enter the command msiexec /i <“the absolute path of the installer”> /L*v <“the absolute path

to the log file”>

4. The steps of the installation process will be logged in the location you indicated as well as

the standard ‘Event Viewer – Application’ logs

4

As with the installation if you un-install the GWPAM Visual Studio Add-On via the command line

instead of un-installing via the Control Panel Programs and Features, you are able to control

the location of the logs for the un-install process.

1. Create a text file in a location where you want to store the logs

2. Navigate to the folder C:\Windows\system32 and open the command prompt from that

location

3. Enter the command msiexec /x <“the absolute path of the installer”> /L*v <“the absolute

path to the log file”>

4. The steps of the un-installation process will be logged in the location you indicated as well

as the standard ‘Event Viewer – Application’ logs

5

The GWPAM Add-On has logging features which can help us trace the error that might occur during

the usage of the tool. The logging is controlled by a configuration file that is placed in the user’s

application data folder (%appdata%).

Access the GWPAMProjectWizard.dll.config configuration file, by navigating to the directory

%APPDATA%\SAP AG\GWPAM\Configuration. The file is placed there during installation GWPAM

Add-On.

6

Once you open the configuration file, navigate to the ‘appSettings’ section.

You can control the log behavior by changing the following keys:

AllowedLogsFolderSize: This key decides what is the maximum size to which the logs folder should

grow up to. Please mention the value in kilo bytes. In the above example the logs folder should be

approximately of 1 MB.

LogDirectory: Here you specify the folder in which the logs would be generated. You can either

provide an absolute path or you can give a folder name. If absolute path is not provided then the

logs are generated in the %TEMP% folder.

LogFileSize: It is the maximum size to which the log files are allowed to grow. Please take care that

it is lower than Folder size as otherwise the logs will be removed as soon as the folder size is

reached.

LogOptions: This key decides where to log the events, in a file location of the windows event viewer.

The following sets of values are possible: 0 for file location, 1 for event viewer and 2 for both file

location and event viewer. The logs will appear in the Event Viewer in the folder ‘Application and

Services Logs GWPAM_Logs’.

7

LogLevel: This key controls the amount and scenarios where logs are generated. The

following values are possible : 0 no logs , 1 for only error should be logged, 2 for error and

warning logging, 3 for information, error and warning logging, 4 for all logs.

By controlling the above mentioned keys, we can control the amount of information that would

appear in the logs and also the location and size of the logs itself.

7

The GWPAM Generated Application project follows a similar logging pattern as outlined in the GWPAM

plugin for Visual Studio Logging.

The difference being is that all the required configuration files and even the logger classes are readily

available in the generated application.

8

You can either choose to use the provided infrastructure for logging or you can write your own logger. If

you are using the auto generated logger, you can control it from the app.config file. The auto generated

logger leverages the trace utility already present within .NET framework. You can change the trace

listener or add multiple trace listeners to your code.

More information on trace listeners can be found on http://msdn.microsoft.com/en-

us/library/4y5y10s7(v=vs.100).aspx .

9

The listener writes to the event viewer and the logs would be located under Windows Logs

Application logs.

The key TraceLevel in the ‘app.config’ file behaves similar to loglevel key in the

GWPAMProjectWizard.dll.config configuration file.

It determines what information needs to be logged. The following are the set of values that key can

take:

0 – Off

1- Error

2-Warning and Error

3-Information, Warning and Error

4-Verbose

If a new logger is implemented all the details in the App.config file should be reviewed as they may

need to be updated.

10

During Runtime the Event Viewer Application logs are populated. To track the call coming from

Outlook to Gateway use the Activity Id in the logs to navigate to corresponding error in the SAP

NetWeaver Gateway System in transaction SLG1

11

In addition to the logging options already covered, several other options are listed below:

SAP Client plug in tool via plugin-starter-gui.exe and incorporate with Solution Manager

Change logging rules in GWPAM coding to render to a 3rd party tool

12

Upon the successful generation of a project, all objects related to the project, including the HTML

Report, generated codes, dll files etc. can be accessed under the project name in the default location

of a Microsoft Visual Studio project.

13

This section describes solutions to commonly encountered issues when using the GWPAM application

Symptom

After the installation of the GWPAM Add-On, the following entries are missing in Visual Studio.

GWPAM does not appear under the Project Templates

Tools menu does not display the ‘Browse SAP Services’

Solution

This issue occurs if Visual Studio was not opened after it was installed. Follow the steps below to

resolve the issue.

1. Uninstall the GWPAM Add-On

2. Open Visual Studio

3. Re-install the GWPAM Add-On

14

Symptom

After the installation of the GWPAM Visual Studio Add-On, the Tools menu does not display the

option ‘Browse SAP Services’.

Solution

Follow the steps below to resolve the issue:

1. Go to Start All Programs Microsoft Visual Studio 2010(12) Visual Studio 2010(12)

Developer Command Prompt for VS

2. Right click on Developer Command Prompt for VS an select Run as administrator from the

resulting menu

3. In the command prompt type devenv/setup

4. From the taskbar, open the firewall configuration and disable the following

Host IPS

Network IPS

Firewall

15

Symptom

In Microsoft Outlook when you click “GetAll” a missing or an empty content type header was

found when trying to read a message. Also while adding SAP Reference.

Solution

To resolve this issue install Microsoft WCF Data Service needs to be installed on the client

machine.

On machines running Visual Studio 2010 install Microsoft WCF Data Service 5.3 or higher

On machines running Visual Studio 2012 install Microsoft WCF Data Service 5.5 or higher

16

Symptom

When you build a project in Microsoft Visual Studio 2010, you get the error message ‘The

“FindRibbons” task could not be loaded from the assembly

Microsoft.VisualStudio.Tools.Office.BuildTasks’

Solution

This issue occurs when Visual Studio 2012 and 2010 are installed on the same machine. If you

have Visual Studio 2012 and 2010 installed on the same machine, and the build fails, follow the

steps below to resolve the issue:

If you are running a 32bit Operating system, proceed as follows:

Go to C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\OfficeTools. Open the

Microsoft.VisualStudio.Tools.Office.targets file. Replace all 10.0.0.0 with 11.0.0.0. Restart

Visual Studio.

If you are running a 64bit Operating system, proceed as follows:

Go to C:\Program Files(x86)\MSBuild\Microsoft\VisualStudio\v10.0\OfficeTools. Open the

Microsoft.VisualStudio.Tools.Office.targets file. Replace all 10.0.0.0 with 11.0.0.0.

Restart Visual Studio.

Open and build the project from Visual Studio 2012.

17

Symptom

You get a pop-up message that prompts you to check your application configuration as shown:

Solution

This is often caused by the presence of multiple App.config file in the solution. The App.config that

holds all the required configuration for a GWPAM based solution to work is stored inside the “SAP

Service Reference” folder under the project file.

For running a GWPAM based solution you need to either have only one App.config file or

specifically load GWPAM config file as and when needed.

Manually remove /merge the App.config file

The developer can merge the extra settings inside the App.config file that is generated by

the GWPAM. Care should be taken that the keys remain unique and none of the sections are

overwritten. If the outer App.config is created by mistake or due to other reason and does not

contain any configuration then it better to delete it all together.

Explicitly load the App.config file

With the help of APIs provided with the GWPAM framework, you can explicitly mention the

path to the App.config that you want the GWPAM to read from.

The code snippet provided will help you do the same.

18

19

This concludes the presentation on Supportability features and Considerations for GWPAM.

www.sap.com

© 2013 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP

products and services mentioned herein as well as their respective

logos are trademarks or registered trademarks of SAP AG in Germany

and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves

informational 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 ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

products and services are those that are set forth in the express

warranty statements accompanying such products and services, if

any. Nothing herein should be construed as constituting an additional

warranty. .