Grouping of OSB projects

Hi!
I have got a problem: I would like to group OSB projects.
We can put more business projects into OSB. These business projects contain of more OSB projects. I would like to see this on OSB console (project explorer):
- businsess project 1
- OSB project 1.1
- OSB project 1.2
- OSB project 1.3
- businsess project 2
- OSB project 2.1
- businsess project 3
- OSB project 3.1
- OSB project 3.2
Ok, I can implement this in OSB console to add new project and move given OSB project to this.
But how could I do this in eclipse? If I deploy OSB components to server, they will be deployed in root. Ok, I could move these manually but this is not so good solution (I have an Ant script which can deploy).
So how could I group my OSB projects in eclipse or in ant script?
Thanks!
Regards,
Viktor

Hello Viktor,
In OSB, you may have only one configuration project (on server) and inside that you may have as many as you want, OSB projects. So if you want to categorize projects from business perspective (businsess project 1, businsess project 2 etc..) then businsess project n will be a OSB project and OSB project n.n will be a folder inside businsess project n
In short, you can not create a OSB project inside another OSB project. I am not sure if I understood your question, right but this is what currently available. For any enhancement which you want, you may raise an ER with support.
Regards,
Anuj

Similar Messages

How to create a new Oracle OSB project automaticaly with script without IDE

Hello,
I want to create automatically an "Oracle service bus project" and an "Oracle service bus configuration project" with scripts (ANT or Maven or ...) without using IDE, without using workshop or Eclipse. I want to create automatically (ANT or Maven) just a skeleton of an OSB project witch i can use after in workshop.
I want to create 1 "Oracle service bus configuration project" with many "Oracle service bus project" automatically (ANT or Maven or scripts) witch i can use after in workshop. How to create a new Oracle OSB project automaticaly with script without IDE ? How can i do this ?
I'm using Oracle service bus 10.3.1
Thank you for your help.

Thank you for your response,
I do not want to just create the services (proxy services and business services) but I want to create a template for 40 OSB project with the same scripts ANT/Maven.
Template="Oracle service bus configuration project" + "Oracle service bus project" + services of 40 OSB projects
The goal is that I have more than 40 projects to create and just the name of the projects that changes (when I say the name of the project ie the name of the OSB project, the name of proxy services and the name of business services ).
So I want to give my script (ANT/Maven) the name of 40 OSB project and the script must generate the skeleton of the 40 projects at once time and after generation of skeleton of the 40 project, I will import them in the workshop to add manually mapping and routing and other things that differs from one project to another.
So i want to generate automatically a skeletons of 40 OSB projects using a script (ANT / Maven) and I give to the script juste the names of the 40 projects.
I want to create a "Oracle service bus configuration project" and "Oracle service bus project" automatically of 40 OSB projects (ANT or Maven or scripts) witch i can use after in workshop.
I want to create one 'template' of all 40 projects in the same time, with the same directory structure (Transforlation, Business services, proxy services, WSDL .....) and all 40 project have the same transport, just the names of projects and services witch changes and i can give to the script all names of projects and services and i can give also all WSDL.
Regards,
Tarik

SWT Error occured in OSB project

When I import OSB project in workshop and tried to see params in stage "service callout" a get "SWT Error occured" [img src=http://f3.s.qip.ru/56TNXCPS.jpg] and can't see params. If to create in workshop new service callout - everything is ok.
Any idea?
Edited by: 936743 on 25.05.2012 6:19

Record about this error in log file
!SESSION 2012-05-25 17:15:24.272 -----------------------------------------------
eclipse.buildId=M20080221-1800
java.version=1.6.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ru_RU
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY com.bea.workshop.product 1 1 2012-05-25 17:15:40.709
!MESSAGE Using product plugin (com.bea.workshop.product) for feedback reports
!ENTRY org.eclipse.ui 4 0 2012-05-25 17:17:15.123
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTError: No more handles
     at org.eclipse.swt.SWT.error(SWT.java:3589)
     at org.eclipse.swt.SWT.error(SWT.java:3481)
     at org.eclipse.swt.SWT.error(SWT.java:3452)
     at org.eclipse.swt.widgets.Widget.error(Widget.java:432)
     at org.eclipse.swt.widgets.Control.createHandle(Control.java:602)
     at org.eclipse.swt.widgets.Composite.createHandle(Composite.java:235)
     at org.eclipse.swt.widgets.Decorations.createHandle(Decorations.java:413)
     at org.eclipse.swt.widgets.Shell.createHandle(Shell.java:522)
     at org.eclipse.swt.widgets.Control.createWidget(Control.java:618)
     at org.eclipse.swt.widgets.Scrollable.createWidget(Scrollable.java:131)
     at org.eclipse.swt.widgets.Decorations.createWidget(Decorations.java:421)
     at org.eclipse.swt.widgets.Shell.<init>(Shell.java:286)
     at org.eclipse.swt.widgets.Shell.<init>(Shell.java:265)
     at org.eclipse.swt.widgets.Shell.<init>(Shell.java:218)
     at org.eclipse.swt.widgets.Shell.<init>(Shell.java:156)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.getTextDimension(TabbedPropertyList.java:709)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.getTabHeight(TabbedPropertyList.java:826)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.computeTabsThatFitInComposite(TabbedPropertyList.java:535)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.computeTopAndBottomTab(TabbedPropertyList.java:863)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.access$25(TabbedPropertyList.java:862)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList$10.controlResized(TabbedPropertyList.java:504)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:221)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
     at org.eclipse.swt.widgets.Control.WM_SIZE(Control.java:4302)
     at org.eclipse.swt.widgets.Scrollable.WM_SIZE(Scrollable.java:333)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1360)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2568)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:356)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:284)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1025)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1371)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4374)
     at org.eclipse.swt.internal.win32.OS.EndDeferWindowPos(Native Method)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:729)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:695)
     at org.eclipse.swt.widgets.Composite.setResizeChildren(Composite.java:901)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1026)
     at org.eclipse.swt.widgets.Composite.layout(Composite.java:551)
     at org.eclipse.swt.widgets.Composite.layout(Composite.java:509)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.layoutTabs(TabbedPropertyList.java:980)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.computeTopAndBottomTab(TabbedPropertyList.java:897)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList.access$25(TabbedPropertyList.java:862)
     at org.eclipse.ui.internal.views.properties.tabbed.view.TabbedPropertyList$10.controlResized(TabbedPropertyList.java:504)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:221)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
     at org.eclipse.swt.widgets.Control.WM_SIZE(Control.java:4302)
     at org.eclipse.swt.widgets.Scrollable.WM_SIZE(Scrollable.java:333)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1360)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2568)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:356)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:284)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1025)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1371)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4374)
     at org.eclipse.swt.internal.win32.OS.EndDeferWindowPos(Native Method)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:729)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:695)
     at org.eclipse.swt.widgets.Composite.setResizeChildren(Composite.java:901)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1375)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2568)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:356)
     at org.eclipse.swt.layout.FormLayout.layout(FormLayout.java:284)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1025)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1371)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.EndDeferWindowPos(Native Method)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:729)
     at org.eclipse.swt.widgets.Composite.resizeChildren(Composite.java:695)
     at org.eclipse.swt.widgets.Composite.setResizeChildren(Composite.java:901)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1375)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:198)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1025)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1371)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:198)
     at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1025)
     at org.eclipse.swt.widgets.Composite.WM_SIZE(Composite.java:1371)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3743)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260)
     at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4374)
     at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method)
     at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2499)
     at org.eclipse.swt.widgets.Control.setBounds(Control.java:2568)
     at org.eclipse.ui.internal.LayoutPart.setBounds(LayoutPart.java:300)
     at org.eclipse.ui.internal.presentations.PresentablePart.setBounds(PresentablePart.java:169)
     at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.layoutContent(PresentablePartFolder.java:129)
     at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.layout(PresentablePartFolder.java:410)
     at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.setBounds(PresentablePartFolder.java:258)
     at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.setBounds(TabbedStackPresentation.java:218)
     at org.eclipse.ui.internal.PartStack.setBounds(PartStack.java:1198)
     at org.eclipse.ui.internal.LayoutTree.doSetBounds(LayoutTree.java:547)
     at org.eclipse.ui.internal.LayoutTree.setBounds(LayoutTree.java:538)
     at org.eclipse.ui.internal.LayoutTreeNode.doSetBounds(LayoutTreeNode.java:535)
     at org.eclipse.ui.internal.LayoutTree.setBounds(LayoutTree.java:538)
     at org.eclipse.ui.internal.LayoutPartSash.widgetSelected(LayoutPartSash.java:276)
     at org.eclipse.ui.internal.LayoutPartSash.access$1(LayoutPartSash.java:259)
     at org.eclipse.ui.internal.LayoutPartSash$1.widgetSelected(LayoutPartSash.java:62)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:947)
     at org.eclipse.swt.widgets.Sash.WM_MOUSEMOVE(Sash.java:380)
     at org.eclipse.swt.widgets.Control.windowProc(Control.java:3716)
     at org.eclipse.swt.widgets.Display.windowProc(Display.java:4361)
     at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
     at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2265)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
     at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
     at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
     at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
     at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
     at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
     at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
     at org.eclipse.equinox.launcher.Main.eclipse_main(Main.java:1148)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.m7.installer.util.NitroxMain$1.run(NitroxMain.java:33)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

What do you mean by changing a Function Group in upgradation projects

Hi ABAPers,
I am new to upgradation project will any one help me in understanding the concepts like.
1) what do you mean by changing a Function Group in upgradation projects
2) what is the relation b/w the Maintenance view and function group
3) what happens when we regenerate the table maintenance in se11
4) how can i restore the changes that have done to FG after regenerating
5) Suggest me is there any Tcode or procedure to see the code in Remote system (like how we compare the versions of remote system)
Could you please help me ..
Any relevant docs you can send it to [email protected]
Thanks in advance..

Hello Smriti,
          Exploding a BOM means to display all the components and sub-components for a BOM in a particular transaction (eg) VA01,CO01,ME22N etc..
You can use the SAP FM's depend on the Functionality:
CS_BOM_EXPLOSION               General BOM explosion
CS_BOM_EXPLOSION_EQUI          BOM explosion - initial screen: equipment
CS_BOM_EXPLOSION_MAT           BOM explosion (old version); as of 3.0, use CS_BOM_EXPL_MAT_V2
CS_BOM_EXPL_EQU_V2             BOM explosion for equipment
CS_BOM_EXPL_KND_V1             BOM explosion for material
CS_BOM_EXPL_MAT_V2             BOM explosion for material
CS_BOM_EXPL_PSP_V1
CS_BOM_EXPL_TPL_V1             BOM explosion for functional location
CSS7                           Explode BOM (Document)
CS_BOM_EXPL_DOC_V1             BOM explosion: document sub-assemblies
CS_BOM_EXPL_GNRL2_V1           General BOM explosion: document sub-assemblies
CSSO
CS_SO_MODE_BOM_EXPLOSION
As per Garet in response to your question better talk to the Functional team to get the better underatanding for your requirement.
Check the below link for more details on BOM:
http://sap-img.com/sap-sd/what-is-bom-referring-to-sap-sd.htm
Thanks,
Greetson

How to define the OSB Configuration Project that an OSB Project uses?

Hello,
I'm using the Workshop bundled with "Oracle Service Bus 10gR1" (Oracle Workshop for WebLogic, Version: 10.3, Build id: 1137967).
Where does one define the OSB Configuration Project that an OSB Project should use?
I deleted an OSB Configuration Project. Now, all the OSB projects that were associated with it are in error stating "This project is not associated with an Oracle Service Bus Configuration". I created a new OSB configuration project so that I may re-associate the "orphan" projects with it. However, I can't seem to find a way to do that.

You can create a new osb configuration project and drag the other osb projects on this projects.
then i will link them to it. (make sure you use the oracle service bus perspective at the top right of the eclipse ide)

Unable to create OSB project in OEPE 11.1.1.6.1

Hi,
I have installed weblogic server 10.3.4 with OEPE 11.1.1.6.1 (wls1034_oepe111161_win32.exe) on Windows XP machine. There after I installed Oracle Service Bus 11.1.1.4.0 (ofm_osb_generic_11.1.1.4.0_disk1_1of1.zip). When I open OEPE I do not find the option to create a OSB project, I have tried to update and it says no updates available. Please let me know how to make it work?
Thanks
Avinash

Hello Avinash,
Make sure that you have chosen "Custom" installation type for OSB and installed "Oracle Service Bus IDE" as well. This will install the OSB plugins in existing OEPE installation. Please refer -
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15017/install_screens.htm#BABDFEEC
Regards,
Anuj

How to deploy osb projects into managed server in weblogic

i am new to osb
i have a doubt
i created a managed server in weblogic admin console, it was running fine ,but i need to know how to deploy my osb projects in that new manged server.As of now it is deployed in http://localhost:7001/sbconsole

I think you need to extend the domain instead of creating the managed instance manually through Admin console. By default when you create a domain using OSB domain template, it deploys all of the applications needed automatically to all the instances. If you are trying to do it manually, then you need to follow the documentation to see which applications need to be deployed to use OSB services.
http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBFGBFF
To deploy a project, Login to SB console http://<admin>:<port>/sbconsole > System Administration > Export/Import Resources.

OSB project deployment problem with MFL file

Hi,
I have created a OSB project to transform a xml message into a text file. For this I have created a mfl and the necessary proxy/business service. I can generate the sbconfig.jar from OEPE tool. But while trying to deploy the sbconfig.jar (generated from OEPE toll) in the OSB server the following error is coming:
<Sep 30, 2013 3:19:06 PM CEST> <Error> <ALSB Console> <BEA-494002> <Internal error occured in OSBConsole : com/bea/nonxml/util/NonXMLSchemaGenerator.genXsdFromMfl(Ljava/lang/String;Ljava/io/Reader;)Ljava/lang/String;
java.lang.Exception: com/bea/nonxml/util/NonXMLSchemaGenerator.genXsdFromMfl(Ljava/lang/String;Ljava/io/Reader;)Ljava/lang/String;
        at jsp_servlet._jsp._main.__errorpage._jspService(__errorpage.java:134)
        at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodError: com/bea/nonxml/util/NonXMLSchemaGenerator.genXsdFromMfl(Ljava/lang/String;Ljava/io/Reader;)Ljava/lang/String;
        at com.bea.wli.common.mfl.MflExecutor.create(MflExecutor.java:76)
        at com.bea.wli.sb.resources.mfl.MflExecutor.create(MflExecutor.java:72)
        at com.bea.wli.sb.resources.mfl.MflEntryHelper.validate(MflEntryHelper.java:90)
        at com.bea.wli.sb.resources.mfl.MflTypeDef.validate(MflTypeDef.java:54)
        at com.bea.wli.config.validation.ResourceValidator.validateContents(ResourceValidator.java:118)
        Truncated. see log file for complete stacktrace
>
[INFO ][alloc ][Mon Sep 30 15:19:11 2013][00464] [YC#33320] Pending requests
Can someone please help me out regarding this problem and let me know the reason.
I am using 11.1.1.5.0 version of OSB.
Please let me know if you need any further details.
Thanks.
Rahul

Hi Ahul,
     It may cause because of the following problem,
1) Make Sure that your MFL is working perfectly
2) Make sure that your OSB Server is Running with out any error..
Let me know still your facing the problem
Regards,
Kiran

Ehcache config in osb project

Hi All,
I'm working on osb 11.1.1.5 version.I have configured Ehcache 2.5.2 version and created java class in the eclipse environment.I created ehcache.xml file and placed it in my application class path,added all ehcache related jars.It is working fine.Now i have created jar file for my java classes and tried to calling this jar in my javacallout component of the proxy service of osb project.I created one folder,i placed all the related jar files into the folder.But im able to get all the classes except the class which consists of ehcache related code,and im also not able to run the proxy with the ehcache jars,if i removed the ehcache jar from my project i'm able to run the proxy service.otherwise it indicating the error
Error publishing project changes for: OSB Configuration 1 socket write error: Connection reset by peer.
I'm also tried with place all the ehcache jars in the domain lib folder.But i'm not able to get the ehcache related code java class in the javacallout of osb proxyservice.
Is there any separate configuration for ehcache in the osb?It is working in the eclipse environment as a java project,but when im trying to call the same java class jar file in the osb project it is not working.
please give me any suggestions....i'm new to osb...
Thanks in Advance!

If you want to call a Java class using Java Callout in Proxy, you need to create a Jar type resource in OSB and import the needed Jar file there. Only the Jar files which are imported this way will be available for Java Callout. Also, any other libraries which your main jar is dependent on should be in the server classpath.

How to publish OSB project to other managed servers?

How to publish OSB project to other managed servers
Edited by: 991757 on 2013-3-4 下午6:09

Not required to be published.

Security Groups when in 'Project Server Permissions Mode' - Project Online

Hi All,
We have Project Online up and running, by default the PWA instance we added to O365 was in "SharePoint Permissions" Mode, we changed to "Project Server Permissions" Mode because of some complex security we need to configure. For some
reason (different from Project Server 2013) Project Online creates a number of Security Groups by default that seem to be duplicates. For example for Administrators there are:
- Administrators
- Administrators for Project Web App
- Web Administrators (Project Web App Synchronized)
For Project Managers:
- Project Managers
- Project Managers (Project Web App Synchronized)
- Project Managers for Project Web App
And there is something similar for all the groups (compared to Project Server 2013):
I have looked online, with no luck, for some guidance on what all these groups are and if I can delete some of them without causing PWA to crash.
If anyone out there can point me in the right direction / send me some documentation or links it will be greatly appreciated!
Thanks!
Jorge

Hi Jorge, I had the same thing on two different tenants within the last week - one today. I will just clean up the SharePoint groups manually. The ones with the descriptions are the correct Project Server permission mode groups... Hopefully Microsoft will
fix this soon, you could raise a support ticket on your office 365 tenant - support is pretty quick! Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Referencing Classpath's Jars form OSB Projects

Hi all,
We have found a behavior we cannot understand in the OSB. As we have assumed in the [Best Practices|http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/pojo.html] , if we are going to use a Jar inside an OSB project, we better use a small jar with the static methods and proxy the logic to the libraries placed in the classpath.
Assume a project ProjectA with a library proxyLib.jar which references libA.jar and libB.jar placed in the server's lib folder.
To use libA and libB from the proxyLib we have to first add them into the classpath, thus we assumed it is done editing the "Class Path" field placed in the "Server Start" tab from the WebLogic Server Console, but we wondered why it didn't work because when importing the project, a classnotfound error appeared for the project's library (proxyLib) which references the external libraries.
We solved it editing manually the setDomainEnv.sh file, but we don't understand why it doesn't worked using the console.
Our system is composed by one AdminServer and one Cluster with 2 Managed servers. The classpath modified by the console referenced the absolute path /...../domains/mydomain/lib/libA.jar and the setDomainEnv file edited is also placed in the ..mydomain/bin folder.
Does anyone know the reason?
Thank you in advance and best regards,
rromero

First of all, thanks for your answers.
Anuj Dwivedi wrote:
If you want to add a jar in server classpath then place it in directory $Domian_Home/lib and just restart the servers. Open the readme file inside same directory and you will find -
The jars located in this directory will be picked up and added dynamically to the end of the server classpath at server startup. The jars will be ordered lexically in the classpath. The domain library directory is one mechanism that can be used for adding application libraries to the server classpath.
It is possible to override the $DOMAIN_DIR/lib directory using the -Dweblogic.ext.dirs system property during startup. This property specifies a list of directories to pick up jars from and dynamically append to the end of the server classpath using java.io.File.pathSeparator as the delimiter between path entries.This is the most preffered way to add a jar in server classpath.
Regards,
AnujAs I said, at first instance, the libraries where already in the lib folder and didn't take any effect until I added manually to the setDomainEnv
atheek1 wrote:
Server Start" tab from the WebLogic Server Console,Whatever you configure in server start takes effect only if you use node manager to start that server . If you are not using node manager these settings wont have any impact.
I also beg to differ with Anuj on putting jars in domain/lib, for some reasons i find in certain cases osb doesn't recognize these jars in domain/lib (both for java callouts and when using 3rd party jms providers ), so to be safe its better to put it explicitly in classpath,
This thread discussed one strange problem with putting jars on domain/lib.
http://forums.oracle.com/forums/thread.jspa?messageID=9173629&#9173629
We are using nodemanagers with the managed servers, so that's why I expected the problem to be solved using the "Server Start" tab.
Regards,
rromero

Deployment process for Large ALSB/OSB project

Hi,
I am searching for some details or article about deployment of alsb/osb projects (number of projects) as part of build process.
How projects manages when number of different alsb projects need to be build, customized and imported into different environments.
We are starting new release where developers would be working on different projects. i have a some ANT scripts which use WLST script to export single project, created jar file and place them into a specific location.
For import, the script looks at a specific location, reads config.jar from that location, and imports that config into target environment. Now with multiple projects and each developer will deliver their own config.jar. How to handle that in WLST. I am not sure if the current approach i am using that any good to handle multiple projects deployment.
Anyone could give some pointers or helpful hints?
we are on version 10.0 and wont be moving to 10gR3 where we could use ANt to build config.jar from .metadata so not sure.
I want to know what other projects are doing etc!
many thanks in advance!
sal

It seems you already have certain level of insight into deployment process, but maybe you will find this document interesting:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/pdf/deploybestprac.pdf

OSB Project Import Problem

Hello All,
I want to import an OSB project into one OSB domain.
There are some other projects already there.
But after importing, it requires me to restart the server, which it is the OSB configuration project problem.
The new project is in another configuration project, which is different from the one for those deployed projects in the server. I don't know the name of the configuration project in the server. What I should do to avoid to restart the server?
Thanks and regards,
Kerr

Hi,
OSB Resources can be imported and exported with eclipse IDE or sbconsole.
Until the project names are unique user should be able to import without any issues.
Not sure of your use case ... but user dont need a re-start at all with new resources it will workwell
thanks

OSB Project redeployment, Proxy endpoint uri not changed

Hi,
We have a problem when redeploying a OSB project with a new proxy Endpoint URI. When we deploy the changed project, through the OSB console Administration->Import, the OSB deployes successfully but still works with the old EndPoint URI ?
On the disk at <domain_home>/osb/config/core/<project>/PollXYZ.proxy.xml we can see that the old EndPoint URI is still present even though all files have a new modified date. When we try change another property, like "all-headers" the changes are reflected sucessfully when redeployed. So it is only the EndPoint URI that is somehow not changeable?
Any ideas?
TIA

No. url is changeable and it works perfectly fine for us. Are you sure the jar which you are deploying has the latest url for sure.
P.S: Post OSB related queries in SOA Suite forum:
SOA Suite

Grouping of OSB projects

Similar Messages

Maybe you are looking for