As a system, the SAP J2EE Engine consists of three logical layers:
- SAP Java Enterprise Runtime – comprises low-level modules that provide functions such as class loading, cluster communication, persistent configuration data management, and so on. For more information, see SAP Java Enterprise Runtime.
- Pluggable components – consists of interfaces, libraries and services components that provide various runtime functions and programming APIs. For more information, see Pluggable Components.
- Applications layer – refers to the applications that are deployed and run on the SAP J2EE Engine. For more information, see Applications.
Read more…
What is the session? Why we need it?
As the HTTP is a stateless protocol, the web server can response to the request from each client, but it cannot remember previous requests from the same client. It is difficult to build the web site such as shopping on-line that requires to distinguish from different clients to retain contextual information. The session concept is involved to solve there issues.
In session management whenever a request comes for any resource, a unique token is generated by the server and transmitted to the client. We can also say that the process of managing the state of a web based client is through the use of session IDs. Session IDs are used to uniquely identify a client browser, while the server side processes are used to associate the session ID with a level of access.
Generally speaking, there are three methods to implement the session concept:
Read more…
Why need JDBC Data Source?
In the J2EE development, the application needs to persist business data into a database. In SAP world, the data can be stored in the ABAP database through RFC calls. Another data repository is the Java database through the SAP Java persistence infrastructure.
During the SAP server installation, a default datasource is set up and intended to be used by all the SAP applications. You can create a new datasource aliases for your application in order to use the default datasource. Besides, you can create a new datasource in order to have a application specific configuration.
How to Administrate JDBC Data Source?
Read more…
SAP offers its own JVM – SAP JVM. The SAP JVM is a Java Virtual Machine for robust, scalable and highly supportable application servers, which can be used in conjunction with SAP products. It implements the Java SE 5.0 standard, offering a strong and reliable foundation for the whole SAP Java stack. SAP NetWeaver 7.1 and higher version can utilize the advanced features of SAP JVM.
With SAP JVM, SAP doesn’t need to support the different behavior of third party JVM implementation. The SAP JVM now is the basis for all java applications running on the NetWeaver.
The SAP JVM comes with a complete set of tools, libraries and APIs to develop, deploy, run, and monitor Java programs in an application server environment. Below diagram shows the components that comprise SAP JVM.
Read more…
SAP delivers various types of program corrections with Support Packages as part of the software maintenance. Support Packages automatically correct a whole range of errors by downloading corrections into the SAP System. Two categories of Support Packages are available: ABAP Support Packages and Java Support Packages.
ABAP Support Packages
ABAP Support Packages contain corrections and updates for the ABAP components of the SAP system that were performed up to a certain point in time.Each Support Package is based on the previous one. If you want to import Support Package 10, for example, you must also import all previous Support Packages (1-9) in one Support Package queue. To import ABAP Support Packages, you use the Support Package Manager (Transaction SPAM).
Read more…
The database connection for SAP J2EE engine is created during the AS Java installation. The database user SAP<SID>DB, password and db server connection string is stored in the secure storage file, located at usrsap<SID>SYSglobalsecuritydataSecStore.properties in the installation folder.
These DB information as well as the default administrator user can be maintained using Config Tool (Execute <AS_Java_install_dir>configtoolconfigtool.bat). Start the Config Tool and select secure store. The configuration for the secure storage in the file system appears.
Read more…
Guided procedure is a workflow technology that allows SAP customers to build their custom process-based solutions to leverage SAP NetWeaver technical platform and combine existing UI and services to fully map business processes.
The disadvantage of guided procedure is there is no fundamental support of delegation functionality. In a realistic business scenario, this is a must-have functionality, because employee might be not able to response to immediately and want to delegate the task to other employees.
SAP GP provides a limited delegation function for the administrator and it is not convenient for the end user to use.
Read more…
Why need development namespace?
Development namespaces enable customers to develop R/3 enhancements and solutions without having to agree on naming conventions with third parties. Additionally, they can deploy their enhancements and solutions in any system around the world without the risk of name conflicts.
In the case of developments based on the SAP NetWeaver platform, you reserve namespace prefixes that span entire namespaces for your development objects. You use one of your own namespace prefixes to identify your own NetWeaver Name Server.
How to reserve a namespace?
The namespace can be reserved in SAP Service Marketplace at http://service.sap.com/namespaces. You should have special roles to perform these activities.
Read more…
Quick news from SAP SCN on the release of SAP NetWeaver 7.3.
The next major release of SAP NetWeaver, has been announced at TechEd Berlin.
SAP will publish more detailed information on the scope of SAP NetWeaver 7.3 on SDN soon. Ramp-Up participation: SAP NetWeaver 7.3 Ramp-Up is planned to start Q4/2010. Ramp-Up is SAP’s standard process for launching its solutions on the market. For more information please access SAP Ramp-Up (SAP Service Marketplace login required) and look for SAP NetWeaver 7.3 underneath “Recruitment open for Upcoming Ramp-Ups”. Customers interested in participating in SAP NetWeaver 7.3 Ramp-Up should contact their Account Executive. Please come back for more information.
Service-oriented architecture (SOA) is a blueprint for an adaptable, flexible, and open IT architecture
for developing services-based, modular business solutions. SAP makes it easy to adopt SOA –
enabling companies in diverse industries to quickly differentiate their businesses and optimize
processes in their business networks. SAP enables businesses to adopt SOA at their own pace as
part of their SAP solutions. At the heart of SAP’s open-standards approach to SOA is the web service.
SAP provides a set of tools to create, configure and monitor the web service. In this post, I would like to share how to expose a remote-enabled function module to a web service.
1. Create a Service Definition
With the inside-out approach, independent function modules that were implemented as RFC-enabled function modules, as function groups, or as BAPIs are provided as a Web service. The Web service can be used across the entire Internet using standard protocols and can easily be added to any development environment.
Read more…