Configuring a common SLD

Hi,
We have been using SLD configured on XI Dev box. Now we have installed XI QA box and need to use the same DEV SLD.
How do i do this?. Do i add XI QA as the data supplier to DEV SLD ?
Thanks for your help.
Regards
Nainesh

Hi,
In QA system go to the transcation SLDAPICUST and maintain the URL/user and pass of the DEV sld system.
Also for the RFC destination SAPSLDAPI and LRCSAPRFC should be pointing to DEV SLD.
Then from QA system run SLDCHECK it should list the business systems in the SLD and should be succesful.
Regards,
Prakash

Similar Messages

JboException: JBO-33001: Cannot find the configuration file /common/bc4j.xc

Hello,
i'm new on this board and found it while i was searching for an solution of my problem.
I would like to apologize about my english, i try my best.
Now lets come to my problem.
I have 1 workspace with 2 projects.
in project 1 there are entity objects, view objects and an application object.
in project 2 there are jsp's action classes and form beans (i try to use Struts).
in one jsp i try this:
<jbo:ApplicationModule id="am" configname="*.*.*.bc4j.ReportingModule" releasemode="Stateful" />
<jbo: DataSource id="ds" appid="am" viewobject="*.*.*.bc4j.HilfeTexteView" />
<select name="TEXT" size="1">
<option value="-1" selected>sonstiges</option>
<jbo:RowsetIterate datasource="ds" changecurrentrow="true">
<option value="<jbo:ShowValue datasource="ds" dataitem="TEXT"></jbo:ShowValue>">
<jbo:ShowValue datasource="ds" dataitem="AUTOR"></jbo:ShowValue>
</option>
</jbo:RowsetIterate>
</select>
<jbo:ReleasePageResources releasemode="Stateful" appid="am" />
compilation finish successful, but when i try to run this jsp, there appear an error like:
oracle.jbo.JboException: JBO-33001: Cannot find the configuration file /common/bc4j.xcfg in the classpath
i think it dont work, because the configuration file bc4j.xcfg is in project 1 folder and i try to take it out of projeck 2 folder
I hope you know what i try to tell you
i will be very happy, when somebody could help me.
greetings
Rene

Please refer to other posts for the JboException.
JBO-33001: Cannot find the configuration file /model/common/bc4j.xcfg
Accessing BC4J ApplicationModule from another Project

What causes JBO-33001: Cannot find the configuration file /common/bc4j.xcfg

I know that the jbo exception message:
JBO-33001: Cannot find the configuration file /common/bc4j.xcfg
can be caused by several things including the file really not being there. But in my current case, I know it is there and can be found throgh the classpath, because I actually find it using Configuration.buildConfigurationFileNameFromClassPath and
Configuration.getConfiguration just before calling Configuration.createRootApplicationModule. Is there any way to turn on a diagnostic to find out what is really wrong?
I would also like to request an enhancement to give meaningful messages in the jbo exception.
Roger

This is on jdev 903 with patch running a local application attempting to connect to standalone OC4J 903. I think the error occurs before there is ever any attempt to make the connection to OC4J. Having one big catch-all exception for everything that can go wrong in creating the AM is pretty poor. I know in the past I have done manual editing of bc4j.xcfg and XML sentax errors cause exactly the same exception as not having the file at all. That is why I would at least like a list of all the causes behind the exception so I can go through and check them all.
Thanks,
Roger

JBO-33001: Cannot find the configuration file /common/bc4j.xcfg in the clas

I m trying to insert into the database from a form.My action class is given below.The application compiles okey, the else option works fine, but during the if option I get the following error:
oracle.jbo.JboException: JBO-33001: Cannot find the configuration file /common/bc4j.xcfg in the classpath
But I checked to see that the file is in the correct class path.What are the other reasons for the error to hapen?Please anyone!!
My action class is as below:
public class InsertDAAction extends Action
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException
String facingName=request.getParameter("facingName");
String facingDirection=request.getParameter("facingDirection");
if (facingName!=null && facingDirection!=null && facingName.equals("john") && facingDirection.equals("meyer")) {
String amDef = "AppModule";
String config = "AppModuleLocal";
ApplicationModule am = Configuration.createRootApplicationModule(amDef, config);
AppModuleImpl myAm = (AppModuleImpl)am;
myAm.createNewOrder(facingName,facingDirection);
return mapping.findForward("success");
else {
return mapping.findForward("fail");
}

I have set the dependency.
and its not in the WAR file.
I think I have the problem in this
ApplicationModule am = Configuration.createRootApplicationModule(amDef, config);
You can see the complete code above.IS there any alternative method for the commenction to the App Module
This have troubled me since almosta week but still cant get out.

Common SLD in XI . Is it possible?

Dear Expert,
Though SAP gives option of using commond SLD, we have problem working with common SLD.
We have the following landscape
DEV R/3 system (TS is D01) connecting to DEV XI System
QAS R/3 system (TS is Q01) connecting to QAS XI System
PRD R/3 system (TS is P01) connecting to PRD XI System
We have one Business System BS_SAP_R3 which is pointing to R/3 system
The aforesaid Business System is used across all the 3 XI landscapes. Now when we transport the interface from DEV to QAS & PRD let us know how this will work in common SLD scenario. How the pointer will dynamically change to different Technical Systems (TS).
with regards,
Ravi Siddam

Same WebAS ABAP business system can't be used in different landscape. You have to define separate business system for each landscape in SLD. While importing the business system in ID from SLD, if you import the one for Dev, then the scenario will always point to Dev R3.
Regards,
Prateek

Common SLD ports, PI7.0

Hi,
The situation is that we are trying to minimize the number of SLD for our PI systems and are facing ports and firewall issues.
Please guide me what all PORTS need to communicate with each other for common SLD.
Few I know are: 5NN00, 33NN and 39NN.
thanks in advance.
Cheers
AJ

Hi
If your SAP PI system is upgraded 7.1 system, which do have functionality of SLD Synchronization.
you can refer....
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/401b2bfb-3077-2b10-6ca1-aa7b7a3d2589?quicklink=index&overridelayout=true]
regards,
Ashutosh

Configuring TREX for sld

hello to all.
Why do i need to do the post installtion of the trex ""Configuring TREX" for sld"?
I have to do it?
Thanks
Menashe

If you are installing any component of 'NetWeaver', you should register it with Central SLD server of your landscape.
Same case with Trex too, that's why you have that post installation step there. However, it is not a 'Mandatory' step which needs to be done immediately after installation. But in future, you might require this. So you may proceed to do it after proper understanding of what is an 'SLD' even !
This step itself tells it's purpose as seen from below help page
http://help.sap.com/saphelp_nwpi711/helpdata/en/42/e33ae230ba3ee2e10000000a1553f6/content.htm
Following link will help you in understanding the SLD
https://www.sdn.sap.com/irj/sdn/nw-sld

EHP1 upgrade of solution manager-any effects in landscape due to common SLD

Hello All,
We have ECC,BI,SRM,XI,EP,MAM and BD in our setup and yes of course Solution Manager dev and prod
We have our SLD installed on solution manager production which is common for all the systems of the landscape
Now we have performed EHP1 upgrade if Solution manager dev and now we are planning on solution manager production
So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
Please let me know your suggestions
Rohit

> So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
The SLD is not affected.
However, SolMan EHP1 requires a LOT of separate notes to be applied.
Note 1172948 - SAP Solution Manager - Basic functions
Depending on what scenarios you use, you will also need to upgrade ST-PI in the external systems before EWAs will be again correctly created.
Markus

Configurations required in SLD,IR,ID,SM59,BD64 to Start with IDOCS

Hello all,
Can You Post me the Above details.
thanks,
Srinivasa

Hi Srinivas,
Let us explore the need for each steps and detail it now...
Step-1 : You need RFC destinations for placing the metadata of the IDoc.
Use transaction SM59 to maintain an RFC destination for the IDoc sender/receiver system.
This RFC destination is used to retrieve the IDoc metadata from the sender system.
The IDoc adapter needs these metadata to create the corresponding IDoc-XML message from the RFC stream.
Step-2 : Next You need IDx1 for getting IDoc metadata from the Sender system.
Use transaction IDX1 to assign a port (RFC destination) to the system that contains the metadata of the IDoc types.
Note:
There is a mechanism on the Integration Server that uses this RFC destination to retrieve and cache the metadata at runtime if it is not yet available on the Integration Server.
Nut-Shell:
Since IDoc metadata is cross-client, you should only assign one port for each system.
If several ports are assigned, ensure that they are all working.
This is Done in Partner Profile.
If you are not able to load the metadata from this system (because of administrative or security-related restrictions, for example),
you can also load it from a reference system (for example, a test system) and use transaction IDX2 to assign it to your production system afterwards.
For non-SAP systems, either the ports in transaction IDX1 have to point to a reference SAP system, or you copy the metadata with transaction IDX2.
I come to mean that if you double click the OutBound Parameter in the Partner Profile you will be allowed to choose the Idoc type like Matmas,Debmas blabla..
There after providing the receiver destination in that partner profile which is nothing but your Maintaining Metadata through a port,
which on double click leads to RFC destination alloted with a port to transfer its data from sender to receiver Server.
Step-3 : Goto SLD and do the following.
Access the System Landscape Directory (SLD) to maintain the technical systems for the sender and receiver business systems of your system landscape.
You have to define a technical system (and a client in the case of SAP systems) to which your business system belongs.
When you define a client number, you also have to specify the corresponding logical system name in the Technical System Browser.
Note:
The technical system configuration is not required if your business system is configured as a data supplier for the SLD.
Step-4 : Goto Integration Directory and do the folllowing.
Access the Integration Directory to define your business systems as services without party.
a) Either you can choose from the Objects Business Service where your client is defined for it.
With this Selected Business Service you just rightclick and choose ASSIGN TO BUSINESS SCENARIO.
b) Second choice is to choose the business system which was done in SLD.
Do the receiver determination and interface determination but since the adapter is not required to choose for Idoc dont do sender determination.
Note:
The IDoc adapter only uses the service definition (business system) together with the corresponding adapter-specific identifiers in the Integration Directory.
The maintenance of your IDoc sender system in the SLD is therefore not sufficient.
It is recommended that you assign your business system definition retrieved from the SLD to a service in the Integration Directory.
Nut-Shell:
Using this information about the system ID, client, and logical system name for a specific business system, the IDoc adapter is able to specify the corresponding service in the XML header. Routing is then based on service names.
You need the
 logical system, SAP system ID, and client for an IDoc receiver SAP system
 SAP system ID and client for an SAP system
 logical system for a non-SAP system.
This means that the business systems used for the routing definitions in the IDoc-XML message header are retrieved from the adapter-specific identifiers of the service definitions in the Integration Directory,
where for each business system client, the corresponding system ID, client, and logical system name is defined.
Caution:
Use the import function to retrieve the adapter-specific identifiers for a service (business system) to avoid double maintenance in the SLD and Integration Directory.
Step-5 : Steps in Integration Repository.
Export the IDoc in Imported Objects.
Double click the Idoc to view the structure.
This Idoc type is decided in the partner Profile.
See step-3 for further details.
Create the Interface Objects like
1.Data Type for Receiver File.
2.Message type which wrapps this Data type.
3.Interface Type.
a) For Sender Idoc just drag the Idoc name which you have loaDED IT IN YOUR imported objects.
b) For Receiver File It just wrapps the Message type of the file.
4.Message Mapping:
The Fields selected in the data type for the file should be the mandatory fields in the Idoc.
Since the Idoc is in the sender side,it just performs similar operation like selecting things from a database.
Begin and Other Attributes are neednt be worried to map.
The Mandatory fields which was chosen will need to be mapped with the target file.
5.Interface Map:
Just Wrapps the Message mapping.
Step-6 : BD64 is to Distribute the Idoc to Various Acceptors.
1.Create Model View.
2.Add Message Type to it.
3.So that it displays your model view with your Message type like MATMAS.
4.Goto Environment and click Generate Partner Profiles.
5.Executing it,you will get a log indicating the Partner,port and Outbound Parameters.
6.After Doing this goto Edit Menu available in the tool Bar and give Distribute.
7.After distributing it ,it shows your logical system name along with the technical name.
8.Now to fill the IDOCs with Data we have to go to Transaction bd10.
9.We can give our own selection criterias and select the list of materials accordingly.
10.Now to check whether the IDOCs has been correctly created and sent to the receiving system (in this case it is the SAP XI Server)
11.we have to check it out in Transaction WE05.
12.Now we can go to the Location we specified in the Configuration where the file will be created.

Development Configurations in the SLD

When a track is created, its Development Configuration is stored in the SLD. I can see this activity in the SLD's Server log, but I don't see otherwise where I can see a list of Development Configurations stored in the SLD. Anyone?

Hello Randy,
On the SLD main page navigate to Content Browser. On the subsequent page in the subset select "All Classes" and in the class dropdown select "Design Time Configuration". All the development configurations will be listed.
Hope this is what you were looking for.
Regards
Sidharth

Configure SLD during the Installtion

I am installing the XI and EP system with NetWeaver 04s. At the moment, I am at step "Cental SLD", pretty much the beginning of the installtion. It says that I have to enter my SLD configuration.
I have the option between:
- Configure local SLD
- Register in existing central SLD.
I am assuming that I have to have installed an SLD upfront. Is that true??? If yes, how can I install the SLD before the installtion routine?
Which option should I choose??
Thanks.
Regards
Go:khan

Enc
Go through the Urls and configure your SLD. If you do face problem post it back here.
Re: Central SLD Configuration.
Re: SLD configuration/move
---Mohan

System registered in SLD invisible in solution manager configuration

Hi
I have installed Solution Manager EHP1 / Oracle 10g / Win2003 on a VM. I ran into a issue in the Managed system configuration. The first step in the maanaged system configuration would help us select the satelllite systems which and configured in the SLD. Since systems were not yet added to SLD just the solution manager system shows up.
Here is the problem
I have added one system to the SLD using "Add Technical system" from http://localhost:50000/sld. This is a ABAP sysystem. The addition went through successfully however this does not reflect when I check the same in solution manager configuration "Managed system configuration"
As per the guide in the same page, I have checked on "Maintain Technical systems" Here too when I search for the system I created in SLD , I am not able to find it. Is there another way of manually maintaining the system in the SLD?
Any ideas as to why this might happen? Does one have to bounce the instance after adding systems to SLD/.... just wondering?
Ideas?
thanks
Ravi

Hi Rajeev
Thanks for your response however I fixed it. It looks like I had incorrectly mentioned the host in RZ70. Instead of mentioning the hostname of the solution manager I had mentioned the host name of the satellite system
The below link helped me fix the issue
http://help.sap.com/saphelp_nwpi71/helpdata/en/e7/01503ede925441e10000000a114084/content.htm
thanks
ravi

SLD Configuration

Hi, I've a problem with the SLD settings. I followed all the configuration steps: server activation, CR files importing, configuration of the SLD Data Supplier Bridge. I created an RFC destination and it is now running.
Then, if I try to test SLD Connection from the Web Dynpro Content Administrator toolbar, it is OK; but when I try to run my application or to create or maintain a JCO destination I get this error:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:997)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.getJCOClientStatus(DetailView.java:1039)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.updateJCOClientElement(DetailView.java:966)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.updateJCOReferences(DetailView.java:845)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.updateDeployableObjectReferences(DetailView.java:831)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.updateDeployableObject(DetailView.java:772)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.selectDeployableObjectPart(DetailView.java:727)
     at com.sap.tc.webdynpro.tools.explorer.DetailView.wdDoInit(DetailView.java:159)
     at com.sap.tc.webdynpro.tools.explorer.wdp.InternalDetailView.wdDoInit(InternalDetailView.java:410)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:275)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:539)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:421)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:539)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:397)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:619)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:262)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:806)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:359)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Do you have any suggestions in order to solve this problem?
Any hint would be highly appreciated. Thank you in advance!
Federica

You said you have created RFC destination, is it in sm59??
Have you created the JCO destinations and tested them? YOu need to update hosts files and also services files for message server port.
If on click of maintain JCO destinations, error is coming, then there is problem in server settings, try restarting server....
Once your JCO destinations are tested propertly, then webdynpro applications should work properly!
Abhijeet

Central SLD Configuration

Dears,
Recently we installed PI DEV and PI QAS server.At time of configuration we choose local SLD option for configuration.
But now we are getting requirement to configure central SLD.
So please confirm which strategy is good between them and if it is central SLD,Please suggest the
procedure to change local SLD configuration to central SLD.
Shivam

Hi Shivam
The SLD planning guide provided previously is the key source to plan, implement and run an SLD landscape
However what it may not deal with specifically is changing an existing SLD landscape to accomodate a local PI specific
SLD and a new Central SLD for Solution Manager (or other purposes)
Some things to consider when selecting Sync options
1) 1 Dual purpose SLD is not recommended - a central SLD might have different administration requirements than a PI specific SLD
2) Where possible do not change established import or export lines in either SLD
3) Keep all SLDs involved in the sync at the same J2EE version, SP landscape and CIM model/content
As the PI SLD can be productive critical - full consideration has to be given to this SLD as you can
still maintain systems manually in a central SLD manually - or indeed in Solution Manager itself (both manually and automatically via RFC) - therefore I would recommend a unidirectional sync from local PI SLD to Central SLD of PI landscape data only - either manually or automatically or indeed explore any available options to have data suppliers update both SLDs (there was some options similiar to this in older SLD versions - but I am not completely familiar with the latest SLD builds)
I would not however encourage full sync or CIM based sync as there maybe established CIM import lines on either SLD nor would I specifically encourage the Central SLD to influence data on the Local existing PI SLD
Best wishes
Stuart

Reg : Initial configuration for SLD

HI all ,
In the netweaver administration portal we have a option for deploy and change .when we click on that we have some options for initial configuration.Now the doubt that i have is that we have installed netweaver java stack on a server .We have configured local sld on that .We want to connect to a seperate ECC 6.0 system.That system doesnt have a sld configured for it .So we want to bring that system into our sld.I have configured NWA_01 i.e .configuration for local sld and NWA_03 i.e. create a connection to the SLD and Setting required authorizations for SLD (CIM client settings) in netweaver administrator portal.Do i need to configure only these or anything else other than this .One more thing is that when i enter the netweaver administrator portal i am getting these error messages.
System Landscape Directory is not accessible
Only local system can be administered
Any pointers regarding this.Thanx in advance .

Hi there,
The java stack is installed as standalone or ABAP+Java?
You need to maintian SLD server details in RZ70 on ECC server and test if data is sent successfully. Check for RFCs SLD_UC/SLC_NUC in ECC.
Also, check if SLD server is running.
regards, Sean.

Configuring a common SLD

Similar Messages

Maybe you are looking for