EP6 Migration to NW04 - J2EE requirements

Hi Guru's
We are in the process of migrating our Portal from EP6 sp2 to NW04 and the tool we are using to migrate is "EP60MIGTOOL_8".
It seems as if this tool requires J2EE version 6.40 on the source system.
Is this correct and do we have to upgrade our J2ee engine to 6.40 on the source system ??
Regards,
Morgan Moodley

Hi Morgan,
when you migrate from EP6 SP2 to NW04, you need two systems.
The source system, with EP6 SP2, at least PL30
The target system, with EP6 NW04, at least SP16 (maybe 17 now).
You execute the migration tools on the EP6 NW04 system, that copy KM/PCD data via the network .
Brad

Similar Messages

  • Upgrade + migration from nw04 on windows 2000 to nw04s on windows 2008

    Dear all,
    I need to upgrade and migrate my nw04 java system from windows 2000 to nw04s on windows 2008.
    From the PAM I can see that NW04 is not supported on windows 2008 and that nw04s (7.0) is not supported on windows 2000.
    So, which is the correct upgrade path? Do I need an intermediate win 2003 server which is supported from both the releases?
    Thanks and regards in advance
    Federico

    Hello my friend
    This will be a very interesting project for sure. As you know, kernel 640 is not supported on win2008 and 700 is not supported on win2000, so here there must be a win2003 as a transition platform for this upgrade+ migration, not to mention migration from 32bit to x64 is also involved. You didn't mention the DB versions in source and target systems, as well as the SAP product you're trying to go with. Here's a brief checklist right now for what I can think of, once you're back with more details then let's make it intact:
    I assume your source OS/DB is win2000SQL2000 32bit, target one is win2008SQL2008 x64.
    1. Install a win2003 x64 server and SQL2000 32bit;
    2. Install a new SAP instance same as your source system release in 32bit compatible mode;
    note: if the system being migrated is BW, then be aware of that you might want to bring new features in SQL2008 of row compression and table partitions.
    3. Detach the source DB from old SQL2000, and attach it to new SQL2000; some post configuration for DB copy will be required (STM tool). Now you've finish a migration from win2000 to win2003 32bit;
    4. Start upgrading NW04 to 7.0, 640 to 700, find details in upgrade guide; Now you have your 700 instance on win2003 x64+SQL2000 32bit;
    note: since release 701(700 EHP1) is available now, which you might want to upgrade instead of 700.
    5. Change the collation 850BIN2 for SQL2000 32bit, detach DB;
    6. Since migration from 32bit to x64 cannot be done smoothly, now you have to uninstall everything and reinstall win2003 and SQL2008 x64, followed by a new 700 or 701 instance;
    7. Attach the source DB, post configuration for DB copy will be required (STM tool); Now you have your 700 or 701 instance on win2003 x64+SQL2008 x64;
    8. Detach the SQL2008 DB;
    9. Now go to your target win2008 OS, install SQL 2008 x64 and new 700 or 701 instance;
    note: there might be some restrictions for NW 7.0 on win2008, go with the latest release (SR3 or newer).
    10. Attach DB to this final OS/DB version: win2008 x64+SQL2008 x64, post configuration for DB copy will be required (STM tool).
    Helpful?
    Regards,
    Effan

  • Migrate 6.20 Java App to NW04 J2EE in NWDS

    We are moving our java apps from WAS 6.20 to NW04(S).
    The SAP migration tool is designed for several third party vendors but does not work with SAP 6.20.
    We can take the EAR file from 6.20 and use the Deploy/Convert tools to deploy the application to NW04S.
    However, we are not sure how to convert the 6.20 Eclipse project to an NW04(S) J2EE project in Netweaver Development Studio.
    Has anyone seen a tutorial on this topic?
    Cheers ... Bart

    Hi Thomas,
    Thanks for your post on this topic.  We have visited that link that you mentioned.  It gives a good overview.
    We have been able to take a 6.20 ear file and use the deploy/convert tools to get the 6.20 java development running on 6.40.
    Our question is more centered around the "Using NWDS" part of that link.   We are really looking for a previous example/tutorial of the process of importing a 6.20 project into 6.40 and then doing the manual conversion.
    Thanks again ... Bart

  • EP6 Migration tool for Netweaver

    Dear All,
    We have developed iViews based on HTMLB,JSPDynPage and JCO can any one help me how to migrate all my iViews to Netweaver EP6
    Is there any tool to migrate my iViews(par files) to netwever EP6
    Thanks and Reagrds
    Prasad.Y

    Hi,
    please don't missunderstand what the migration tool is able to do. You have to adapt your coding yourself (if necessary). A good point to start with would be to deploy your EP5 applications to your NW04 system and see which errors come up. Now correct error after error until your applications are running.
    Regards, Jochen

  • How to migrate a full J2EE application from WebLogic to NetWeaver?

    I have an independent J2EE application which can be run on WebLogic successfully. Now, I want to migrate it to the platform of NetWeaver. Could you tell me how to do with it? And where can I find the jar files of the application I deployed?
    Thank you very much!

    Have you tried the "exploded" format?
              Also, do you mean Weblogic 6.1 (sp2?).
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              Clustering Weblogic? You're either using Coherence, or you should be!
              Download a Tangosol Coherence eval today at http://www.tangosol.com/
              "adurthy" <[email protected]> wrote in message
              news:[email protected]..
              >
              > HI All,
              >
              > I am trying a migrate a application Jsp application with taglibs from
              tomcat 4.0
              > to weblogic 6.2
              >
              > I tried the example way but none seems to work
              >
              > any help or articles are appreciated
              >
              > thanks
              > sivaji
              

  • Role Migration EP60 NW04

    Hello,
    its mybe an easy question, but i dont find an answer in the manual :-(.
    i would upload some SAP BW roles to the Enterprise Portal.
    In EP 5.0 i know there was a tool named "Role Migration".
    So i search this forum where this is located now.
    All Postings say that there mus be an entry under "System Administration - Transport"
    But in my Portal there isnt only:
    Export
    Import
    Upload von Content und Aktionen
    Unification-Synchronisation
    Does anybody know where i can find the "Role Upload"?
    Best Regards,
    Patrick

    hi John,
    it is very strange :-/.
    I take a look in an other NW04 SP9 Portal and it has your entrys. My Portal didnt have this. I have the Super Administrator role assigned.
    Never seen this before that an menu entry are lost.
    Best regards,
    Patrick
    > Hi Patrick,
    > When I log on to my SP9 portal, under System
    > tem Administration > Transport, I have the following
    > entries in the detailed navigation.
    >
    > Export
    > Import
    > Upload Content and Actions
    > Unification Synchronization
    > Role Upload
    > Content Mirroring.
    >
    > Acording to your note I assumed that you only had the
    > first four entries.  The fifth entry on mine is the
    > Role upload.  Are you logged on as the super
    > administrator or just system administrator?
    >
    > John

  • LDAP user authentication on EP6 built on NW04 abap+java

    Hello,
    Our customer insisted we install is EP6 system as a ABAPJAVA system. He asked that users login to the portal will be authenticated (username password) from their directory service via LDAP. Because the EP6 is built on a ABAPJAVA, and not only JAVA, I cannot use the portal or visual adiministrator tools to make the LDAP be the source User Management system.
    I have been looking all day in the sap online help and I do not see any instructions on how to configure user+password logon authentication via LDAP on an ABAP based UME system. The most I have managed was to setup the connection from the EP6 system to ldap via transaction LDAP and bring up the ldap connector.
    I need to know how to proceed from here.
    Thanks
    Boaz

    Hello,
    I add a notion that this configuration is not supported.
    However, please look at the following link, which relates to an ABAP system, I refer to the bolded section.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/aa/a17941601b050de10000000a1550b0/frameset.htm
    The following is mentioned in this link:
    The user password is not transferred from the SAP Web AS to the LDAP directory during the synchronization of the user data. You must therefore maintain the user password with one of the following options:
    You specify the passwords centrally in the LDAP server. The users must log on using the UME, are authenticated with the LDAP server, receive a logon ticket and can then access all systems with Single Sign-On. In this case, all systems must be configured so that they accept logon tickets.
    ·        You specify the passwords in a decentralized way, both in the CUA and in the LDAP directory (or in the UME). In this case, the CUA systems do not need to accept logon tickets.
    What is the meaning behind this?
    Thanks
    Boaz

  • Cannot restart SAP NW04s j2ee : open cluster failed

    Hi,
    I can't start SAP j2ee, the dispatcher is in yellow light in SAPMMC.
    this is my sapstartsrv.log file:
    trc file: "sapstartsrv.log", trc level: 0, release: "700"
    pid        2028
    Thu Dec 18 10:32:26 2008
    SAP HA Trace: Build in SAP Microsoft Cluster library '700, patch 175, changelist 1007059' initialized
    Initializing SAPControl Webservice
    SapSSLInit failed => https support disabled
    Starting WebService Named Pipe thread
    Starting WebService thread
    Webservice named pipe thread started, listening on port
    .\pipe\sapcontrol_00
    Webservice thread started, listening on port 50013
    LJBW\bwdadm is starting SAP System at 2008/12/18 10:45:49
    SAP HA Trace: FindClusterResource: OpenCluster failed: 1753 [sapwinha.cpp, line 212]
    SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 907]
    LJBW\bwdadm is stopping SAP System at 2008/12/18 11:28:24
    SAP HA Trace: FindClusterResource: OpenCluster failed: 1753 [sapwinha.cpp, line 212]
    SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 907]
    LJBW\bwdadm is starting SAP System at 2008/12/18 11:32:13
    Many thanks
    George

    it says failed to update service environment from user environment.
    here is the dev_w0 file.
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ
    B 
    B Thu Dec 18 11:32:24 2008
    B  create_con (con_name=R/3)
    B  Loading DB library 'E:\usr\sap\BWD\DVEBMGS00\exe\dbmssslib.dll' ...
    B  Library 'E:\usr\sap\BWD\DVEBMGS00\exe\dbmssslib.dll' loaded
    B  Version of 'E:\usr\sap\BWD\DVEBMGS00\exe\dbmssslib.dll' is "700.08", patchlevel (0.171)
    B  New connection 0 created
    M sysno      00
    M sid        BWD
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    175
    M intno      20050900
    M make:      multithreaded, ASCII, optimized
    M pid        4224
    M
    M  kernel runs with dp version 241(ext=110) (@(#) DPLIB-INT-VERSION-241)
    M  length of sys_adm_ext is 364 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4224) [dpxxdisp.c   1323]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          43512     (1176)
    M  DpShMCreate: sizeof(tm_adm)          3786880     (18840)
    M  DpShMCreate: sizeof(wp_ca_adm)          18048     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
    M  DpShMCreate: sizeof(comm_adm)          528048     (1048)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)          0     (96)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1296)
    M  DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 05510040, size: 4446512)
    M  DpShMCreate: allocated sys_adm at 05510040
    M  DpShMCreate: allocated wp_adm at 05511BA8
    M  DpShMCreate: allocated tm_adm_list at 0551C5A0
    M  DpShMCreate: allocated tm_adm at 0551C5D0
    M  DpShMCreate: allocated wp_ca_adm at 058B8E50
    M  DpShMCreate: allocated appc_ca_adm at 058BD4D0
    M  DpShMCreate: allocated comm_adm at 058BEC40
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 0593FAF0
    M  DpShMCreate: allocated gw_adm at 0593FB30
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 0593FB60
    M  DpShMCreate: allocated wall_adm at 0593FB68
    M  rdisp/queue_size_check_value :  -> off
    M  ThTaskStatus: rdisp/reset_online_during_debug 0
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M 
    M Thu Dec 18 11:32:25 2008
    M  ThInit: running on host bwdev
    M 
    M Thu Dec 18 11:32:26 2008
    M  calling db_connect ...
    C  Thread ID:5228
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'E:\usr\sap\BWD\DVEBMGS00\exe\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      171
    C    patchcomment ODBC DBSL Error handling in DSQL batches (1233665)
    C  Local connection used on BWDEV to named instance: np:BWDEV\BWD
    C  CopyLocalParameters: dbuser is 'bwd'
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C  Provider Release:9.00.3042.00
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C  Cache sizes: header 52 bytes, 20000 names (26880000 bytes), 500 dynamic statements (2728000 bytes), total 29608052 bytes
    C  Using shared procedure name cache BWDEV_BWD_BWDBWD_BWD_MEM initialized by another process.
    C  Connected to db server : [BWDEV\BWD] server_used : [np:BWDEV\BWD], dbname: BWD, dbuser: bwd
    C  pn_id:BWDEV_BWD_BWDBWD_BWD
    C  Using MARS (on sql 9.0)
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20081218 113226 BWDEV\BWD      
    C  The IRow interface is supported by this OLEDB provider
    M  db_connect o.k.
    M  ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif
    I 
    I Thu Dec 18 11:32:28 2008
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 0B550040, size: 4400128)
    M  SHM_ROLL_AREA          (addr: 9C490040, size: 61865984)
    M  SHM_PAGING_AREA          (addr: 0B990040, size: 33554432)
    M  SHM_ROLL_ADM               (addr: 0D9A0040, size: 618548)
    M  SHM_PAGING_ADM          (addr: 0DA40040, size: 525344)
    M  ThCreateNoBuffer          allocated 324144 bytes for 1000 entries at 0DAD0040
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 7424 bytes (50 server) at 09590040
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    X  ES initialized.
    B  dbntab: NTAB buffers attached
    B  dbntab: Buffer FTAB(hash header)  (addr: 0DBB0088, size: 456)
    B  dbntab: Buffer FTAB(anchor array) (addr: 0DBB0250, size: 159884)
    B  dbntab: Buffer FTAB(item array)   (addr: 0DBD72E0, size: 719172)
    B  dbntab: Buffer FTAB(data area)    (addr: 0DC86C28, size: 30724096)
    B  dbntab: Buffer IREC(hash header)  (addr: 10770088, size: 456)
    B  dbntab: Buffer IREC(anchor array) (addr: 10770250, size: 159884)
    B  dbntab: Buffer IREC(item array)   (addr: 107972E0, size: 179784)
    B  dbntab: Buffer IREC(data area)    (addr: 107C3128, size: 6144000)
    B  dbntab: Buffer STAB(hash header)  (addr: 0F9E0088, size: 456)
    B  dbntab: Buffer STAB(anchor array) (addr: 0F9E0250, size: 159884)
    B  dbntab: Buffer STAB(item array)   (addr: 0FA072E0, size: 179784)
    B  dbntab: Buffer STAB(data area)    (addr: 0FA33128, size: 3072000)
    B  dbntab: Buffer TTAB(hash header)  (addr: 10DA0088, size: 4304)
    B  dbntab: Buffer TTAB(anchor array) (addr: 10DA1158, size: 159884)
    B  dbntab: Buffer TTAB(item array)   (addr: 10DC81E8, size: 479448)
    B  dbntab: Buffer TTAB(data area)    (addr: 10E3D2C0, size: 3755676)
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 37, CON_ID = -1
    B  dbstat: TABSTAT buffer attached (addr: 119415D0)
    B  dbtbxbuf: Buffer TABL  (addr: 125B00C8, size: 30000128, end: 1424C4C8)
    B  dbtbxbuf: Buffer TABLP (addr: 142500C8, size: 10240000, end: 14C140C8)
    B  dbexpbuf: Buffer EIBUF (addr: 14C200D0, size: 4194304, end: 150200D0)
    B  dbexpbuf: Buffer ESM   (addr: 150300D0, size: 4194304, end: 154300D0)
    B  dbexpbuf: Buffer CUA   (addr: 111E00D0, size: 3072000, end: 114CE0D0)
    B  dbexpbuf: Buffer OTR   (addr: 154400D0, size: 4194304, end: 158400D0)
    B  dbcalbuf: Buffer CALE  (addr: 0FD40040, size: 500000, end: 0FDBA160)
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 0B45B140
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  2 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 1D630098
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 1D6308E8
    S    using messages for server info
    S  size of spec char cache entry: 165020 bytes (timeout 100 sec)
    S  size of open spool request entry: 1216 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A 
    A Thu Dec 18 11:32:29 2008
    A 
    A  -PXA--
    A  PXA INITIALIZATION
    A  PXA: Locked PXA-Semaphore.
    A  System page size: 4kb, total admin_size: 34956kb, dir_size: 17352kb.
    A  Attached to PXA (address 4D080040, size 600000K, 2 fragments of 282524K )
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A 
    A 
    A Thu Dec 18 11:32:30 2008
    A  ABAP ShmAdm attached (addr=BACA6000 leng=20955136 end=BC0A2000)
    A  >> Shm MMADM area (addr=BB025338 leng=134016 end=BB045EB8)
    A  >> Shm MMDAT area (addr=BB046000 leng=17154048 end=BC0A2000)
    A  RFC Destination> destination bwdev_BWD_00 host bwdev system BWD systnr 0 (bwdev_BWD_00)
    A  RFC Options> H=bwdev,S=00,d=1,
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 1
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects          allocated 76458 bytes at 0FF30040
    N  SsfSapSecin: putenv(SECUDIR=E:\usr\sap\BWD\DVEBMGS00\sec): ok
    N 
    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is E:\usr\sap\BWD\DVEBMGS00\exe\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...completed with return code 5.
    N  =================================================
    B  dbtran INFO (init_connection '<DEFAULT>' [MSSQL:700.08]):
    B   max_blocking_factor =  50,  max_in_blocking_factor      = 255,
    B   min_blocking_factor =   5,  min_in_blocking_factor      =  10,
    B   prefer_union_all    =   1,  prefer_join                 =   1,
    B   prefer_fix_blocking =   0,  prefer_in_itab_opt          =   0,
    B   convert AVG         =   1,  alias table FUPD            =   0,
    B   escape_as_literal   =   0,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x00,  character encoding          =SBCS / []:X,
    B   use_hints           = abap->1, dbif->0x1, upto->0, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    M  JrfcVmcRegisterNativesDriver o.k.
    W  =================================================
    W  === ipl_Init() called
    W    ITS Plugin: Path dw_gui
    W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
    W    ITS Plugin: sizeof(SAP_UC) 1
    W    ITS Plugin: Release: 700, [7000.0.175.20050900]
    W    ITS Plugin: Int.version, [33]
    W    ITS Plugin: Feature set: [17]
    W    ===... Calling itsp_Init in external dll ===>
    W  === ipl_Init() returns 0, ITSPE_OK: OK
    W  =================================================
    N  VSI: WP init in ABAP VM completed with rc=0
    E  Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume bwdev_BWD_00
    E  Enqueue Info: enque/disable_replication = 2
    E  Enqueue Info: replication disabled
    E  EnqCcInitialize: local lock table initialization o.k.
    E  EnqId_SuppressIpc: local EnqId initialization o.k.
    E  EnqCcInitialize: local enqueue client init o.k.
    M  MBUF info for hooks: MS component UP
    M  ThSetEnqName: set enqname by server list
    M  ThISetEnqname: enq name = >bwdev_BWD_00                            <
    E 
    E  *************** EnqId_EN_ActionAtMsUpHook ***************
    E  Hook on upcoming Ms (with EnqSrv), get auth EnqId and check it locally
    E 
    E  *************** ObjShMem_CheckAuthoritativeEnqId ***************
    E  Checking authoritative EnqId from EnqSrv into ObjShMem
    E  ObjShMem_CheckAuthoritativeEnqId: ObjShMem ...
    E  EnqId.EnqTabCreaTime    = -999
    E  EnqId.RandomNumber      = -999
    E  ReqOrd.TimeInSecs       = -999
    E  ReqOrd.ReqNumberThisSec = -999
    E  ObjShMem_CheckAuthoritativeEnqId: ObjShMem ...
    E  EnqId.EnqTabCreaTime    = -999
    E  EnqId.RandomNumber      = -999
    E  ReqOrd.TimeInSecs       = -999
    E  ReqOrd.ReqNumberThisSec = -999
    E  ObjShMem_CheckAuthoritativeEnqId: EnqId is initial in ShMem
    E  ObjShMem_CheckAuthoritativeEnqId: Overwrite incoming auth EnqId, continue
    E  EnqId inscribed into initial ObjShMem: (ObjShMem_CheckAuthoritativeEnqId)
    E  -SHMEM--
    E  EnqId:          EnqTabCreaTime/RandomNumber    = 18.12.2008 11:32:30  1229571150 / 4224
    E  ReqOrd at Srv:  TimeInSecs/ReqNumberThisSec    = 18.12.2008 11:32:30  1229571150 / 2
    E  ReqOrd at Cli:  TimeInSecs/ReqNumberThisSec    = 18.12.2008 11:32:30  1229571150 / 1
    E  Status:         STATUS_OK
    E  -
    M  ThActivateServer: state = STARTING
    L  BtcSysStartRaise: Begin
    L  Raise event SAP_SYSTEM_START with parameter <bwdev_BWD_00        >
    L  BtcSysStartRaise: End
    M 
    M Thu Dec 18 11:32:31 2008
    M  SosICreateNewAnchorArray: sos_search_anchor_semantics = 1
    C 
    C Thu Dec 18 11:32:33 2008
    C  The IRow interface is supported by this OLEDB provider
    B 
    B Thu Dec 18 11:32:36 2008
    B  table logging switched off for all clients
    M 
    M Thu Dec 18 11:32:37 2008
    M  SecAudit(RsauShmInit): WP attached to existing shared memory.
    M  SecAudit(RsauShmInit): addr of SCSA........... = 05300040
    M  SecAudit(RsauShmInit): addr of RSAUSHM........ = 05300490
    M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 053004C8
    M  SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 053004D4

  • Migration from NW04 to NW04s

    Hi,
    I have two servers.
    One is the DTR/SLD/CMS/CBS working on NW2004.
    The other is the DTR/SLD/CMS/CBS working on NW2004s ie NW 7.0 SP11
    I have trackd on both the DTRs
    I need to transport the SC & DCs created on the track on NW2004, to the new track on NW2004s(NW7.0).
    Is there any SAP document or blog about this transportation??
    I read on help.sap about importing the project into the NWDS04s & then copy pasting the src files to the DCs of the new track. But i want to avoid this.
    Is there any other systematic way of going ahead with this??
    Regards,
    Hanoz

    go thru dis
    /people/guenter.schiele/blog/2007/02/12/how-to-migrate-developed-software-components-to-a-new-release-in-nwdi

  • R/3 Enterprise migration required to migrate EP 6.0 SP2?

    We currently have R/3 Entprise Core 4.7 installed, w/Ext Set 1.10, and are running Enterprise Portal 6.0 SP2 with the J2EE 6.20 Engine.
    Can we install Netweaver 2004s and migrate EP 6.0 SP2 to the current release (in order to take advantage of the Web Dynpro for ABAP and Visual Compose tools) without migrating R/3 Enterprise to mySAP ERP?
    Thanks,
    Paul

    Hi Paul,
      You can upgrade the portal with out upgrading the R/3 enterprise.  Note, that you can't go directly from EP6 sp2  to NW 2004s.   You have to migrate to NW04 and then perform the upgrade to NW 2004s.  Check the portal migration home page at http://service.sap.com/nw-epmig
    Good Luck,
    John

  • NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

    We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
    ECC5.0
    Abap Stack
    EP6 SP13
    Java Stack
    latest versions of MSS and ESS BPs
    The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
    With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
    Any help on this will be greatly appreciated.
    Thanks in advance.
    Regards, Neeta

    Hi,
    Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
    http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
    The error message I get is (rather long....):
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
        ... 53 more
    See full exception chain for details.
    Correction Hints
    Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
    Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version 
    DOM version 
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 95420.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Other
    Session Locale en_US
    Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
         ... 53 more
    Thanks, Neeta

  • Export/import content from EP6 into NW04

    We are upgrading from SRM3.0/EP6 SP2 (source) to SRM5.0/Portal NW2004s (target).
    The only thing we need to preserve from the source portal are the users and roles. We plan to re-apply the business package for SRM 5.0 after the migration is completed. We are not using any Collaboration Rooms.
    I know there is a migration path from EP6 SP2->EP6 SP9(NW04), followed by an upgrade from NW04->NW04s.
    My question is:
    - is it possible to export content from EP6SP2 and import it into NW04/MW04s?  this will eliminate the complicated migration path from EP6 SP2 to NW04.

    Hi,
    As long as you only need to transport PCD content, I would recommend using normal PCD transport (just did an upgrade from EP6 SP2 to NW04 SP13 and used normal PCD transport without any problems. Will do the same for another upgrade to NW04s). Only if you have KM content you are forced to use the migration tools.
    I am not quite sure about users and role migration since I've only use LDAP as a user store (we manually repeated the AD group to portal role mapping since there were very few)
    There was a conf call on this, but the only reference I can find now is https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/supplemental_docs/prtl204.pdf
    Dagfinn

  • How to Upload/Migrate EP5 Users To EP6 of Netweaver Componet

    I want to migrate my EP5 Application into EP6 of Netweaver Componet, Can any one guide me How To Migrater/Upload Users in EP6 of Netweaver. First of All I want to Know How To Take the Users Content whcich is in EP5 and in whcih format how to take. I really dont know where my Users are saved in EP5 and how to take those Users and upload in EP6 of Netweaver
    Thanks and Regards
    Prasad.Y

    OSS 827768 Comparison between Migration and Transport
    732458 Migration Enterprise Portal 6.0 SP2 to NW '04 - Central Note
    732461 Central Note - Migration of EP & KM from 5.0 to NW '04 
    Look under /instguidesNW04 -> Documentation -> How-To guides for the current docs on EP5 and EP6 migration.
    Also, NW04 is able to take in users through a plain text upload file.
    Nick

  • Migrate EP 5 SP6 to NW04s

    We want to upgrade to the last version of SAP Portal, but in all the
    documents we´ve read the upgrade is referred to EP 6 SP14 o higher
    (NW04) but it´s not named the version NW04s.
    Is it possible to upgrade from EP 5 SP6 to NW04s???. The tool to do the
    upgrade, is it available for NW04s???
    And other question, whitch is the version of portal in NW04s?.
    Thanks and regards.
    Raúl Martinez.

    Hi,
    You need to do a migration to NW04 then an upgrade to NW04S.
    I am doing this right now from an EP6 SP2 portal.
    I think the best way is to migrate to NW04 SP16 first, then upgrade to NW04S SP07.
    For this you need two computers. One with the source portal (EP5 or EP6) and another with a NW04 SP16 clean, on same version database. You migrate the KM part, then the PCD part.
    You can find all docs for migration at :
    https://service.sap.com/nw-epmig
    Then choose the EP5 scenario.
    You can find the migration tools at :
    https://service.sap.com/swdc , support packages and patches, sap netweaver (x2), sap netweaver 04, entry by component, ep migration, EP 5.0 MIGRATION TO NW04
    Then you upgrade the NW04 SP16 system to NW04S SP07.
    You can find documentation at :
    https://service.sap.com/instguides , Sap Netweaver, Release 2004S, upgrade.
    Take a look to the upgrade master guide and upgrade documentation.
    Good luck.
    Brad

  • Migrating from WebLogic to Sap netweaver j2ee application

    Hi all,
    We are migration a weblogic j2ee application in to sapnetweaver. In web logic, we have config.properties file which contains weblogic related roles, permissions and all configuration related to the application. If we want to use that file in sap netweaver how to configure it. 
    Can anyone please explain.
    Thanks in advance
    Points will be awarded for good answers
    Madhuri
    Message was edited by:
            jaya madhuri bai gaykwada
    Message was edited by:
            jaya madhuri bai gaykwada

    Hi,
    There is no file that contains all this properties you'll need to configure it all with the Visual Administrator.
    Regards,
    Pavel Sheynkman.

Maybe you are looking for