Safter Maskan

Delta Links and SAP Content Objects

2009-05-18T03:35:00.001-07:00

Delta Links and SAP Content Objects

Use

SAP objects are contained:

● Within the initial content provided with the portal. See Standard Initial Content.

● Within the business packages delivered by SAP that can be imported into the portal from the Portal Content Portfolio area in the SAP Developer Network (SDN) at www.sdn.sap.com.

The content objects provided by SAP (the initial content) can be found in the Portal Catalog in the following folder: Portal Content/Content Provided by SAP. Objects in this folder belong to the SAP namespace. The ID of the object contains one of the following prefixes:

● com.sap*

● com.sap.pct*

Do not make any changesto objects in the SAP namespace. If you do so, and a new version of the object is then imported into the portal, the object will be overwritten and you will lose all your changes.

...

Features

You have two possibilities for reusing objects provided by SAP and adapting them to your needs:

1. Scenario 1: You use the SAP objects that are delivered without a namespace.

2. Scenario 2: You create a delta link from an SAP object.

Activities

Scenario 1: You use the SAP objects that are delivered without a namespace

As described above, the objects in initial content belonging to the SAP namespace can be found in the Portal Catalog in the following folder: Portal Content/Content Provided by SAP.

You may not use or change these objects.

In parallel, there are copies of these objects in two other folders of the Portal Catalog: Portal Content/Portal Administrators and Portal Content/Portal Users. These folders contain for example:

● the administrator roles

● the standard user role

● the preconfigured page for the navigation areas in the portal

You can change all the objects in these two folders as needed by opening them in the Portal Content Studio for editing. Since the objects are not in the SAP namespace, you can use or change the objects.

You can use the objects in these two folders because they have a delta link relationship to the original objects in folder Content Provided by SAP. The initial content is provided by SAP together with the delta link relationships.

Note the following for the administrator roles:

● If you want to change the preconfigured administration roles, always use the administrator roles in the folder Portal Content/Portal Administrators.

● If you want to assign administrator roles to users, always use the administrator roles in the folder Portal Content/Portal Administrators.

Scenario 2: You create a delta link from an SAP object

You can derive an object from an SAP object with a delta link. You assign the derived object a name in your own namespace. You do this by copying the SAP object from the Portal Catalog and inserting it elsewhere in the Portal Catalog as a delta link. See Creating Delta Links.

In this way you create a reference to a delivered object that is not part of your own namespace (the source object) from an object belonging to your own namespace (the target object).

You can now change "external" contents within your own object by working on the reference object, and not on the original object delivered by SAP. The system records the changes that you make (such as deleting folders or adding folders to role hierarchies) as a delta link.

Result

In both scenarios the advantages of the delta link method become apparent:

● You can make changes to a target object (delta link object) and the source object remains unchanged.

● If the source object is reimported into the portal at a later time with changes to its contents, these changes appear automatically in all the derived target objects.

● When you import the content object again, your changes to the derived (target) object are retained.

How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)

2009-05-18T03:28:00.000-07:00

How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)

Applies to: SAP NetWeaver Developer Studio (NWDS) version 2.0.7 or 7.0.11 and SAP Web Application Server (WAS)

version 6.40.

Summary

SAP NetWeaver Developer Studio is an integrated environment for the development of J2EE-based, multitiered
business applications. It is based on open-source Eclipse, providing an open and extensible
development environment using Java and Web services. SAP has enhanced the standard Eclipse
functionality with a comprehensive set of design, construction, and maintenance tools that cover the full
software life cycle.
SAP Web Application Server is an SAP delivered homogenous infrastructure for ABAP-based applications
as well as for J2EE-based applications. All existing business objects and interfaces can be used the same
both in the Java and ABAP environments.
This article is a simple guide to connect WAS from NWDS before going to build or deploy any NWDS
application to WAS from NWDS.

Table of Contents
Applies to:..................................................................................................................................1
Summary ...................................................................................................................................1
Author Bio..................................................................................................................................1
Abbreviation Used.......................................................................................................................2
Server Requirements ..................................................................................................................2
Client Requirements...................................................................................................................2
Client Configuration....................................................................................................................2
Prerequisite .............................................................................................................................2
Check the Message Server is running from the command........................................................2
Check your machine has installed with NWDS.........................................................................3
Open the NWDS......................................................................................................................3
Configuration Steps.................................................................................................................3
Check NWDS is able to connect to remote WAS J2ee Engine.....................................................4
Related Content.........................................................................................................................5
Disclaimer and Liability Notice.....................................................................................................6

Server Requirements

a. SAP WAS 6.4 installed and configured on local or remote machine.
Client Requirements

a. Install J2sdk 1.4.2_15
http://java.sun.com/j2se/1.4.2/install.html

b. Install NWDS 7.0.11

Client Configuration

Prerequisite

i) WAS Message Server Host Name (say, hdklerpsdf013)
ii) WAS Message Server Port (say, 3601)
Check the Message Server is running from the command
C:\>telnet hostname port (say, C:\>telnet hdklerpsdf013 3601)
If the client has no access to access the service or WAS message server is not running or any
network related problems exists then a message will appear at the command prompt
“Connecting To hdklerpsdf013...Could not open connection to the host, on port 3601: Connect failed”
If server is running and you can access the server then a blank screen opens when you execute the
above command.
How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 3
Check your machine has installed with NWDS
From control panel see if NWDS is installed.
Open the NWDS
From Startup/Installed directory open NWDS.

Configuration Steps

i) From NWDS menus go to Window 􀃆 Preferences. When you click on Preferences then the
following window opens.
ii). Select SAP j2EE Engine from the Preferences left side configuration tree.
iii) Select the first radio button (SAP J2EE engine is installed on remote host) at the right side of
the window.
iv) Put the Message Server Host name and port into the required place. Then apply the value you
entered.
How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 4
[N.B. If you have WAS J2EE engine installed on your local machine then configure it locally selecting
the second radio button (SAP J2EE engine is installed on local host) same window and put the
appropriate values.]
Check NWDS is able to connect to remote WAS J2ee Engine

a. From NWDS menus go to Window􀃆 Show View 􀃆 J2EE Engine and click on J2EE Engine.
b. Now the following window displays at the below (default position) of the NWDS
c. Now click on the instances, dispatcher, SDM, server0 on the left side tree and get details status of
the instances on the right side of the J2EE Engine window. If you see every instance is greencolored
then everything is configured. Now build your application and deploy on the remote server
from NWDS.
How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 5
Related Content
SAP NetWeaver Developer Studio
SAP Web Application Server Overview (on thespot4sap.com)
WAS with ABAP and Java
How to Connect from SAP NetWeaver Developer Studio (NWDS) to Web Application Server (WAS)
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
© 2007 SAP AG 6
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces
and therefore is not supported by SAP. Changes made based on this information are not supported and can
be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods
suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of
this technical article or code sample, including any liability resulting from incompatibility between the content
within this document and the materials and services offered by SAP. You agree that you will not hold, or
seek to hold, SAP responsible or liable with respect to the content of this document.

Installing SAP NetWeaver Developer Studio Standalone Version

2009-05-18T03:26:00.000-07:00

1 Overview

Purpose

This document describes how to install the SAP NetWeaver Developer Studio as a standalone version. To install as part of the SAP NetWeaver Developer Workplace, see the installation guide Developer Workplace for SAP NetWeaver 2004s.
You can see the SAP NetWeaver installation guides at service.sap.com/instguides.
Platforms
You can install the SAP NetWeaver Developer Studio on:
● Windows 2000
● Windows XP

Web Browser
You require Internet Explorer 5.5, or higher.
Minimum Hardware Requirements
The SAP NetWeaver Developer Studio requires approximately 500MB disk space, 512MB RAM, and an 800MHz processor.
2 Installing SAP NetWeaver Developer Studio Standalone
Prerequisites
● Local administrator rights under Windows 2000 or Windows XP.
● Installed Java Sun SDK version 1.4.2 or higher.
If you do not have a Java SDK installed, download the installation from www.java.sun.com.
Procedure
...
...
1. From the root directory of the installation CD (or from whichever folder you copied the installation files to), double-click JDTsetup.exe.
2. In the SAP NetWeaver Developer Studio Setup Wizard - [Step 1 of 2] screen, choose Next.
3. Choose Browse to specify the folder where you want the SAP NetWeaver Developer Studio to be installed. To confirm, choose Install

SAP Deployment

2009-05-18T03:24:00.000-07:00

Deployment

Use

You use the Deployment tab to deploy new software packages with the Software Deployment Manager (SDM).The SDM takes you through the individual steps, from selecting the Software Component Archive (SCA) and the Software Deployment Archive (SDA), to actually deploying the software in the target directory.

Prerequisites

You have downloaded the software packages from a download area, or inserted a CD with new software packages in your CD drive.

Scope of Functions

The SDM supports you when you deploy software packages, and warns you about any possible inconsistencies caused by dependencies between different Software Deployment Archives (SDAs). It also tells you whether an SCA that you need to install has inconsistencies.

Select the archives that you want to deploy on the screen Choose SCAs/SDAs to Be Deployed.

To select SCAs/SDAs within your local network environment, choose Add SCA/SDA to Deployment List (Local File Browser). After the archive has been loaded, you see a list of information about the version, software type, number of dependencies, and the archive name.

To select SCAs/SDAs from the file system of the SDM Server, choose Add SCA/SDA to Deployment List (Server Side File Browser).

To remove the selected archives from the deployment, choose Delete SCA/SDA from Deployment List.

To toggle the display of information about the vendor and location, choose Show Additional Columns for Vendor and Location and Hide Additional Columns for Vendor and Location.

To display detailed information about an archive in a new screen, select an archive and choose Show Information about SDA.

Show Legend shows you the meaning of the icons displayed for this deployment step, in a separate screen.

In the Deployment Configuration area of the screen, which you can open or close with the arrow icons, you decide which archive versions are allowed to be deployed. You have the following options:

· Settings for Updating SCAs/SDAs

Ў Update deployed SCAs/SDAs that have lower component versions than the selected SCAs/SDAs only

With this option, you can deploy new archives only, or update existing archives with a newer version.

Ў Update deployed SCAs/SDAs that have the same or lower component versions than the selected SCAs/SDAs

With this option, you can redeploy existing archives. This overwrites the previous deployment.

Ў Update deployed SDAs/SCAs that have any version

With this option, you can deploy any archive, without its version being checked by the SDM.

· Handling in case of deployment errors

Ў Stop when the first error occurs

With this setting, the deployment terminates as soon as it encounters an error. Any deployments that have already been completed are retained.

Ў Skip deployment of SCA/SDAs depending on the erroneous deployment

With this setting, any archives that cause deployment errors are skipped. The SDM still processes the list of archives until the end.

Activities

The deployment of new software components is divided into several steps.

...

1. To select additional SCAs, or SDAs, choose Add SCA/SDA to Deployment List. To delete superfluous SCAs or SDAs, choose Delete SCA/SDA from Deployment List.

Choose Next.

2. The SDM determines the Deployment Action from the manifest data and displays the data in the archive list. The Repository Preview shows you how the SDAs are distributed in the SDM Repository.

Choose Next.

3. The SDM tells you that it is ready for deployment. Choose Start.

If an error occurs and you have to perform the deployment again, deployments that were successfully performed are not repeated.

4. A success message appears at the end of the deployment process. Choose Confirm to confirm the deployment.

See also:

· SDM Repository

· Undeployment

· Log Viewer

For more background information, see Software Deployment Manager and Working with the Graphical User Interface (GUI).

ESS: How to Add Custom Area Page to Overview page.

2009-05-09T02:13:00.000-07:00

Prerequisites:
This article does not details simple portal activities like creating iviews/pages. Hence some of the steps
have been described as ‘Add an iview/page’ without giving further details.

Step Wise Procedure:
The ESS page before adding new area is shown below.

Changing Ess & Mss screen fields (SAP)

2009-05-09T02:05:00.000-07:00

--------Introduction

This Howto section explains how to further check the fields settings through table T588M when setting up the Employee Self Services (ESS)

Source : SAP cookbook "T588M_ESS Cook Book" All rights SAP AG.

--------Steps

Maintain table V_T588M_ESS - Control of Screen Fields for ESS Scenarios

--------Examples

* Field control for ESS scenarios enables you to influence the appearance of screens dynamically. You can change screen field attributes during runtime. The system reads the instructions as to how this should be done from a Customizing table (T588M_ESS).

* For a long time it has been possible to change field attributes in master data dynamically (table T588M). Until now this has not been possible for ESS scenarios based on master data.

* Field control helps you use Customizing settings to tailor screens for ESS scenarios to suit country and customer-specific requirements. You do not need to create a completely new screen.

* Field control enables you to display a single screen in numerous layouts.

You can set up the screen field control with the help of view V_T588M_ESS.

To access this maintenance interface for the first time you must know the function group of the ESS scenario (subset). You can find the relevant function group with the help of the function module that processes the list screen and detail screen.

Function modules are assigned to the relevant transaction code for each scenario in the table T77WWW_SC.

You must enter a valid screen number on the detail screen of the editing interface. The view checks that the screen exists in the ESS function group you entered.

Controllable screen fields are displayed in the view and grouped together. For each group you can use radio buttons to specify that screen fields:

* Are hidden
* Receive the required entry field attribute
* Receive the optional entry field attribute
* Can be displayed as read-only

To enable you to define several different field controls for one screen, the view allows you to assign a variable key.

However, there must be a base entry for which the variable key field is in its original state.

To define a variable key you can specify a feature. The return value of the feature determines the variable key, which can be seen in one of the later entries.

The feature should be based on the structure PMESS.

To control an ESS screen field you must ensure that modification group 3 is assigned a value between 001 and 050 in the Screen Painter.

If you want screen fields to be able to be grouped together, you must assign them the same value for modification group 3.

In the corresponding screen flow logic you can use the class CL_HR_ESS_SCREENCONTROLER. For each screen you must generate an object from the class once.

If a table control is used on the screen it can be transferred to the class constructor. The constructor "freezes" the controllable columns in their original state to guarantee a defined initial status for the field control.

In many cases, it may be necessary for a screen's structure to be dependent on employee data or the selected subtype. Control is possible with the help of a feature that uses the structure PMESS. The feature returns a variable key, which identifies the entry in table T588M_ESS.

If you change the feature data the system detemines a new entry in table T588M_ES. To make this possible, the class provides the method init_pbo.

To change screen field properties you can call up the class method set_screen. You can call up this method from the application in two ways:

* In a loop over the table SCREEN for modifying normal screen fields
* In a loop over the column table COLS in table control

Then, in the flow logic, you must make a corresponding MODIFY entry: in the screen table for normal screen fields, or in the column table for table controls.
[edit]
Conclusion

This cookbook is quite useful as of release 46c, if not using the webdynpro.

If you are using the webdynpro, rather consider the following:

Unfortuanetly all these services are obsolete with the new Webdynpro services.

If you are using webdynpro based ESS then you can use T588MFPROPS and T588MFPROPC.

->Regarding table T588MFPROPS and T588MFPROPC: These tables define properties (e.g. "Required Field") of fields used in a service. These properties are used in the background at the Business Logic stage of verification (i.e. after a user presses Next on the Detail screen); they do not control appearance or behaviour of fields on the Detail screen itself.

* Table entries for T588MFPROPS are pre-delivered.
* Table entries in T588MFPROPC can be added for country or customer specific changes to standard behaviour.

Theorically, this table is NOT ESS specific.

Through the configuration, It is not possible to add or remove fields from the screen. You can only make the fields mandatory or optional. If you select the unused field, the changes to that field will not be considered.

I would go for enhancing my own FM and assign it in T77WWW_SC