Java EE in SAP Technology

Tags

Java, Java EE, SAP Web AS Java

The use of Java EE in SAP technology has the following advantages for SAP NetWeaver Application Server:

• The open integration architecture SAP NetWeaver integrates perfectly into the openness of Java EE.
• Java EE is further proof of the strategy of platform-independence pursued by SAP.
• The Java EE Connector architecture allows standardized integration of external applications.
• Web Services technologies are supported directly by Java.
• The quickly-growing Java community provides simple access to experienced developers.

Advertisements

Terms in SAP Web AS Java

Tags

Java, SAP Web AS Java

If you are new to SAP Web AS Java, these are the familiar terms that being used.

Java is an object-oriented and platform-independent programming language that has spread across many areas.

Java Runtime Environment is an independent platform environment to run Java program

Java Programs consist of application and applet. Java applications are computer programs with the full functional range also provided by other programming languages. The term applet essentially means “little application”. It usually means a Java applet, a small computer program that runs in a Web browser and is written in the Java programming language.

Java virtual machine is a model of a processor (which often does not exist as real hardware) and the associated system architecture. It is a computer program that emulates a processor. see graphic below.

A Java Development Kit (JDK) is required to write platform-independent Java programs. The Java Development Kit includes the software required to create and test Java applications and applets, the packages with the Java classes that are part of the basic configuration, and the online documentation

Java Standard Edition (Java SE). The standard edition is the normal software environment and defines the Java™ SE Development Kit (JDK). This includes the Java SE Runtime Environment (JRE).

Java Enterprise Edition (Java EE). The enterprise edition builds on the JDK and integrates additional packages such as Enterprise JavaBeans (EJB), servlets, JavaServer Pages (JSP), Java Mail API, and Java Transaction Service (JTS). The Java EE SDK (Software Development Kit) includes the Sun Java System Application Server and requires a JDK.

Java Micro Edition (Java ME). The micro edition is a small runtime environment for small devices such as Personal Digital Assistants (PDAs) or telephones.

Enterprise Java Beans is a package of application logic components in accordance with Java EE specification.

EJB Container is a location to execute Enterprise Java Beans which is part of Java EE application server.

Web Container is a part of Java EE Application Server which Java Server Pages and Java servlets are executed in.

Java Server Pages (JSP) are a technology developed by Sun, which essentially allow the simple dynamic generation of HTML and XML output for a Web server.

High Availability in Solman

Tags

solman

There are no general High Availability (HA) requirements for the SAP Solution Manager. High-availability applications allow you to maximize downtime security and minimize downtimes. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic. At SAP, high availability is always focused on business applications and their related components. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure, such as the operating system, database, and hardware. Collaborative business can give you a competitive advantage. This means integrating existing heterogeneous system landscapes to include business partners, customers, and suppliers. You may also have requirements of your own, depending on the availability requirements of the implemented IT management processes.

Further Documentation Tool	Link
Service Marketplace – High Availability	http://service.sap.com/ha
Help Portal	http://help.sap.com/ → SAP NetWeaver → SAP NetWeaver 7.0 including Enhancement Package 1 → <language> → SAP Library → SAP NetWeaver Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → High Availability → SAP High Availability documentation

Role assignment question

Tags

roles, user

Question :

You have to assign a role to a user.YOu can add the role to user in su01 OR you can add the user to role in pfcg.which method is preferable?why?

Answer :

It depends on the requirement. If you need to maintain role in one user, it is more efficient that you use SU01 then assigned many roles. If you need to maintain many users within one role then you should use PFCG.

If you need to maintain mass user, I would suggest you to use SU10.

Specify Logon Group

Tags

SMLG, solman

Specify Logon Group

You can specify logon groups for the SAP Solution Manager system. The Resource Manager then only runs extractors in the instances in the logon group.

Prerequisites

You have called the SAP Solution Manager Management work center.

Procedure

1. Choose the Landscape view.
2. Select the system.
3. Choose Extractors.
4. Go to the Configuration tab.
5. Choose Change.
6. Under Logon Group for EFWK, choose Create. You go to the transaction SMLG.
7. Create a logon group.
8. Exit the function. The logon group appears under Logon Group for EFWK
9. Select the logon group.
10. Choose Set.

Niping Syntax

Tags

network interface, NI, NIPING, SAP, SAP Protocol

Question : what is the syntax of niping command?

Answer : to get an idea of using niping command you can type niping without parameter.

Niping

This article is to answer guest question about using niping. Thanks to vinvk for the question.
Niping is a testing program developed by SAP to enhance TCP/IP and UDP layer function. Network Interface (NI) is used by SAPRouter and all SAP programs to provide independency of various communication. The enhanced TCP/IP and UDP Protocol is called SAP Protocol which provide one field length more and error information. This program simply send request to the server, then read the reply from server. Niping mostly uses to test connection to SAP server with or without SAP Router. Niping also provides enhancement communication through the firewall or proxy server.

Niping syntax

Example niping command (with or without SAProuter),
host1 : saprouter -r //start saprouter in host1
host2 : niping -s //this will emulate a test server
host3 : niping -c -H host2 //this will test connection to host2 without SAProuter
host3 : niping -c -H /H/host1/H/host2 //this will test connection to host2 with SAProuter

niping -t //this is for self test which will display a result *** SELFTEST O.K. *** if connection OK

VMWare Server things

Tags

bootable, Server, VMware, Windows

VMware

Finally, I’m able to run VMWare on my Notebook. I knew this software for long time, but for VMWare Server I’ve just installed it last night. Well, I encountered some problem with this installation, started with creating bootable Windows Server 2003 cd, then VMWare cannot detect my guest OS Win Server 2003 x64 bit. If you face this issue, may be solution below will help you.

New BR*Tools Feature in SAP Netweaver 7.1

Tags

BRARCHIVE, BRBACKUP, BRCONNECT, BRRESTORE, BRSPACE, BRTOOLS, Netweaver 7.1, RMAN, SAP

In SAP Netweaver 7.1 you can find the following features of BR*Tools :

1. Verification of database and archive log files with RMAN ( BR*Tools 7.00 patch 22 ) which affects :
   o BRARCHIVE -w|-verify use_rmv|first_rmv|only_rmv
   o BRBACKUP -w|-verify use_rmv|only_rmv
   o BRRESTORE -w|-verify use_rmv
2. Support for Oracle Data Pump like export and import ( BRSPACE patch 17 ) which affects :
   o BRSPACE -f tbexport
   o BRSPACE -f tbimport
   o Special Import and Export Functions
3. Administration of Database statistics using BRSPACE ( BR*Tools 7.00 patch 24 ) which affects :
   o BRSPACE -f mstats
4. RMAN support for split-mirror and standby-database backup, and support for split-mirror backup of a standby database which affects
   o RMAN-Relevant Profile Parameters
   o Split Mirror Backup
   o Split Mirror Backup: Software Configuration
   o Standby Database
   o init.sap parameters: backup_type, standby_db, disk_copy_cmd, post_shut_cmd, post_split_cmd, pre_shut_cmd, pre_split_cmd
5. Support for RMAN save sets with disk backups, which affects the following section :
   o disk_copy_cmd
   o rman_compress
6. Automatic handling of Oracle 10g RAC Cluster Services. This will affect db_services.
7. Improvements to handling of database statistics.
   Update Statistics
   o Sample sizes for update statistics
   o BRCONNECT -f stats
   o init.sap parameters: stats_bucket_count, stats_dbms_stats, stats_sample_size, stats_table
8. Improvements to table reorganization and index rebuild, which affects the following section :
   o Reorganization
   o Reorganizing Tables with BR*Tools
   o Rebuilding Indexes with BR*Tools
   o BRSPACE -f tbreorg -r|-sortind -m|-mode online|offline
   o BRSPACE -f idrebuild -m|-mode online|offline
9. Various new options and parameters, which are :
   o BRCONNECT : -f dbstate, -f dbstart, -f dbshut, -f crsyn, -f chpass, -f check
   o BRRESTORE -i|-interval
10. Flashback database
    o BRSPACE: -f tbreorg, -f idrebuild, -q|-query
    o init.sap parameters: stats_special, check_cond, db_services, rman_compress, man_maxcorrupt
11. Abort of archive, backup, or restore which affects :
    o Abort of archive, backup, or restore
    o brarchive -g|-abort
    o brbackup -g|-abort
    o brrestore -g|-abort

Mostly this all feature is already covered in BRTOOLS 7.00  as of patch 31 or BRTOOLS 7.10 as of patch 7 and may vary depends on the feature. When I’m writing this article, the latest patch for version 7.00 is 41 and the latest patch for version 7.10 is 31. For more details BRTOOLS correction you can visit SAP Notes 1060305 – Correction in BR*Tools version 7.10 and SAP Notes 849483 –  Correction in BR*Tools version 7.00.

Important Log Files for Portal Application

Tags

Application, Java, logs, Portal, SAP

If you run a Portal application based on SAP Web AS, you may find an error on your running process. Mostly the errors are logged into a log files of Java server process. A Portal application usually identified by prefix http://<hostname&gt;:<port>/irj/… Here’s the important log files location :

1. <drive>:\usr\sap\<SID>\DVEBMGS<inst_no>\j2ee\
   cluster\serverX\log\defaultTrace.xx.trc
2. <drive>:\usr\sap\<SID>\DVEBMGS<inst_no>\j2ee\
   cluster\serverX\log\applications.x.log

X: server process number, start from 0,1,2 .. X
xx:default trace number which will be overwritten between 0-19 by default. the most updated can be displayed with the latest timestamp in OS.

The thing is not all people can read what is inside the log files since this is generated roughly from Java process, but those texts are very helpful to predict the portal application. The logs also display some Java class which is used by application. for example :

#1.5#001185E9BA0D0090000031F90000524C00046B19DB1815A0#1243658700982#com.sapportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#sap.com/irj#com.sapportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0384ffffffd20071ffffffb2]#n/a##0ff0c3b04a1111deb8c3001185e9ba0d#Thread[ThreadPool.Worker1,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Exception occured during garbage collection: com.sapportals.wcm.repository.manager.cm.persistence.PersistenceException: SQLException: Cannot change transaction isolation during distributed transaction and when the connection is shared. DataSource name: “SAPSR3DB”, current isolation level is “TRANSACTION_READ_UNCOMMITTED”, new isolation level is “TRANSACTION_READ_COMMITTED”.#

Yes, of course you need to practice how to solve the issue. There will be a hundreds or even a thousands of variation of the error. Well , prepare your time to learn then 🙂

RZ10 – Character Limitation on Profile Import

Tags

Import, Profile, R/3, RZ10, SAP

I tried to import profile after system refresh a while ago. I just noticed that import profile character entry is limited. As far as I’m involved in SAP Basis consultant, I never experience a problem when importing an instance profile in RZ10. Before I show you where the character limit entry reside, here’s the procedure how I import a profile:

1. Run transaction RZ10.
2. Write down the profile name in Profile
3. Click Import Button (F8)
4. If you receive a warning like ‘First maintain management data‘. Click continue.
5. Fill in the necessary data, Activation in operating system file name and name of reference server for profile parameter check.
   
6. Click on Copy Button
7. Distribute to instance.
8. Save.
9. Profile has been imported.

Now, when you look in the activation in operating system file name field, you will find that it point to physical file which is in Operating System directory. If you are using local directory as in the picture above, this should be no issue on character limit. But if you are using shared directory which has long character name, like for example : \\saphostr3app1\sapmnt\DEV\SYS\profile\START_DVEBMGS00_SAPHOSTR3APP1, you will see as below picture:

When you save this setting you will find your profile file name become START_DVEBMGS00_SAPHO . The character limit is likely 60 character allowed. So just you aware about this limit, you can manage the profile name to a better looks. 🙂