Special Consideration in Migration from NetWeaver 7.0 to NetWeaver 7.3

Special Consideration in Migration from NetWeaver 7.0 to NetWeaver 7.3

Composite Application Framework (CAF)

• Need to be migrated during design-time before migration run time systems

Web Dynpro Applications

• Only need to be rebuild in new framework and redeploy

Portal Applications

• Migration has to be done explicitly due to different deployment format.
• Packaging format no longer PAR or portal archive.  New packaging supported is WAR or web archive.  These are package further in an EAR or enterprise archive.  SAP has a tool (PAR Migration Tool) to convert old transport packages to new format.

Java Data Objects

•  Need to follow a specific path of compilation and redeployment

What’s new with NetWeaver Portal 7.3?

What’s new with NetWeaver Portal 7.3?

• Enterprise Workspaces 1.1 personal productivity and collaboration solution
• Web Page Composer is part of the portal
• Ajax Framework Page
• smooth presentation and rendering activities
• asynchronous data communication between the portal server and client
• Javascript based API to support data exchange and support UI
• Wiki’s and Forums as add-on
• Web services and APIs to interface portal with other 3rd party portals or solutions

What’s new with NetWeaver 7.3?

• Previous NetWeaver stack ran on Java 4 and this one runs Java EE 5
• SAML 1.1\2.0 – New security standard that enables cross-platform and cross-domain SSO and federation capabilities.
• JSR 168/286 – Support for Portlet specifications
• WSRP 1.0 – Support for Web Services for Remote Portlet Development.

Seven Steps to Reset SDM Password

For Windows -

1. Go to command prompt.

2. Go to folder \usr\sap\DVEBMGS01\JC<instance>\SDM\program (where SDM, RemoteGui.bat exists). Please note that DVEBMGS01 refers to dual stack systems (ABAP+Java).  For single stack systems, it would be \usr\sap\<SID>\JC<instance>\SDM\program.  The path in Unix is the same.

3. In MMC, Goto J2EE processes. Right click on SDM and “disable process”

4. Type – sdm jstartup “mode=standalone”

5.  Type – sdm changepassword “newpassword=initpass”

6.  Type – sdm jstartup “mode=integrated”

7.  Now goto MMC and start SDM Your new password to get in to JSPM or SDM is initpass

8.  Re-start the SDM server

Changing the Secure Store Password in Config Tool

I was trying to deploy to the NetWeaver J2EE using NetWeaver Developer Studio (NWDS) to software deployment manager (SDM), and I got the error below. SDM uses the administration password set in the secure store. The administrator password had recently changed and it was not updated in the secure store.

Error:

“Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654. com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.”

Steps to change secure store password:

1. Acccess Config Tool at the the following path:  C:\usr\sap\<SID>\JC<instance>\j2ee\configtool\configtool.bat
2. It’s best practice to export the database. Save as ServerCfgExport.zip or choose your own name.  This is insurance.  You will be able to re-import an old configuration and put the system in the prior state.
3. Navigate to the secure store.  Check the snapshot below.
4. Change the password for admin/password/<SID>

Backing up the J2EE Config Database

It is best practice to backup the NetWeaver J2EE Engine Config database before you do any changes to it.  Here’s how to do it.

1. Acccess config tool at the the following path:  C:\usr\sap\<SID>\JC<instance>\j2ee\configtool\configtool.bat

2. Click File and Export DB

3. Take the default name of ServerCfgExport.zip or create your own.

4. Click OK.

5. Click Ok, if you made any changes to the config, you will have to restart the J2EE engine

How Can I Access System Information?

Here is the link to the system information of your WAS Java server.  This includes software component information, service pack level and version.

Activating SAP Super User

SAP* is the SAP super user.  It is activated in cases where an administrator has forgotten the Admin password and system is using Java user management engine (UME).

1. Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat. 
2. Switch to configuration mode by clicking on “Pencil” icon
3. Navigate to cluster_data — server — cfg — services
4. Click on Property sheet of com.sap.security.core.ume.service
5. Select properties:
   ume.superadmin.activated = True
   ume.superadmin.password = <password>
6. Save and restart Java Engine.
7. Now login with user id sap* and password <password> at  http://<host>:<port>/useradmin/index.jsp or Visual Administrator
8. Search for Administrator user in the user store
9. Search for Administrator user and reset its password
10. Now deactivate SAP* by following above steps except for setting ume.superadmin.activated as False.  You won’t be able to use any other user besides SAP* until you deactivate this feature.   As always back up the config database and restart the server when appropriate.

Creating JCo Destinations

Different business packages require different JCo Destinations to be set up.  ESS and MSS has its  own JCo’s.  BI dashboards have their own.  Custom applications have custom JCo’s.  Through the JCo’s, data is passed between the Portal and the source system like ECC.  In the case below, we are configuring the SAP_R3_Financials for business data and SAP_R3_Financials_MetaData for meta data.  One is created for the business user and the second is created for the metadata user.

Creating SAP_R3_Financials JCo.

1. Enter Client and J2EE Cluster under the General tab

2. If your connecting through the back end through SSO, then select User Definition to be SSO.  Otherwise, enter the user id and password of the business user.

3. Enter the message server, system name and logon group under  the Connection tab 

Creating SAP_R3_Financials_MetaData JCo.

The meta data connection is similar to before except for the user.  User is usually service user.

Creating a Model Using NetWeaver Developer Studio

One of the basic steps in creating a web dynpro is to create a model.  In your web dynpro, click on Models and select Create Model from the context menu.

 In this case, let’s get data through a BAPI call to the backend.  In SAP, your backend system can be ECC, BI, CRM, etc.  For a BAPI, pick Import Adaptive RFC Model.

Enter a Model Name, Model Package, and the logical system name fo model data and metadata.  Ultimately, these JCo Destinations will be configure in the NetWeaver Portal.

Specify the host name, system number, client and user information for the SAP backend system.  This information will be used at development.

 Search for your RFC by putting BAPI* in the Function Name window.

Let’s refine it further and pick BAPI_SALESORDER*.  For this example, let’s pick BAPI_SALESORDER_GETLIST.

A new model have been added that consists of the RFC BAPI_SALESORDER_GETLIST

Showing Properties or Input Variables in BEx Analyzer 7.0 Reports

1. Select an empty cell.

2. Click on the “Insert Text” button on the BEx Design Toolbox

3. In the design mode, a textbox icon will appear.  Click on this icon to set the properties.

4. Select the properties among the many available to you.