UCES 6.05 Development on NWDI 7.4

[Former Member]

I'm currently trying to bring UCES online for a client.

I'm having issues with modifying UCES using NWDI/NWDS.

The environment is setup like this:

UCES on its own box with Netweaver 7.00 SP30

NWDI on its own box with Netweaver 7.4

NWDS 7.00 running with Oracle JDK 1.4.2_19

The track is set up as a "modification" track with SAPUCES and FSCM_BD:

I have imported all the dependent SCs except UMEADMIN since it doesn't appear on the "Check-in" tab.

Then I go to NWDS, download the config and try to "Sync Sources..." and get these errors:

Not sure if this is UCES specific error or because of something not setup correctly with NWDI?

Or maybe I didn't follow the correct steps?

Thanks!

Eddy

[Former Member · Accepted solution]

OMG!

I created an OSS incident with SAP and they ended up re-assembling the SCA so now in the SMP there's a new version (update 1, I think).

Well, thanks for your answers, anyway!

Eddy

[former_member271886 · Accepted solution]

Dear Eddy,

Sorry for posting here,But I found very few people expert in areas of UCES...

We are facing issue in customizing UCES.Here is the list of issue I am facing

while customizing UCES.

• We are on SAP NW 7.0 with SAP UCES 6.0 installed on it.
• We have an urgent requirement to add java code ( payment gateway integration) Inside UCES with some JAR files.
• As we do not have NWDI set up on our UCES portal previously, we have set up the NWDI now.
• On checking component info of the portal system, we found that the component corresponding to biller direct is: com.sap.isu.ebpp
• From this we have identified that we need to add UCES SCA in our track (created in Step 3).
• Our BASIS team has downloaded the relevant SC from marketplace. On placing the SCA in /CMS/Inbox, we are able to view the SCA in CMS.
• However, on checking-in the SCA, and then trying to import the same in the NWDI track, we are getting error "Import failed".
• Can you please guide me if we have to modify the JSP content_billList_html under and have the DC com.sap.isu.ebpp visible in our system info then which all SCA we have to import and why my SCA UCES is getting import failed.

Here is the thread

Regards

Imran Khan

[Former Member]

Thanks to both Jun and Stefan!

I have verified that the file NOT corrupt since I can unzip it with JAR.

I have also looked into the SP_MANIFEST.MF file. In it, the entry for approvalstatus is:

pr_approvalstatus: EXTERNAL

So what does it mean to have a value of "EXTERNAL" (since this file comes from SAP)?

How can I have a value of "ASSEMBLED"?

Thanks!

Eddy

[Stefan-EA]

Eddy,

Did you add 7.00 UMEADMIN SC to the CMS inbox?

[Former Member]

Yes, the file UMEADMIN30_0-10003471.SCA is physically on the file system in the inbox directory together with the other SCA files.

I have read somewhere that it would only appear in the "check in" tab if there's a build-time dependency.

Since it's a "modification" track, all dependencies are pre-setup by SAP. How might I check to see that there is indeed a build-time dependency or not?

Thanks!

Eddy

[junwu]

first check the sld to see if  the dependency is defined or not. i think it should be there if it is required for this SC. update the cms content.

when you add SC to the track, it automatically pull all the dependency, after that you can add your own dependency if you are sure it(umeadmin) is required,

[Former Member]

As you can see in my original post, in the 1st image, UMEADMIN is already a dependency of FSCM_BD. This was automatically pulled in when I added FSCM_BD. I didn't add it.

So the question is why is it not appearing in the check in list?

Is there a way to find out what kind of dependency it is (build-time, runtime, etc.)?

Thanks!

Eddy

[junwu]

check if this helps

SCA Files are not visible on the check-in tab in transport studio of CMS

The behaviour (and the potential causes) is described in SAP note:
#1259604 - CMS check-in tab: Not all files from inbox are displayed

This implies that an SCA downloaded from e.g. a development system (i.e. not assembly step) will NOT be visible in the Inbox. Technically this can be checked by looking at the SAP_MANIFEST.MF of the SCA. The "pr_approvalstatus" must be "ASSEMBLED".

Actually there are two filters when you check in a file:
the first is the track configuration itself. The files in the CMS/inbox will be shown on the check in tab if they were really conigured on the track data tab in the landscape configurator. The second filter is the SAP_MANIFEST.MF file inside the SCA. If it has not the proper structure then it won't be possible to check in. This file guarantees that an SCA file is allowed for check in.

[Stefan-EA]

The file might be corrupt. Try downloading it again and adding it to the inbox.

You can validate the SCA with "jar -tvf <filename>"