This content has been marked as final. Show 10 replies
As far as I know there is ant support in osb 10.3.1.0, so you can build your sbconfig.jar without workshop.1 person found this helpful
Support for generating config.jar from command line or ant task
we had/have same problem but only work around we have with current version i.e. 10.0 is to export config project from a development server.
10gR3 appears to have the solution by creating config jar from .metadata folder. Now i wonder if this creative idea is going to help real problems, as in most projects more there are typically more then one develer, so how to merge or which .metadata folder to put in the repository to create config jar? some one should correct me here???
I am not sure if thats any helpful but surely help you decide which approach you will follow. I would be more than happy to hear what approach you picked up for this issue as we have similar environment here.
From the documentation as was pointed out to me (RTFM :-) you can actually build a sbconfig.jar file based on a Configuration Project. So I agree with you on a new challenge, "how to organize your Configuration Projects for automatic building". We will be looking into that as and any suggestions from more experienced people are welcome.
Looking at some statements concerning Configuration Projects (Copyright: Jeff Davies et al. )
An OSB Configuration Project is also used to create and contain resources for SMTP, UDDI, and so on that can be accessed by all projects in the configuration project. It represents the configuration information associated with an OSB Domain (a group of servers, all similarly configured and providing identical functionality). It is also an umbrella project that will contain all of the other OSB projects you wish to deploy onto a specific OSB Domain.
So depending on the number of OSB Domains you have you can have multiple Configuration Projects. You mentioned something about different workspaces for different developers perhaps getting you into trouble. I think I am going to use the following approach. For my deployments I will be needing Configuration Projects. So at least these are going to be created and checkin. Of course my OSB projects will be checked in. For the developers they can create their own local Configuration Projects as long as they are not checked in. Everybody is developing locally.
I hope I can have more than one Configuration Project per Domain. When I do a sequential export of multiple sbconfig.jar files from different configuration projects I hope every new export does not completely erase the former one. So they are added and only resources are overwritten which are identical.
Perhaps there are some best pratices on how to do this in a controlled way
thanks for sharing you experience!
We fully automated the nightly build and deployment, and it's possible using the ant script you've mentioned.
Currently I'm checking out the OSB projects from subversion, and building the sbconfig.jar using ant, which uses workshop in the background.
Regarding the OSBConfiguration file, I'm generating it on the fly, as you said you might want to have different projects being imported and sorting out dependencies across different phases of your project.
Once you export the project, you might have issues with the System project, as the Export file will add some entries with "deletes", so make sure that you don't import the System project to OSB, OR apply a patch (released last month by Oracle) to fix the issue.
There is another patch to enable you to export subprojects. So let's say you have 10 projects in your repository, you might want to group specific projects per JAR. I was planning initially to export one JAR per project, so it would be easier to distribute the JARs and deploy them in the production environment, however each time you invoke ANT it starts Workshop in the background and it takes a long time. So I decided to group the projects in 4 jars only.
Regarding the JCA DB Adapter, currently it's not possible to export a project which uses the JCA DB Adapter due to a bug in the ConfigExport. I already raised this issue with Oracle about 4 months ago, but didn't get the patch yet. If you raise this issue with the support it might help us to get a patch sooner.
Edited by: email@example.com on Mar 17, 2010 6:26 PM
I am have same problem,we are the team working on one project...and everybody checkin their final copy to svn..
Now i want to checkout the proxy service ,business services ....n all and deploy on a single server.
Do anyone have the script to do this?
I have no idea how will i create sbconfig.jar just from the artiifacts...
I also automated the OSB export with ant scripts. I works when i run the ant scripts in my OSB workshop.
But when you want the build to be automated with Continuous Integration, I would have to install the full OSB workshop on my build environment?
That is not exaclty what I want. I would expect from Oracle that they provide a fully self-contained ant-task which could be used on the build envrionment.
How have you solved this problem?
Oracle supplies ant scripts for the export/creation of the sbconfig.jar from a running osb server or from a eclipse workspace project.
both work well and will create the sbconfig.jar for you
for the export from the eclipse workspace you indeed need some eclipse jars to do the export.
currently we use scripts to do the svn checkout and export the jar from these resource and deploy it to a server, works ok
We are in a Similar situation in our project. Can you send me the ABT Script which you are using? I can take it as a reference and Build my own.
Thanks for your help.
WLST scripts to import/export and customize OSB configuration jar
with those scripts you should be able to do your thing,we used them too in our framework