cancel
Showing results for 
Search instead for 
Did you mean: 

DI installation for NWDI

Former Member
0 Kudos

Dear Experts,

I have installed ECC/ EP on the same server and while installation not selected NWDI.

Now I want NWDI so that developer can work? How do I start with? What things needs to be installed?

Have checked the Service market place for download the DI packages from the link below

Support Packages and Patches

Support Packages and Patches" SAP NetWeaver" SAP NETWEAVER" SAP NETWEAVER 7.0" Entry by Component" Development Infrastructure

Development Infrastructure

ADOBE DOCUMENT SERVICES 7.00

BI META MODEL REPOSITORY 7.00

BI UDI 7.00

DI BUILD TOOL 7.00

DI CHANGE MGMT. SERVER 7.00

DI COMPONENT BUILD SERVER 7.00

DI DESIGN TIME REPOSITORY 7.00

From the above we can see there are 4 different things from DI side. So what needs to be downloaded to install the DI for the nwdi if not installed during the ECC installation?

Regard

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

You need not reinstall. You can install the additional usage types required for DI through JSPM. Thats all you need to do.

The following note explains how exactly you should do this for different usage types:

Note 883948 - NW 7.0(2004s): Inst.Add.Java Usage Types/Software Units

According to the note, for DI you will need the following usage types to be imported.

DICBS*_.SCA |DI COMPONENT BUILD SERVER 7.00

DICMS*_.SCA |DI CHANGE MGMT SERVER 7.00

DIDTR*_.SCA |DI DESIGN TIME REPOSITORY 7.00

You have to download these usage types from serice marketplace and then place it in the JSPM inbox and deploy exactly as mentioned in the note. The note is self explanatory.

If you need to know how to use JSPM, read the following:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/89ac337d-0c01-0010-b6ae-a9f2b88a...

http://help.sap.com/saphelp_nw70/helpdata/en/87/4797422930c56ae10000000a155106/frameset.htm

Regards,

Jazz

Former Member
0 Kudos

Hi Jazz,

I think I have gone through the information you have provided. But I like to mention few details.

I have updated my JSPM till 12 and while selecting the Add on , the packages was not read.. It read from teh same option of Business package.. and when tried selecting hte 3 DI components, it gave error with DI_CMS. So I continued with the 2. and CMS is giving the error message as below.

Any information u would like to share?

root@sapdev # pwd

/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08

::::::::::::::

BATCHCONFIG_04.ERR

::::::::::::::

PerfTimes : loadNativeLayer: loading jperflib failed. /sap/sapmnt/DEV/exe/libjperflib.so: ld.so.1: java: fatal: /sap/sapmnt/DEV/exe/libjperflib.so: wrong ELF class: ELFCLASS64

::::::::::::::

BATCHCONFIG_05.ERR

::::::::::::::

PerfTimes : loadNativeLayer: loading jperflib failed. /sap/sapmnt/DEV/exe/libjperflib.so: ld.so.1: java: fatal: /sap/sapmnt/DEV/exe/libjperflib.so: wrong ELF class: ELFCLASS64

09/01/22 19:33:24 - com.tssap.dtr.pvc.repository.RepositoryManager - LOGGING CONFIGURATION

09/01/22 19:33:24 - com.tssap.dtr.server.servlet.WebdavMethod.tracePerformanceStatistics - LOGGING CONFIGURATION

09/01/22 19:33:24 - /Applications/DTR/Propagation - LOGGING CONFIGURATION

09/01/22 19:33:24 - com.tssap.dtr.server.servlet.WebdavServlet - LOGGING CONFIGURATION

09/01/22 19:33:24 - SAP/BC_DTR - JDBCCONNECTOR

09/01/22 19:33:24 - dtr - WEB

09/01/22 19:33:24 - sap.com/tcdtrenterpriseapp monitoring configuration - MONITORING CONFIGURATION

09/01/22 19:33:24 - ***********************************************************

Jan 22, 2009 7:33:43 PM Info: End of log messages of the target system.

Jan 22, 2009 7:33:43 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 22, 2009 7:33:43 PM Info: Finished successfully: development component 'tc/dtr/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_C'/'1521448'/'0', grouped

by software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'

Jan 22, 2009 7:33:43 PM Info: Starting to save the repository

Jan 22, 2009 7:33:47 PM Info: Finished saving the repository

Jan 22, 2009 7:33:47 PM Info: Starting: Initial deployment: Selected development component 'tc/jdi/heartbeat/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_

C'/'1497030'/'0' will be deployed.

Jan 22, 2009 7:33:47 PM Info: SDA to be deployed: /sap/sap/DEV/DVEBMGS10/SDM/root/origin/sap.com/tc/jdi/heartbeat/enterpriseapp/MAIN_APL70VAL_C/0/149

7030/tcjdiheartbeat~enterpriseapp.sda

Jan 22, 2009 7:33:47 PM Info: Software type of SDA: J2EE

Jan 22, 2009 7:33:47 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 22, 2009 7:33:50 PM Info: Begin of log messages of the target system:

09/01/22 19:33:47 - ***********************************************************

09/01/22 19:33:47 - Start updating EAR file...

09/01/22 19:33:47 - start-up mode is lazy

09/01/22 19:33:47 - EAR file updated successfully for 117ms.

09/01/22 19:33:47 - Start deploying ...

09/01/22 19:33:48 - EAR file uploaded to server for 50ms.

09/01/22 19:33:48 - Successfully deployed. Deployment took 523ms.

09/01/22 19:33:48 - Application : sap.com/tcjdiheartbeat~enterpriseapp

09/01/22 19:33:48 -

09/01/22 19:33:48 - heartbeatJDI - WEB

09/01/22 19:33:48 - sap.com/tcjdiheartbeat~enterpriseapp monitoring configuration - MONITORING CONFIGURATION

09/01/22 19:33:48 - ***********************************************************

Jan 22, 2009 7:33:50 PM Info: End of log messages of the target system.

Jan 22, 2009 7:33:50 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 22, 2009 7:33:50 PM Info: Finished successfully: development component 'tc/jdi/heartbeat/enterpriseapp'/'sap.com'/'MAIN_APL70VAL_C'/'1497030'/'0'

, grouped by software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'

Jan 22, 2009 7:33:50 PM Info: Starting to save the repository

Jan 22, 2009 7:33:53 PM Info: Finished saving the repository

Jan 22, 2009 7:33:53 PM Info: Starting: Initial deployment: Selected software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117

061443''/'0' will be deployed.

Jan 22, 2009 7:33:53 PM Info: Finished successfully: software component 'DI_DTR'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117061443''/'0'

Jan 22, 2009 7:33:53 PM Info: Starting to save the repository

Jan 22, 2009 7:33:56 PM Info: Finished saving the repository

Jan 22, 2009 7:33:56 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Jan 22, 2009 7:33:56 PM Info: -


Deployment was successful -


Jan 22, 2009 7:34:00 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp

Jan 22, 2009 7:34:00 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63109

Jan 22, 2009 7:34:04 PM Info: Opened client connection to sapdev (IP address sapdev/10.150.203.95, remote port 63508)

Jan 22, 2009 7:37:23 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp

Jan 22, 2009 7:37:23 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63508

Jan 22, 2009 7:37:41 PM Info: Start logging to '/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08/OperateSDM_01.LOG'

Jan 22, 2009 7:37:41 PM Info:

Jan 22, 2009 7:37:41 PM Info: ==========================================

Jan 22, 2009 7:37:41 PM Info: = Starting to execute command 'ping' =

Jan 22, 2009 7:37:41 PM Info: ==========================================

Jan 22, 2009 7:37:41 PM Info: Sending "ping" command to the SDM server...

Jan 22, 2009 7:37:41 PM Info: Opened client connection to localhost (IP address localhost/127.0.0.1, remote port 63565)

Jan 22, 2009 7:37:42 PM Error: Wrong password supplied - Request for Logon rejected. Remaining logon attempts until SDM server will be shut down: 2

Jan 22, 2009 7:37:42 PM Error: SDM server is running, but authentication failed because of wrong password.

Jan 22, 2009 7:37:42 PM Info: Close client connection to localhost/127.0.0.1, remote port 63565

Jan 22, 2009 7:37:42 PM Error: Processing error. Return code: 104

Jan 22, 2009 7:39:12 PM Info: Start logging to '/sap/sap/DEV/DVEBMGS10/j2ee/JSPM/log/log_2009_01_22_19_06_08/OperateSDM_01.LOG'

Jan 22, 2009 7:39:12 PM Info:

Jan 22, 2009 7:39:12 PM Info: ==========================================

Jan 22, 2009 7:39:12 PM Info: = Starting to execute command 'ping' =

Jan 22, 2009 7:39:12 PM Info: ==========================================

Jan 22, 2009 7:39:12 PM Info: Sending "ping" command to the SDM server...

Jan 22, 2009 7:39:12 PM Info: Opened client connection to localhost (IP address localhost/127.0.0.1, remote port 63590)

Jan 22, 2009 7:39:12 PM Error: Wrong password supplied - Request for Logon rejected. Remaining logon attempts until SDM server will be shut down: 1

Jan 22, 2009 7:39:12 PM Error: SDM server is running, but authentication failed because of wrong password.

Jan 22, 2009 7:39:12 PM Info: Close client connection to localhost/127.0.0.1, remote port 63590

Jan 22, 2009 7:39:13 PM Error: Processing error. Return code: 104

Jan 22, 2009 7:39:14 PM Info: Opened client connection to sapdev (IP address sapdev/10.150.203.95, remote port 63598)

Jan 22, 2009 7:39:14 PM Info: -


Starting validation -


Jan 22, 2009 7:39:14 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending

Jan 22, 2009 7:39:14 PM Info: Update strategy: UpdateLowerVersions

Jan 22, 2009 7:39:14 PM Info: Starting deployment prerequisites:

Jan 22, 2009 7:39:18 PM Info: Loading selected archives...

Jan 22, 2009 7:39:18 PM Info: Loading archive '/usr/sap/DEV/DVEBMGS10/SDM/program/temp/DICMS14_0-10003499.SCA'

Jan 22, 2009 7:39:24 PM Info: Selected archives successfully loaded.

Jan 22, 2009 7:39:25 PM Error: Unresolved dependencies found for the following SDAs:

1.: development component 'tc/SL/CMS/PCS'/'sap.com'/'MAIN_APL70VAL_C'/'1535381'/'0'

dependency:

name: 'tc/com.sap.tmw.clients/_ctsa_client'

vendor: 'sap.com'

There is no component either in SDM repository or in Deployment batch that resolves the dependency.

dependency:

name: 'tc/di/scm/transport_api'

vendor: 'sap.com'

There is no component either in SDM repository or in Deployment batch that resolves the dependency.

Deployment will be aborted.

Jan 22, 2009 7:39:25 PM Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.

Deployment will be aborted.

Jan 22, 2009 7:39:25 PM Error: Prerequisites were aborted.

Jan 22, 2009 7:39:29 PM Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) select

ed. Select at least one.

Deployment will be aborted.

Jan 22, 2009 7:39:34 PM Info: -


Ending validation -


Jan 22, 2009 7:39:34 PM Info: Delete the files from /usr/sap/DEV/DVEBMGS10/SDM/program/temp

Jan 22, 2009 7:39:34 PM Info: Close client connection to sapdev/10.150.203.95, remote port 63598