problem with CBS

[Former Member]

Hi all,

I have installed the JDI SP9 on WAS SP9. and then i was trying out Senario 2+ given at help.sap.com.

But while following given steps i got following error when i tried to activate the activity.

<i>Build number assigned: 7

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "CVX_TSTTRACK_D" at Node ID: 3,464,550

[id: 9; parentID: 0; type: 4]

[options: FORCE ACTIVATE PREDECESSORS]

REQUEST PROCESSING started at 2005-05-12 09:16:57.44

===== Pre-Processing =====

List of activities to be activated:

1 activity in compartment "lti.com_DTR_TEST_COMPONENT1_1"

Solving Build Error

[seq. no 11][created by CMSADM at 2005-05-12 03:45:45.0][ID 9d44d2e0c29111d99f9c0002e3562ffe]

Analyse dependencies to predecessor activities... started at 2005-05-12 09:16:57.456

Analysing compartment "lti.com_DTR_TEST_COMPONENT1_1"

The following 2 predecessors have to be added to request 9:

"Initail Development of J2EE Application" [seq. no 10][created by CMSADM at 5/11/05 2:28 PM][ID 17dcced1c1f711d9a47a0002e3562ffe]

"Initial Development" [seq. no 7][created by CMSADM at 5/11/05 8:55 AM][ID 4d296656c1f411d985ef0002e3562ffe]

Analyse dependencies to predecessor activities... finished at 2005-05-12 09:16:57.472 and took 16 ms

Analyse activities... started at 2005-05-12 09:16:57.472

Synchronizing component "lti.com/appl/tax" from repository... finished at 2005-05-12 09:16:57.804 and took 111 ms

Component "lti.com/appl/tax" is to be CHANGED by this activation.

Synchronizing component "lti.com/appl/tax/servlet" from repository... finished at 2005-05-12 09:16:57.898 and took 94 ms

Component "lti.com/appl/tax/servlet" is to be CHANGED by this activation.

Synchronizing component "lti.com/appl/taxappl" from repository... finished at 2005-05-12 09:16:57.962 and took 64 ms

Component "lti.com/appl/taxappl" is to be CHANGED by this activation.

3 components to be build in compartment "lti.com_DTR_TEST_COMPONENT1_1"

Analyse activities... finished at 2005-05-12 09:16:58.088 and took 616 ms

Calculate all combinations of components and variants to be built...

<b>"lti.com/appl/tax" variant "default"

"lti.com/appl/tax" variant "default" cannot be built. Activation will fail.

INVALID dependency is declared to public part: tax.</b>

<b> [DC 149 variant "default"][SC 9 "lti.com_DTR_TEST_COMPONENT1_1"] using [PP tax of DC 148 at Build-Time Dependency]

"lti.com/appl/tax/servlet" variant "default"

"lti.com/appl/tax/servlet" variant "default" cannot be built. Activation will fail.

INVALID dependency is declared to public part: api.</b>

[DC 150 variant "default"][SC 9 "lti.com_DTR_TEST_COMPONENT1_1"] using [PP api of DC 148 at Build-Time Dependency]

"lti.com/appl/taxappl" variant "default"

Prepare build environment in the file system... started at 2005-05-12 09:16:58.198

Prepare build environment in the file system... finished at 2005-05-12 09:16:58.198 and took 0 ms

===== Pre-Processing ===== finished at 2005-05-12 09:16:58.198 and took 758 ms

Change request state from PROCESSING to FAILED

ERROR! The following problem(s) occurred during request processing:

ERROR! The following error occurred during request processing:Activation failed due to component "lti.com/appl/tax" variant "default". The component is BROKEN.

ERROR! The following error occurred during request processing:Activation failed due to component "lti.com/appl/tax/servlet" variant "default". The component is BROKEN.

REQUEST PROCESSING finished at 2005-05-12 09:16:58.198 and took 758 ms</i>

i thought error is in the declaring and using public part. but i have checked the steps for the same in the tutorial at help.sap.com

Thanks in advance

[wolf_hengevoss]

Dear all,

I feel that there is some clarification needed regarding development scenarios with the JDI: The discussed sentence of course has to read "Please note that what's called "scenario 2" will <b>not</b> be supported in the future so I recommend that you concentrate on the other tutorials." (sorry for the typo).

The reason behind this is that scenario 2 adds two services to development scenario 1 that are handled easier and more comprehensively by CBS and CMS used in scenarios 2+ and 3:

• Creation of development configurations in a tool "Configuration Wizard": This is replaced by the processes in the CMS.

• Definition of a central build process: A manually defined build process in the "Development Component Utility Script" is replaced by the CBS build.

That's why scenario 2 became obsolete. Therefore in SAP NetWeaver 2004 there are only development scenarios 1, 2, and 3 left as recommended scenarios. To add some additional information: It was stated correctly that "Scenario 2 is a simple case of scenario 3 (just one track)". So we will only speak of two scenarios in the future distinguishing between development using only the DTR as central source code versioning system (former scenario 1) and development of components with the full Development Infrastructure (as in scenarios 2+ and 3). Here two cases will be described: Using one track (former scenario 2+) and layered development (former scenario 3).

<b></b>

Best regards

Wolf Hengevoss

SAP AG

Product Mgmt. Software Life Cycle Mgmt.

[Former Member]

Hi,

it seems that your <b>tax</b> component defined in scenario 2+ use <b>DTR_TEST_COMPONENT1_1</b> which is defined in scenario 1 and hence visible only to DTR but not to CBS and CMS.

As a result of it CBS can't build the project because of missing dependencies.

Does it helps?

In addtition:

Scenarion 2+ is a simple case of scenario 3 (just one track) so no surprise it was removed but why scenario 2 was moved? Sombody knows?

Best Regards,

Victor.

Best Regards?

Message was edited by: Victor Shafran

[Former Member]

HI Jain,

Recently i received a mail by SAP mentioning that time being Scenario 2, 2+ will not work, try to concentrate on other scenarios.Mean while Have you done with Sceanrio 1 (team Oriented),Scenario-3(Layered).

Regards,

RK

[Former Member]

Hi,

I'd be curious to see what SAP says on the subject. We have scenario 2+ working with SP11. There were problems getting the configuration correct, but it does work. We did not have the problem described in the original message in this thread, so I can't help you there.

Rob

[Former Member]

Hi Rob Ericsson,

Following is the message got from SAP related to Scenario2 recently.

-

---

-

---

Dear Sir or Madam,

Thanks for your kind words on my article. To find tutorials regarding the JDI in the Developer Studio choose Help --> Help Content -->

SAP NetWeaver Developer Studio Documentation --> SAP Web AS for Java Applications --> Development Manual -->

Working with the SAP NetWeaver Java Development Infrastructure --> Getting Started – Development Infrastructure --> -->

<b>Please note that what's called "scenario 2" will be supported in the future so I recommend that you concentrate on the other tutorials</b>.

Best regards,

Wolf Hengevoss

Product Mgmt. Software Life Cycle Mgmt.

-

---

-

---

In your case if Scenario-2 is working suggest us what are the precautions we have to take ..

Thnaks

RK

[Former Member]

Hi,

We followed the steps outlined in the NWDS help tutoial on Scenario 2+ to configure our development track. We have a WebDynpro application, so some of the specifics are different, but the basic operations are the same.

I would read the note that as saying that you should not use Scenario 2, especially in conjunction with the disclaimer in the tutorial that there is no supported way to migrate to another scenario, but it is hard to tell.

-r