cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

Activation Error: "unknown entity type 'Archive'"

Former Member
0 Kudos

Hi,

I have a problem with a External Library - DC:

1) Add a new DC of type External Library

3) Go to Windows Explorer and copy a JAR file

4) Go to Navigator tab of the Development Configurations Perspective and paste the JAR files into the libraries folder

5) Right-click JAR file and choose Development Component => Add to Public Part

6) Choose the "Provide an API for developing/compiling other DCs" radio button from the popup

7) Check-In Activity

😎 When I want to activate the Avtitity I get an CBS Build Error:

-


Build Plugins Version 6.40.0.111 (ExternalArchivePlugin, 630_VAL_REL ) from 2005-09-08 23:39:44 CEST

Building development component 'dc/isolib', vendor 'isogmbh.de', type 'External Library'

software component 'ATLANTIK_CERTIFIED_VACANCY', vendor 'isogmbh.de'.

location 'E11_ATLCERVA_D'.

source code location 'http://isosap11:50300/dtr/ws/ATLCERVA/isogmbh.de_ATLANTIK_CERTIFIED_VACANCY/dev/active/'.

General options:

convert *.xlf to *.properties: yes

include sources for debugging: yes

Reading BuildInfrastructure extension from DC tc/bi/util (vendor sap.com)

Added technology 'sap.com/tc/bi/core'

Error: unknown entity type 'Archive'.

Cleaning up.

-


Does anyone know why the entity type 'Archive' is unknown in the CBS?

Regards,

Claus

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

There was a bug in the build plugin. Please check Note 887465 if this is the problem you are experiencing.

Former Member
0 Kudos

Hi,

great. That's exactly my error. We will install the Patch.

Thanks,

Claus

Answers (2)

Answers (2)

Former Member
0 Kudos

<i> [..] In the Developer Studio it is possible to create a DC under the "built-in" Development Configuration called "Local Development". This is a static pool of Build Plugins shipped with the DevStudio which won't be updated when you import new SCAs by the CMS. It should only be used when no JDI has been installed.

You also can create a local DC within an existing Development Configuration. The benefit is that you are always using the latest Build Plugins coming from CBS but the DC sources aren't checked in in DTR.

For you it means that the patch provided on the Service Marketplace is for feeding your CMS tracks. The static pool in the DevStudio can't be fixed this way. [...] </i>

As a quick fix for the NWDS plugins you can follow these steps:

1. Go to the folder <i>C:\SAP\JDT_SP14\eclipse\plugins\com.sap.tc.ap\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\externalarchive\_comp</i>

2. Make a backup copy of the file <i>.dcdef</i> and store it in a save place

3. Delete the file <i>.dcdef</i>

4. Still in the same folder create a new <i>.dcdef</i> file with the following content

<?xml version="1.0" encoding="UTF-8"?>
<development-component version="1.0">
  <name>tc/bi/bp/externalarchive</name>
  <vendor>sap.com</vendor>
  <component-type>
    <vendor>sap.com</vendor>
    <type>Build Plugin</type>
  </component-type>
  <external/>
  <dependencies>
    <dependency>
      <dc-ref>
        <name>tc/bi/javatech</name>
        <vendor>sap.com</vendor>
      </dc-ref>
      <pp-ref>def</pp-ref>
      <at-runtime/>
    </dependency>
  </dependencies>
</development-component>

You should now be able to build your exteranl archive in NWDS without errors.

0 Kudos

Hi Claus,

What is the version of NWDS, JDI and WAS. I hope they are all above SP12. External library DC was introduced in SP12 as far as i know.

Also if they are all above SP12 then you also need to make sure that the three sca files that you have checked in during the setting up of tracks are consistent with the SP level of JDI.

Hope this helps.

Regards

Sidharth

Former Member
0 Kudos

External Library was already available before SP12

Seems like something went wrong with the import of the 3 base sca's.

0 Kudos

Sorry for that info then. I thought i read somewhere that External Library DC was introduced in SP12.

Regards

Sidharth

Former Member
0 Kudos

It was introduced with SP12, you're right there.

If the build plugins (i.e. SAP_BUILDT) would have been too old then the CBS wouldn't have found the correct plugin (DC) to actually build the DC and there would be an error message in the request log stating that a DC "tc/bi/bp/..." could not be found. There would be no build log at all since the CBS would only process the request but not start a real build.

Since the build was started in this case the problem had to be with the plugins themselves.

Best regards,

Marc

Former Member
0 Kudos

How do we incorporate these fixes into the development environment (Developer Studio)? The instructions for the patch say "Follow the instructions in the official documentation how to import the Build Pluging into your development landscape."

What official documentation?

I can of course deploy the component to the J2EE engine, but that doesn't do me any good when I'm trying to build an External Library DC....

0 Kudos

Hi Ken,

Firstly you will have to deploy the relevant sca file into your J2EE engine using SDM and then for importing the same in your dev environment you have to take the new sca file place it in the CMS inbox and from there checkin the new file into your track.

This will fix the dev env.

Regards

Sidharth

Former Member
0 Kudos

Development environment = NetWeaver Developer Studio

Development Landscape = Track definition in CMS

What they are saying is that you must import the build plugin into your Development Landscape. This involved putting it in the CMS inbox on the file system of the JDI server, checking it into the track and then import it into all track stages using CMS Transport Studio.

Once you've done this, you must re-import the Development Configuration in NWDS to get the new version into your local development environment.

Former Member
0 Kudos

Re-importing the development configuration is only necessary if you changed the track configuration.

After re-importing archives (SCAs) into a a track you only need to sync those archives from the NWDS (e.g. by selecting "Re-sync Archives" from the context menu on the appropriate compartment in the "Active DCs" view). There is no need to remove and re-import the whole configuration from the client.

Former Member
0 Kudos

Thanks for the correction

Former Member
0 Kudos

My apologies, I should have mentioned that while I'm using DCs and SCs, I'm not currently using the JDI (we're in the process of getting the JDI configured). I'm using DCs in the LocalDevelopment SC to get familiar with SAP's development environment.

So, I guess what I need to know is how to patch NWDS with the updated jar files - is it as simple as replacing the NWDS jar files with the corresponding jar files supplied in the patch?

0 Kudos

Hi Ken,

It would really help if you could explain in detail the error you are getting and when.

From what i have understood you are developing DC's under Local Dev and then while doing a DC build you are getting the error mentioned above.

In my opinion in order to resolve this problem you may have to upgrade your NWDS to SP14.

Let us know where you are getting stuck.

Regards

Sidharth

Former Member
0 Kudos

I am at SP14 already. Here's the error message:

Nov 15, 2005 7:16:09 AM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: example.ca/struts-libs: Build failed for example.ca/example.ca/struts-libs(MyComponents) in variant "default": unknown entity type 'Archive'.

------------------------------------- Build log ------------------------------------------------------
Development Component Build (2005-11-15 07:16:03)
  Component name: example.ca/struts-libs
  Component vendor: example.ca
  SC compartment: MyComponents
  Configuration: LocalDevelopment
  Location: local
  Source code location: ZCS8M@CIW03030328
  DC root folder: D:src.dtcLocalDevelopmentDCsexample.caexample.castruts-libs_comp
  DC type: External Library
  Host: CIW03030328

DC Model check:
		[dcmake] All used DCs are available locally
		[dcmake] validating dependency to build plugin "sap.com/tc/bi/bp/externalarchive"
		[dcmake] DC model check OK

Start build plugin:
		[dcmake] using build plugin: sap.com/tc/bi/bp/externalarchive
		[dcmake] starting build plugin from : D:Program FilesSAPJDTeclipsepluginscom.sap.tc.apcompSAP_BUILDTDCssap.comtcbibpexternalarchive_compgendefaultpubliclib



Build Plugins Version 6.40.0.111  (ExternalArchivePlugin, 630_VAL_REL ) from 2005-09-09 23:37:14 CEST 
Building development component 'example.ca/struts-libs', vendor 'example.ca', type 'External Library'
         software component 'MyComponents', vendor 'sap.com'.
         location 'local'.
         source code location 'ZCS8M@CIW03030328'.
General options:
 convert *.xlf to *.properties: yes
 include sources for debugging: yes

Reading BuildInfrastructure extension from DC tc/bi/util (vendor sap.com)
Added technology 'sap.com/tc/bi/core'
<b>Error: unknown entity type 'Archive'.</b>
Cleaning up.