The SAP NetWeaver Business Client (NWBC) is a new, desktop-based SAP integration platform that provides end users with a seamless integration of classic SAP GUI-based transactions and new applications developed in Web Dynpro. Existing browser-based SAP applications can also be integrated.
Click here for SAP Help on NWBC
SAP GUI for Java 7.20 has now been released and is available from ftp://ftp.sap.com/pub/sapgui/java/720
Please leave your user experience reviews and comments below.
The TMS Test tool for Business Objects can be invoked using the SAP Transaction code: /n/SCMTMS/BO_TEST
Please do take note of the Disclaimer though:
This transaction is for SAP internal use only.
It is used by SAP support colleagues.
Do not use this transaction for business.
Incorrect handling may result in unwanted
manipulation of business data.
Continue anyway?
It doesn’t seem to be released for any productive use at the moment.
Following on from my previous post: SAP Gui for JAVA on a Linux system
Download:
SAPGUI for Java from ftp://ftp.sap.com.
Install process:
–> Logon as root
–> Start Terminal –> type java -jar PlatinGUI-Linux-xxxx.jar (Check the file name)
# Default Install will install on /opt folder (probably /opt/SAPClients folder)
Configure SAPGUI for Java
Change to install directory and run ./guilogon (usually /opt/SAPClients/SAPGUI700rev1/bin )
Click New
Enter Description, click advanced
Check Expert Configuration
Enter the server details, connection string.
For load balancing use: conn=/M/(IP_Address_of_Message_Server)/S/36(system_number)/G/(name_group) or
conn=/H/(IP_Address_of_Message_Server)/S/32(system_number).
That’s it, you’re ready to rock n roll! You could ditch your windows box if this works for you! 
Part 1: Prerequisites:
JRE (Java Runtime Environment) from SUN Microsystems (http://java.sun.com).
If you need to install the correct java version:
1) Download the jdk-6-linux-i586.bin from http://java.sun.com to the desktop
2) chmod +x jdk-6-linux-i586.bin
3) .\jdk-6-linux-i586.bin
4) mv jdk1.6.0 /usr/lib/Java6
5)
update alternatives –install “/usr/bin/java” “java” “/usr/lib/Java6/bin/java” 1
update alternatives –set java /usr/lib/Java6/bin/java
update alternatives –install “/usr/bin/javac” “javac” “/usr/lib/Java6/bin/javac” 1
update alternatives –set javac /usr/lib/Java6/bin/javac
update alternatives –install “/usr/bin/javaws” “javaws” “/usr/lib/Java6/bin/javaws” 1
update alternatives –set javaws /usr/lib/Java6/bin/javaws
update alternatives –install “/usr/bin/apt” “apt” “/usr/lib/Java6/bin/apt” 1
update alternatives –set apt /usr/lib/Java6/bin/apt
6) Test the installation
java -version
javac -version
ant
apt
To check the JVM version just go to: http://www.java.com/en/download/installed.jsp
To Test Virtual Machine: http://www.java.com/en/download/help/testvm.xml
Download:
SAPGUI for Java from ftp://ftp.sap.com.
What is SAP?
Understand the SAP Business Suite
Contents:
If you want to stop users from logging in from multiple machines at the same time, use the instance profile parameter: login/disable_multi_gui_login
Go to Transaction RZ10
–> Select the Default Profile
–> Click radio button for Extended Maintenance
–> Clicck Add then type: ‘login/disable_multi_gui_login’ in the parameter box.
–> Value *
However if you want particular users to be excepted from this rule you could set up the parameter: ‘login/multi_login_users’
The users against this parameter will be allowed multiple logins. This applies to dialog logon type only. It does not apply to system logons that occur using the Remote Function Call (RFC) or to logons via the Internet Transaction Server (ITS).
to prevent user from multi login, you can put a parameter in the Instance Profile to prevent them from doing so.
Transaction RZ10–> Instance Profile–> Extended Maintenance
Use the ‘login/disable_multi_gui_login’ Parameter.
Enter User name as the value.
You can specify the list of Excepted Users for Multiple Logons using Parameter:
“login/multi_login_users”
Note: This function applies to dialog logons only. It does not apply to system logons that occur using the Remote Function Call (RFC) or to logons via the Internet Transaction Server (ITS).
Go to transaction SM37
Select the job you want to debug
In the command box type JDBG and press enter
Why object locks?
The locks are used in sap to prevent concomitant change of an object by two developer.
The enque work process manages the locking system. The lock entries for data to be processed in lock table which is maintained in main memory.
Various Lock Modes in SAP
Shared Lock (S):
Several users can access the locked data at the same time in display mode.
Requests for further shared locks are accepted, even if they are from other users.
Exclusive locks are rejected.
Exclusive lock (E):
The locked data can be displayed or edited by one user only.
Requests for either another exclusive lock or a shared lock are rejected.
Optimistic Lock (O):
An optimistic lock can be set if the data is displayed in change mode and the lock behaves like a shared lock if there are access collisions. But if the data is changed, the optimistic lock converts to an exclusive lock. 0ptimistic locks on the object then become invalidated. It can therefore be possible that the conversion fails, if beforehand another optimistic
lock was converted. In such cases the use of optimistic locks is only beneficial, if the probability that the data will NOT be changed is high.
Exclusive but not cumulative lock (X):
Exclusive but not cumulative locks can only be requested by the same transaction once only.
All further lock requests are rejected.
Youtube video on how to install the NetWeaver 7 (ABAP Stack only)
Powered by WordPress