SAP Installation number is a 10-digit number supplied by SAP. You receive the installation number as part of the installation package. The number is printed on the "Request Fax License Key" form.
SAP has stated that they recommend one installation number per SAP product landscape. For example, in a typical R/3 landscape where you have a development, QA and production system. This would all be defined and registered under one installation number. If you then have developers who have registered developer keys (developer keys are defined for and map to a SAP installation number) then that developer key will work in all of the systems defined for that landscape. That means that a developer key available in the development system would then also work in the production system. The developer will only have to supply it once per SAP instance. This also applies to SAP access key(object key) which is used to modify SAP standard programs.
Below link explains SAP installation number, license key, developer key perfectly.
Installation SAP Numbers, SAP Keys, SAP License number
SAPconnect provides a standard interface for external communication, which supports sending using telecommunication services, such as FAX, text messages (pager/SMS), Internet mail and X.400, as well as sending to printers and between different SAP Systems.
Read more…
In my previous post, I have explained what the DataSource is and how SAP deal with it. In this post, I would like to share more information about the DataSource.
The default JDBC drivers are delivered in library component: com.sap.portal.jdbcdrivers. You can find a list of JDBC driver library for each DBMS – P9sybase.jar, P9db2.jar, P9oracle.jar, P9informix.jar, P9sqlsever.jar.
You can add your aliases in the DataSource definition. Aliases are alternative names that are used by the application components when they look up a DataSource object. Below figure shows the aliases used by SAP standard applications.
Read more…
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…
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…
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…
Package, application component and software component are all used to organize SAP repository objects. In order to identify different purpose of repository objects, we assign the repository object to the package.
The package will then assign to a surrounding package and it will also assign to a application component, software component. Below screen shot shows the relationship below them.
Application component classifes the package from the functionality point of view. Like BC (basis component), AP (application component) and SD (sales and distribution). While software component is involved because of the distribution of the SAP software. For example, there are SAP_BASIS,SAP_ABA,SAP_APPL and etc. There is a special software component named HOME which content is delivered by the customer.
Change request is used to organize the change of repository objects and transport them to other systems.