Template finished with errors - Technical configuration of BI-Java

Hi experts,

Scenario:

Portal on NWP

SLD on NWS

BI on NBI

We have maintained the JCo Destinations to NBI on NWP/WebDynpr Content Admin Console - Tested succesfully

On NWP we can test and log on to our central SLD on NWS.

But while running the template Technical configuration of BI-Java still several errors occure:

1. Importing certificates to NWP and to NBI

Error: RuntimeException invoking method storeTrustedTicketIssuers

Step: Import of the BI System Certificate from file system to the J2EE engine

Error: RuntimeException invoking method storeTrustedTicketIssuers

Step: Import of the BI System Certificate (client 000) from file system to the J2EE engine

2. Errors with the JCo Destinations

using https

Error: Failed to delete JCO client connection 'BI_METADATA' on 'NWP.SystemHome.<SERVER>'

Step: WD JCO Dest. BI_METADATA

Error: Failed to delete JCO client connection 'BI_MODELDATA' on 'NWP.SystemHome.<SERVER>'

Step: WD JCO Dest. BI_MODELDATA

Error: Failed to delete JCO client connection 'WD_ALV_METADATA_DEST' on 'NWP.SystemHome.<SERVER>'

Step: WD JCO Dest. WD_ALV_METADATA_DEST

Error: Failed to delete JCO client connection 'WD_ALV_MODELDATA_DEST' on 'NWP.SystemHome.<SERVER>'

Step: WD JCO Dest. WD_ALV_MODELDATA_DEST

using http:

like the errors of https except not while deleting but while creating

3. Wrong Entry for SLD in Destinations - Template protocol

The Destinations:

Arguments

NAME : BI_METADATA 

CLIENT : 200 

MSGSERVERNAME : <BI-SERVER>

SYSTEMNAME : NBI 

USER : SAPJSF 

PASSWORD : % secure content % 

LOGONGROUP : SPACE 

SLD_HOST : <PORTAL-SERVER>

SLD_PORT : 50100

SLD_USER : SLDDSUSER 

SLD_PASS : % secure content % 

USERTYPE : DEFINED_USER

Where is this SLD defined - that is the local SLD of the Portal not our central SLD witch the Portal is connected (Test succesfully executed)??

Any ideas

kind regards and thanks in advance

Edited by: Tom Uhl on Sep 15, 2008 11:55 AM

Problem solved - wrong settings in template installer if there is no local SLD on the portal itself - editing the entries for SLD Host and the destinations in VA manually - working