Compatability of J2EE and ABAP Editions

Are these two sneak preview editions (Java Edition and ABAP Edition) compatable such that they both can be installed on the same XP system?
Presumably the Full edition which is not yet released will provide for a proper J2EE add-in installation.
But in the meantime, should it be OK to install the J2EE ABAP installations separately on the same system?
If yes, if there any special approach to the instance numbering that must be followed?
Thanks!

Thanks for those hints. I have installed the ABAP version (SID = NSP). After that the J2EE installation (J2E) is smart enough to figure out that instance 00 is already taken and uses 02 (without any input from the installer).
But ... unfortunately ... Load Java Database Content step just hangs. The last message in the log is an INFO message (see below). It seems like a lot of people have reported problems like this one.
So close!
INFO 2005-11-09 12:34:39
Output of C:\Program Files\JavaSoft\1.4.2_09/bin/java.exe '-classpath' './sharedlib/antlr.jar;./sharedlib/exception.jar;./sharedlib/jddi.jar;./sharedlib/jload.jar;./sharedlib/logging.jar;./sharedlib/offlineconfiguration.jar;./sharedlib/opensqlsta.jar;./sharedlib/tc_sec_secstorefs.jar;c:\sapdb\programs\runtime\jar\sapdbc.jar;C:/usr/sap/J2E/SYS/global/security/lib/tools/iaik_jce_export.jar;C:/usr/sap/J2E/SYS/global/security/lib/tools/iaik_jsse.jar;C:/usr/sap/J2E/SYS/global/security/lib/tools/iaik_smime.jar;C:/usr/sap/J2E/SYS/global/security/lib/tools/iaik_ssl.jar;C:/usr/sap/J2E/SYS/global/security/lib/tools/w3c_http.jar' '-Duser.timezone=Europe/Berlin' '-showversion' '-Xmx512m' 'com.sap.inst.jload.Jload' '-sec' 'J2E,jdbc/pool/J2E,C:\usr\sap\J2E\SYS\global/security/data/SecStore.properties,C:\usr\sap\J2E\SYS\global/security/data/SecStore.key' '-dataDir' 'C:/WAS/NW04SneakPrevJavaSP11/NWSneakPreviewSP11/SAP_NetWeaver_04_SR_1_Installation_Master_DVD__ID__51030843\IM01_NT_I386\..\..\SneakPreviewContent\JDMP' '-job' 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_COPY\ONE_HOST/IMPORT.XML' '-log' 'C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_COPY\ONE_HOST/jload.log' is written to the logfile C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_COPY\ONE_HOST/jload.java.log.

Similar Messages

MYSAPSSO2 cookie format in J2ee and ABAP - NW7

Hello
I installed NW7 with ABAP + Java with system id DV1. I was able to configure the java and abap to issue ticket and to be accepted by other systems (DV2).
If I login to the DV1 abap host using webgui url(integrated ITS), I am getting the MYSAPSSO2 cookie in the browser IE. With this I am able to login to DV2 j2ee and also to ABAP.
If I login to DV1 j2ee engine using the portal link, I am not seeing the MYSAPSSO2 cookie in the browser, but seeing JSESSIONID and with it still I am able to login to DV2.
My question : Is the JSESSIONID exactly equal to MYSAPSSO2 ? If not how can I make the DV1 J2ee to issue MYSAPSSO2 cookie ? Thanks.
SAPLearner

Hi
I am able to test and able to login to the other j2ee or abap system. But still not able to see the MYSAPSSO2 cookie issued by EP j2ee.
DV1 - NW7 SP12 system ABAP + J2ee(with portal on it)
DV2 - NW7 SP12 system ABAP + J2ee(with BI java)
I have exported DV1's java and abap certificate to DV2, made it trusted and the the connection is working.
When I login to DV1 j2ee using the url http://<DV1fullhostname>.com:52200/irj/portal
and getting the below in my browser
SignOnDefault=<windows id>; JSESSIONID=(DV1host_DV1_22)ID2068173650DB0050916542928689590End; SAPPORTALSDB0=urn%253Acom.sapportals.appdesigner%253Aframework%2526isPersonalizeMode%3Dfalse; GWS_AUTO_LOGIN=FALSE; AbxUserLocale=en_US_STAFF; PortalAlias=portal; saplb_*=(DV1host_DV1_22)613943650
With this above cookie I am able to login to DV2 j2ee http://<DV2fullhostname>.com:52500/nwa
or abap http://<DV2fullhostname>.com:8025/sap/bc/gui/sap/its/webgui
without any issue. In my browser I do not see MYSAPSSO2 cookie. Why is that?
My login stack in j2ee is defined as below.
 1. Evaluate ticket
 2. Basic login modele
 3. Create ticket
At the same time if I login to DV1 abap http://<DV1fullhostname>.com:8022/sap/bc/gui/sap/its/webgui I can see the cookie MYSAPSSO2 in the browser and still able to login to DV2.
Dont understand why my DV1 j2ee is not issuing MYSAPSSO2 cookie and issueing JSESSIONID ?
Appreciate your reply
SAPLearner

HA Solution with J2EE and ABAP Stack

In the Planning Guide is written that if DB2 data sharing is used, each application server connects to only one database server at any one time. There is a mechanism called sysplex failover that automatically redirects an application server to another database server in case of a failure. Sysplex failover is currently not available for a SAP J2EE system.
Lets assume that DB2 Member A fails. The ABAP Stack A is doing automatically a reconnect to DB2 Member B. The J2EE Stack A isn't able to do this. So what happens now with the new incoming http requests over the WebDispatcher/ICM? The J2EE Server on A is basically running still well, because only DB2 member A is down.
a) Does the MSG server realize that DB2 Member A is no longer available and informs therefore the WebDispatcher that incoming requests should be send to J2EE Server on machine B?
b) Doesn't the MSG server realize this situation and therefore the WebDispatcher will furthermore load balance the requests between J2EE server A and J2EE server B?
Thanks for your help and clarification?
Roger

Sorry, I haven't had time to answer your questions and unfortunately won't have in the forseeable future.
I'm using read only, so I do not know about RW, except that AD requires SSL and probably some settings on the AD server as well as the account you are connecting with.
BTW. The answer to the original question is that it is not possible to mix ssl and non-ssl connections to LDAP
Regards
Dagfinn
Message was edited by: Dagfinn Parnas

URLs Prefixes Customized on Both J2EE and ABAP Side

In the Diagnostic Support tool I am getting the subject error message and the following check error:
The URL for ABAP customizing table RSPOR_T_PORTAL: https://mycompany.com:1443 is not compatible with the URL for ABAP-based BI URL generation for BEx Web Applications 3.x (function module RSBB_URL_PREFIX_GET): http://mycompany.com:8104
I have no idea where the function module RSBB_URL_PREFIX_GET is getting that port of 8104. Any ideas where I can check?
Mike

I think from the profile parameter : icm/host_name_full.
in your instsance profile enter :
icm/host_name_full = hostname.domaine.
look also at the 2 parameters :
icm/server_port_0
ms/server_port_0
may be the ms/server_port_0 is equal to 81$$.
instance id is it 04 ?
these parameters should (if i remember well) define the URL you are using. make changes and let me know if it works.
Regards.

Corrupt ? : Java and ABAP Trial Version on Linux - VMware Edition

Has anyone been successfull in downloading / running the brand new testdrive "Netweaver 7.0 - Java and ABAP Trial Version on Linux - VMware Edition" ?
I tried downloading it twice, but it appears the second file (part2.rar) is corrupt.
unpacking gives a CRC error on file 'SLES10SP1_Test_Drive(2)-s003.vmdk.
Thanks & Best regards,
Jeroen Engelen
SAP Netweaver Technology consultant

Hello all,
You have to follow instruction on this side>
http://www.novell.com/documentation/sles10/esd/ii_sap_testdrive_sles10sp1_vmware1.html
YOu need to download
part1 > which is soft from NOvell called
SAP Test Drive "SLES10SP1VSAP.rar"
Maybe this link help you "http://download.novell.com/index.jsp?product_id=&search=Search&families=2658&version=8161&date_range=&keywords=&sort_by=&x=14&y=7
After donwload from sdn part two
SAP NetWeaver 7.0 - Java and ABAP Trial Version on Linux - VMware Edition
from sdn Downloads.
YOu need to use VMWARE soft to start up SLES 10 (part1) and after that use SLES to start up SAP.
But here I have problem I can not login to SLES as I don't know passwrod, I was trying to found it at novell web site or SAP without any sucess.
So at this point I am stuck
Here is the same qeustion from Jim Jiang and me
what is user name and password for SLES10 SP1 SAP Version
Hope this give you overview what needs to be done, to start up Trial SAP version
Peter Nechala

CRC failed in Java and ABAP Trial Version on Linux - VMware Edition part02

I download SAP NetWeaver 70 - Java and ABAP VMware Trial and I couldn't install it because part02 rar file has reported a checksum error.
- SAP NetWeaver 70 - Java and ABAP VMware Trial.part02.rar: CRC failed in SLES10SP1_Test_Drive(2)-s003.vmdk. The file is corrupt
Also, I think file SLES10SP1_Test_Drive.vmdk is missing from the archive files.
Could you please, confirm that the archives in the sdn downloads are correct!

I also have the same problem, CRC error:
X:SAPSAP NetWeaver 70 - Java and ABAP VMware Trial.part02.rar: CRC hiba a SLES10SP1_Test_Drive(2)-s003.vmdk-ban. A fájl sérült

JAVA Stack and ABAP Stack not in Sync

Hi,
when i logged into the MI Server(7.0) gonr thru the following navigation :
Administration-->Mobile Infrastructure---->Mobile components
which i click on the search button i am getting the following error
"JAVA Stack and ABAP Stack not in Sync"
Already i redeployed the sapjra.rar, still i find the error unchanged.
Any help on this would be great........
Thanks,
vijay.

Hi
Refer this link
Need to Configure MI Server 7.0
As explained by veeraragavan in this link follow these steps
Following are in brief the roles required, just forward the same to your BASIS administrator.
In the ABAP Stack -Under Transaction SU01:
End User:
SAP_MI_SERVICE
Administrator / Critical Developers:
SAP_J2EE_ADMIN
SAP_MI_ADMIN
In the J2EE Stack - Under Identity Management:
End User:
No role required. You can give a role for display: SAP_JAVA_NWMOBILE_ADMIN_READONLY
Administrator / Critical Developers:
SAP_JAVA_NWMOBILE_ADMIN_SUPER
regards
Manohar
Edited by: Gouri Manohar Gadhamsetty on Jan 19, 2009 7:17 AM

Full ABAP Edition-Trial: no installation of maxdb???

Hello to all,
I installed "Full ABAP Edition-Trial" some days ago and everything worked fine without any problems. Windows on partition H: and programs (like sap and sapdb) on partition L:.
Because of an other problem I had to reinstall Windows on H:. I deleted the subfolders L:\SAP and L:\sapdb. to get a clean world for sap.
I start the installation process and setup asks me the path to install sap. I enter "L:\SAP". In the next screen it asks me about the database master password. I enter my password. In the next screen the setup tolds me to install the components MaxDB to L:\sapdb and application server to L:\SAP\NSP. Total Size: 18823.1 MB needed (By the way: I have 40 GB free).
I press the install button and installation process runs without errors. Then (after 2 minutes!) I get the screen that tolds me "The InstallShield Wizard has successfully installed SAP Netweaver 2004s ABAP Trial Version.".
So I start the SAP Management Console and start the instance. The icons become green and I see for example that the processes msg_server.exe and dispwork.exe are running. Dispwork.exe stops after a few seconds.
Looking to the system log I see "Communications data: Service initialization failed" and some "SAP-Basis System: Initialization DB-Connect Failed, Return Code 008192" messages.
When I press the database icon in the the SAP Management Console, I get a screen "page could not be displayed".
So it seems like a database problem. I look to the windows explorer and there is only the SAP-folder (with 341 MB). THERE IS NO SAPDB-FOLDER!!!
I can't find an installation-log to see if there were problems (No log.txt at SAP\NSP).
I deinstalled everything with deinstaller, run some registry cleaner and also installed a clean windows at H:, but everytime the same. I find note 572836 (Deleting SAPDB Registry entries and services) but it doesn't help.
I know when I installed SAP the first time (where it worked fine), I had not to install the microsoft loopback adapter. So I tried the installation with and without the adapter. No success!!!
I get crazy about it... Perhaps there is something wrong about the preinstalling environment: I download the two files SAPNW2004sABAPTrail_part1.rar and SAPNW2004sABAPTrail_part2.rar to the folder L:\downloads. Then I unpack only the first one SAPNW2004sABAPTrail_part1.rar in the same folder. Then there is a new folder SAPNW2004sABAPTrail_part1. This one contains a folder SAPNW2004sABAPTrail. There are some folders and files. I change to the folder images. There I start the setup.exe (but before I installed the lookback adapter).
I'm a little bit irritated about the files SAPNW2004sABAPTrail_part1.rar and SAPNW2004sABAPTrail_part1.rar. The first one has a size of 1536000KB and the SAPNW2004sABAPTrail_part2.rar has a size of 1249739KB. Just for analyze I unpack the SAPNW2004sABAPTrail_part2.rar-file and see that it has exactly the same structure like SAPNW2004sABAPTrail_part1.rar!!! Also the size of the unpacked files are the same. Is this normal???
So, that's my problem: No database here. Anyone here who has an idea? Please help me. I really need ABAP here!!!
Kindly regards,
Andy

I have found the InstallationSteps.stat and install.log. Everything seems to be installed successfully, but no database is mentioned :-(. Here are the two files.
I still need help!!!
=Start of InstallationSteps.stat====================
CreateDirectories;20070108204154;20070108204155;Succeeded
CopyExecutables;20070108204155;20070108204157;Succeeded
AdaptProfiles;20070108204157;20070108204159;Succeeded
AddToServices;20070108204159;20070108204207;Succeeded
StartSCSInstance;20070108204207;20070108204232;Succeeded
StopSCSInstance;20070108204232;20070108204233;Succeeded
CreateXUserEntry;20070108204233;20070108204234;Succeeded
RestartServiceViaSAPControl;20070108204234;20070108204305;Succeeded
InstallMMC;20070108204306;20070108204308;Succeeded
=End of InstallationSteps.stat====================
and here is the install.log file:
=Start of install.log ====================
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: CreateDirectories
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:41:55
ACTION: * Logfile: steps.CreateDirectories.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
SUCCESS: Execution of step: >> CreateDirectories <<
 finished successfully.
 Elapsed time: 00:00:00 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: CopyExecutables
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:41:56
ACTION: * Logfile: steps.CopyExecutables.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
COPY_EXECUTABLES: Copy log converter (lc.jar) to users home directory
COPY_EXECUTABLES: Copy SDC log viewer (slv.jar) to users home directory
COPY_EXECUTABLES: Prepare environment for engine configuration:
COPY_EXECUTABLES: Copy jperflib.dll to actual working dir.
COPY_EXECUTBLES: Create startup and stop scripts in engine bin folder.
copyFileWithProcessing(L:\SAP\NSP\home\additional_sw\t_startSystem.cmd,L:\SAP\NSP\SYS\exe\run,startSystem.cmd)
Reading file L:\SAP\NSP\home\additional_sw\t_startSystem.cmd
Keys:
Sections to process:
copyFileWithProcessing(L:\SAP\NSP\home\additional_sw\t_stopSystem.cmd,L:\SAP\NSP\SYS\exe\run,stopSystem.cmd)
Reading file L:\SAP\NSP\home\additional_sw\t_stopSystem.cmd
Keys:
Sections to process:
copyFileWithProcessing(L:\SAP\NSP\home\additional_sw\t_strdbsj2ee.cmd,L:\SAP\NSP\SYS\exe\run,strdbsj2ee.cmd)
Reading file L:\SAP\NSP\home\additional_sw\t_strdbsj2ee.cmd
Keys:
Sections to process:
COPY_EXECUTABLES: Finished ....
SUCCESS: Execution of step: >> CopyExecutables <<
 finished successfully.
 Elapsed time: 00:00:00 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: AdaptProfiles
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:41:57
ACTION: * Logfile: steps.AdaptProfiles.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\antlr.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_compatibility.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.api.perm.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.core.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\common_cache_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\common_cache_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com_sap_tc_jtools_jver.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\exception.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\i18n_cp.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\iaik_jce.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jenqulib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jta.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jts_jco.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\logging_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\opensqljts.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\opensqlsta.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\remserver.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\resources.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\rfc_container_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\sapxmltoolkit.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_admin_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\transport.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_jts_extensions_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_jts_extensions_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_service.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_admin_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_internal_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_kernel.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_trace_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_util.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jenqulib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\charsets.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\jce.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\jsse.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\rt.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\security\local_policy.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\security\US_export_policy.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\sunrsasign.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\lib\tools.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jperflib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartup.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartupapi.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartupimpl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\frog.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\sapmc.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\soapclient.jar
ADAPT_PROFILES: Start to create the profiles
CONFIGURATION: Create JDBC Path in J2EE installation directory.
CONFIGURATION: New JDBC Path: L:\SAP\NSP\DVEBMGS00\j2ee\jdbc (Exist=false)
CONFIGURATION: Old JDBC Path: L:\SAP\NSP\DVEBMGS00\j2ee (Exist=false)
CONFIGURATION: New JDBC Path created.
CONFIGURATION: Copy Jars from: L:\SAP\NSP\_installTemp\j2ee\INSTALLER\COMMON\JDBC\ADA
CONFIGURATION: to : L:\SAP\NSP\DVEBMGS00\j2ee\jdbc
ADAPT_PROFILES: Create profiles for standalone J2EE
copyFileWithProcessing(additional_sw/t_DEFAULT_PFL_710,L:\SAP\NSP\SYS\profile,DEFAULT.PFL)
Reading file additional_sw/t_DEFAULT_PFL_710
Keys:
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
copyFileWithProcessing(additional_sw/t_START_INSTANCE_HOST_710,L:\SAP\NSP\SYS\profile,START_DVEBMGS00_AMMERSEE)
Reading file additional_sw/t_START_INSTANCE_HOST_710
Keys:
 WITHOUT_SHARE
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
finished reading Section WITHOUT_SHARE
copyFileWithProcessing(additional_sw/t_SID_INSTANCE_HOST_710,L:\SAP\NSP\SYS\profile,NSP_DVEBMGS00_AMMERSEE)
Reading file additional_sw/t_SID_INSTANCE_HOST_710
Keys:
 WITHOUT_SHARE
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
finished reading Section WITHOUT_SHARE
copyFileWithProcessing(additional_sw/t_START_DB_INIT_710,L:\SAP\NSP\SYS\profile,START_DVEBMGS00_AMMERSEE)
Reading file additional_sw/t_START_DB_INIT_710
Keys:
 WITHOUT_SHARE
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
finished reading Section WITHOUT_SHARE
copyFileWithProcessing(additional_sw/t_strdbmsONCE.cmd,L:\SAP\NSP/SYS/exe/run/,strdbmsONCE.cmd)
Reading file additional_sw/t_strdbmsONCE.cmd
Keys:
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
copyFileWithProcessing(additional_sw/t_setsapenv.cmd,L:\SAP\NSP/SYS/exe/run/,setsapenv.cmd)
Reading file additional_sw/t_setsapenv.cmd
Keys:
Sections to process:
[JDK_CONTAINER, WITHOUT_SHARE]
SUCCESS: Execution of step: >> AdaptProfiles <<
 finished successfully.
 Elapsed time: 00:00:01 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: AddToServices
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:41:59
ACTION: * Logfile: steps.AddToServices.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
AddToServices: Instance shall not be started by default.
AddToServices: Therefore we provide a start script in:
AddToServices: L:\SAP\NSP\home\startEngine.bat
AddToServices: Service will be created.
DEBUG: Register service with the following command:
DEBUG: "L:\SAP\NSP\SYS\exe\run/sapstartsrv.exe" -r -q -s NSP -n 00 -p L:\SAP\NSP\SYS\profile\START_DVEBMGS00_ammersee
Start external command...
Service succesfully installed.
Process exited with rc: 0
SUCCESS: Execution of step: >> AddToServices <<
 finished successfully.
 Elapsed time: 00:00:07 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: StartSCSInstance
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:42:07
ACTION: * Logfile: steps.StartSCSInstance.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\antlr.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_compatibility.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\base_services_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.api.perm.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com.sap.security.core.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\common_cache_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\common_cache_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\com_sap_tc_jtools_jver.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\exception.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\i18n_cp.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\iaik_jce.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jenqulib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jta.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\jts_jco.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\logging_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\opensqljts.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\opensqlsta.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\remserver.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\resources.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\rfc_container_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\sapxmltoolkit.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_admin_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\services_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\transport.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_jts_extensions_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_jts_extensions_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\ume_service.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_admin_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_impl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_internal_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_kernel.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_trace_api.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\cfw\lib\vmc_util.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jenqulib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\charsets.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\jce.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\jsse.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\rt.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\security\local_policy.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\security\US_export_policy.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\jre\lib\sunrsasign.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jkit\lib\tools.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jperflib.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartup.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartupapi.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\jstartupimpl.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\frog.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\sapmc.jar
Adding to classpath: L:\SAP\NSP\SYS\exe\run\servicehttp\sapmc\soapclient.jar
Starting SCS-Instance
Executing SCS-startup-command: L:\SAP\NSP\SYS\exe\run\startsap.exe name=NSP nr=00 SAPDIAHOST=ammersee
Execute in current working dir: L:\SAP\NSP\home
Start external command...
\ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ STARTSAP continues...
Process exited with rc: 0
SUCCESS: Execution of step: >> StartSCSInstance <<
 finished successfully.
 Elapsed time: 00:00:23 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: StopSCSInstance
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:42:32
ACTION: * Logfile: steps.StopSCSInstance.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
Checking running engine process via sapcontrol and wait for stopped
Checking on: SCS
Stop instance with cmd: L:\SAP\NSP\SYS\exe\run\sapcontrol.exe -prot PIPE -nr 00 -host ammersee -function StopWait 300 10
Stop instance in directory: L:\SAP\NSP\SYS\exe\run
Start external command...
08.01.2007 20:42:33
Stop
OK
08.01.2007 20:42:33
StopWait
OK
Process exited with rc: 0
Start external command...
08.01.2007 20:42:33
GetProcessList
OK
0 name: msg_server.EXE
0 description: MessageServer
0 dispstatus: GRAY
0 textstatus: Stopped
0 starttime: 2007 01 08 20:42:20
0 elapsedtime: 0:00:13
0 pid: -1
Process exited with rc: 4
SUCCESS: Execution of step: >> StopSCSInstance <<
 finished successfully.
 Elapsed time: 00:00:01 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: CreateXUserEntry
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:42:34
ACTION: * Logfile: steps.CreateXUserEntry.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
SUCCESS: Execution of step: >> CreateXUserEntry <<
 finished successfully.
 Elapsed time: 00:00:00 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: RestartServiceViaSAPControl
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:42:34
ACTION: * Logfile: steps.RestartServiceViaSAPControl.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
Restarting service via sapcontrol
Restart service with cmd: L:\SAP\NSP\SYS\exe\run\sapcontrol.exe -prot PIPE -nr 00 -host ammersee -function RestartService
Restart service in directory: L:\SAP\NSP\SYS\exe\run
Start external command...
08.01.2007 20:42:35
RestartService
OK
Process exited with rc: 0
SUCCESS: Execution of step: >> RestartServiceViaSAPControl <<
 finished successfully.
 Elapsed time: 00:00:30 [HH:mm:ss]
Process exited with rc: 0
Start external command...
Active Loglevel: 4
ACTION: **********************************************************************
ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
ACTION: *
ACTION: * Executing Step: InstallMMC
ACTION: * User: Fasan
ACTION: * WorkingDirectory: L:\SAP\NSP\home
ACTION: * Date: 2007.01.08 20:43:06
ACTION: * Logfile: steps.InstallMMC.log
ACTION: * Property File: L:\SAP\NSP\home\j2eeinst.props
ACTION: * Tool Version: 720.2.20060802095936
ACTION: **********************************************************************
INSTALL_MMC: Prepare to extract the SAPMMC
SAPMMC already extracted on cd. don't extract it a secon time.
INSTALL_MMC: Start to copy dll to SYSTEM32 directory
INSTALL_MMC: Copy sapmmc.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Copy sapmmcada.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Copy sapmmcdb6.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Copy sapmmcinf.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Copy sapmmcms.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Copy librfc32.dll to H:\WINDOWS\SYSTEM32\
INSTALL_MMC: Start to copy the help file
INSTALL_MMC: Copy sapmmc.chm to H:\WINDOWS\help\
INSTALL_MMC: Start to copy the msc file
INSTALL_MMC: Copy sapmmc.msc to H:\WINDOWS\
INSTALL_MMC: Start to register dll
INSTALL_MMC: Register sapmmc.dll
InstallMMC: Registering dll with the following command: regsvr32 /s sapmmc.dll
INSTALL_MMC: Register sapmmcada.dll
InstallMMC: Registering dll with the following command: regsvr32 /s sapmmcada.dll
INSTALL_MMC: Register sapmmcdb6.dll
InstallMMC: Registering dll with the following command: regsvr32 /s sapmmcdb6.dll
INSTALL_MMC: Register sapmmcinf.dll
InstallMMC: Registering dll with the following command: regsvr32 /s sapmmcinf.dll
INSTALL_MMC: Register sapmmcms.dll
InstallMMC: Registering dll with the following command: regsvr32 /s sapmmcms.dll
SUCCESS: Execution of step: >> InstallMMC <<
 finished successfully.
 Elapsed time: 00:00:01 [HH:mm:ss]
Process exited with rc: 0
=End of install.log ====================

Initial password for SAP* in SAP NetWeaver 2004s ABAP Edition

Hello,
I have just installed the SAP NetWeaver 2004s ABAP Edition on my PC and I want to setup some new clients to simulate an ALE model.
Does anyone know the initial password for SAP* ?
I have already tried PASS and pass because I know it is case -sensitive now but it did not work.
Thanks a lot.
Wim Van den Wyngaert

Hi,
initial SAP* password is 06071992
DDIC is 19920706

Java Maping and ABAP Mapping

Hello,
Pls let me know about Java Maping and ABAP Mapping
Also pls provide good simple scenario blogs for Java Maping and ABAP Mapping.
Regards

Hi Ranchit,
Check these links for Mappings
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9202d890-0201-0010-1588-adb5e89a6638
https://websmp102.sap-ag.de/~sapdownload/011000358700003604872004E/MappingXI30.pdf (Need Service Makrket place ID)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8a57d190-0201-0010-9e87-d8f327e1dba7
JAVA Mapping BLOGS
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-iii
/people/stefan.grube/blog/2006/10/23/testing-and-debugging-java-mapping-in-developer-studio
ABAP Mapping Blogs
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
/people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
Sachin
Message was edited by:
Sachin Dhingra

Users mapping between EP and ABAP system

Hello
I'd like to ask for some guidance in my quest
Current situation looks like this:
I've configured UME in AS Java to work with LDAP as read only data source. Then I've configured SPNego to run SSO - It works, users from MS AD can log into portal.
Now I have application in WD which authorizes via EP/AD - works fine.
And next step is users mapping between AD and ABAP backend (serving some BAPI's for WD app)
I've found a bunch of help pages starting from
http://help.sap.com/saphelp_nwce711/helpdata/en/0b/d82c4142aef623e10000000a155106/frameset.htm
But somehow it's quite complicated to achieve this mapping. I've tried to set RFC destinations logon type to user mapping but without succes.
Can anyone point me to some more clear example or give path to configure this scenario? Is there a way of configuring this with NWA or some XML file editing is required?
Any help will be appreciated.
BTW: whole environment is in version 7.11
Best regards
Maciej

There is no equivalent to SPNEGO on the ABAP side.
If your goal is to propagate the user, then possible options are:
-> Wait for SAML 2.0 or invest now in a SAML 1.0 provider.
-> Use the same kerberos ticket for the EP as what your ABAP system will accept: route = SNC and 3rd party libraries.
-> Issue SAP logon tickets for the ABAP system from the EP, and use these in your WDA.
Another option is to expose the service with saved logon data in the ICF. If the service is just a wrapper for the BAPI, then you can also consider using trusted RFC between the service and the backend, but this might not be acceptable for your service.
I have only done experimental stuff with this and some of the above is not released yet. Also consider the consequences, even if it "does work"...
Cheers,
Julius

1:n Message split and Abap Proxies??

Hello,
Can I not use Message split and Abap Proxy together? My scenario is MDM->File ->XI->Proxy->BI.
I am getting a single file syndicated from MDM and in XI If I use message mapping to do 1:n split in the message mapping, can I use it with Abap Proxies? As per the link below, XI adapter is not present in the list..We are on PI 7.0 SP14. Thank you..
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
Thank you for any suggestion..

Hi Thanujja,
If you see the message from Raj, I dont think we can split the messages for the proxy. This is beacause the splitting of messages take place at the Adapter Level only for the adapters on the Java stack.
As suggested by Guru, you can try splitting the messages in the inbound proxy instead of using a BPM, in that way you can acheive good performance.
Thanks,
Srini
Edited by: srinivas kapu on Mar 27, 2008 9:09 AM
Edited by: srinivas kapu on Mar 27, 2008 9:10 AM

Using XSLT to link XML and ABAP data

Hi Experts,
I am using XSLT to deal with XML and ABAP data.
I using the following statement to convert a Internal Table to XML String:
CALL TRANSFORMATION id SOURCE root = lt_sflight RESULT XML l_xml_string.
And I get the XML String:
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<ROOT>
<SFLIGHT>
</SFLIGHT>
<SFLIGHT>
</SFLIGHT>
</ROOT>
</asx:values>
</asx:abap>
But What I expected is:
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<ROOT>
<DATA>
</DATA>
<DATA>
</DATA>
</ROOT>
</asx:values>
</asx:abap>
Could you tell me how to get my dream format using XSLT?
Best Regards,
Guo Guo Qing
Edited by: guoqing guo on Jun 11, 2008 9:58 AM

Hi Experts,
I am using XSLT to deal with XML and ABAP data.
I using the following statement to convert a Internal Table to XML String:
CALL TRANSFORMATION id SOURCE root = lt_sflight RESULT XML l_xml_string.
And I get the XML String:
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<ROOT>
<SFLIGHT>
</SFLIGHT>
<SFLIGHT>
</SFLIGHT>
</ROOT>
</asx:values>
</asx:abap>
But What I expected is:
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<ROOT>
<DATA>
</DATA>
<DATA>
</DATA>
</ROOT>
</asx:values>
</asx:abap>
Could you tell me how to get my dream format using XSLT?
Best Regards,
Guo Guo Qing
Edited by: guoqing guo on Jun 11, 2008 9:58 AM

How is the interface between the Java Stack and ABAP stack is achieved?

How is the interface between the Java Stack and ABAP stack is achieved?..Please send me the answer to [email protected]

Hi,
By interface, I assume you mean the connection between the ABAP and the Java stacks in a double stack system.
The connection from Java to ABAP is through JCo connections defined in the WebDynpro section of the J2EE start page. So Java to ABAP requests are processed through JCo.
The connection from ABAP to Java is through RFC connections defined in TA SM59. The ABAP to Java requests are processed through RFC.
Refer https://dsd.esco-salt.com/StartPage/documents/integration/3.html for detailed explanation.
The UME can be maintained in either ABAP or in JAVA depending on the persistence.
Refer: http://help.sap.com/saphelp_nw70/helpdata/en/5b/5d2706ebc04e4d98036f2e1dcfd47d/frameset.htm
Check UME data source configuration.
Some quick FAQs can be found at:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad47eb90-0201-0010-7cb2-ddfa5ed879ec
Hope this helps.
Best Regards,
Srividya.R

SMSY for ERP JAVA and ABAP Stack

Hi Folks - I have installed SAP ERP 6.0 EHP5 in one database called T12. Now there is a need for a Java stack and I have installed the Java stack in another database called J12.
I was able to define the ABAP stack on system landscape and MOPZ is working fine. However, I am not sure how I should go about the Java (J12) instance definidstion on SMSY.
I am using Somlam 7.1 on Oracle Linux system.
ABAP stack is on ERL 6.0 EHP5 and Java stack is Netweaver 7.0 EHP2.
J12 and T12 systems are connected via JCO.
SLD has been defined for both stacks and they are using the local SLD for the SolMan.
Your help is much appriciated.

Sunny - I checked the SLD and It is working fine. There were couple of issues that I fixed. Since I defined the Java system manually I delete it. Hopefully SLD will populate the definition.
In same note, Would it be possible that installing ERP java and ABAP stack on different hosts (stand alone) is causing this issue, especially they are using different Sid's?
I was reading SAP Note 1344564, It states
III.Some Main Instances include other Main Instances (E.g., in SAP
ERP 6.0, Main Instance SAP NW - Enterprise Portal includes SAP NW -
EP Core.). If the including Main Instance is installed, it's not
necessary to mark the included Main Instance(s) for relevance.
Is this mean in SMSY I do not have to define any product for the Java engine? When installing the Java, I had to create the product manually to be able to generate the installation key.
Your input is appreciated.
Edited by: kourosh Ghouchkhani on Nov 22, 2011 1:20 AM

Compatability of J2EE and ABAP Editions

Similar Messages

Maybe you are looking for