Anybody using jikes in production environment?

anybody using jikes in production environment?
thanks,
-ramu

"Joe Herbers" <[email protected]> wrote in message
news:3aa69c84$[email protected]..
We were going to use jikes when we switched to 1.3, but had a few problems
with it. It compiles much faster than Sun's JDK, but it would
occasionally crash. We could recompile the stuff that crashed andproceed,
but that concerned us (I don't recall if there was anything else). So we
bought the latest version of VisualCafe (Professional and Enterprise
Editions have a fast 1.3 compiler) since we had used their 1.1 compiler in
production in the past.We've been using Jikes for months now without any serious problems. I've
never known it to crash. (Jikes 1.12, JDK 1.3, Redhat Linux 6.2, WL 5.1) The
caveat I could offer you is that Jikes is much more willing to generate
warning messages than javac. In particular, I've noticed that it will throw
annoying messages on Weblogic's ejbc-generated code unless you specifically
suppress warnings.
-- Brendan Smith
-- periopcare.com

Similar Messages

  • Should Plugins Be Used In A Production Environment?

    Hello All.
    I am seeking your opinion on an issue that recently was raised in my work environment.
    We are heavy users of Apex 4.x. I recently introduced Apex plugins to several of my fellow developers. They all were astounded.
    However, someone questioned if we should incorporate a plugin into our production apps. The concern here is that, despite their usefulness, plugins are not officially supported by Oracle. If we run into an issue with a plugin, our only support would come from the person who authored the plugin. I would not be able to call Oracle/Apex Tech support to ask my question. And so, if the plugin author, for some reason, was not available, the problem would not be addessed. Furthermore, because the plugin code is not available to me (at least I think so; please correct me if I'm wrong), I would be forced to either remove the plugin from my app or come up with custom code to do what the plugin is doing.
    Another concern is would the plugin code "survive" an Apex upgrade. I would hate to upgrade, say, from 4.0.2 to 4.1 and find that my previously installed plugins had disappeared. Frankly, I'm not sure this is a realistic concern, still I'm mentioning it because I don't have a sure answer.
    Of the two concerns, the former is the biggest. In a "play/test" environment, not having the author answer or correct an issue with their plugin is frustrating but not critical. But in a production setup, this would be a big problem.
    These concerns are giving my management pause as to whether or not to incorporate plugins into our production Apex apps.
    It's my understanding that several of the popular open source software tools (Linux, perl, mySQL, JQuery, etc.) each have a core team of people who "maintain" the tool. There's a psuedo company giving oversite to the code. And so, such tools sort of have a critical mass of people supporting the tool. On the other hand, an Apex plugin has just one person (the author) maintaining the code. And that sole supporter may, for whatever reason, stop supporting it, making production support dicey.
    I would appreciate your opinions about this?
    Thank you.
    Elie

    Hi,
    That concern is not limited to plugins only. Install any third party library, and run into an issue the support you receive is by the author of said library, and not by oracle themselves - as they didnt author it! In the end, you need to assess, should something go wrong, can you either get the support you require, or have the ability to fix the code your self.
    The plugin code is available, in shared components -> plugins -> you can normally see how a particular plugin works. However, this is not always the case - some authors want to keep their code hidden well (probably if they have released the plug in under a commercial license), so wrap their code.
    Anyway, if you're still worried- just code it yourself? In the end, you should be thoroughly testing your apps to ensure their will be as little issue as possible. If you test it well, you reduce the risk down the line of anything going wrong. If the tests fail, don't use the plugin and look at another solution. Plugins are not limited to those released open source. For instance, your organisation may have a common functionality in all your apps, so then you can create a plugin for your dev's to use. By documenting the plugin well, down the track if there are issues, you should be able to fix it.
    And so, such tools sort of have a critical massI like to think APEX has a large population - that is every growing - helping out too. Look at this forum, their are people helping out every day.
    Another concern is would the plugin code "survive" an Apex upgrade. I would hate to upgrade, say, from 4.0.2 to 4.1 and find that my previously installed plugins had disappeared.Of course, I'm not an Oracle employee, so can't speak for there future. But i'd be quite surprised if they didn't make the upgrade path for plugins as seamless as possible, in the event they had some core changes.
    Just some of my thoughts.
    Ta,
    Trent
    Edited by: trent on Apr 14, 2011 11:07 AM
    Also, Martin made some posts on his blog about some other concerns of plugins. Perhaps you'd like to have a read of them too:
    http://www.talkapex.com/2011/04/malicious-code-in-apex-plugins.html
    http://www.talkapex.com/2011/04/malicious-code-in-apex-plugins-feedback.html

  • Order combination(mill product) to be used in normal production environment

    Hello All,
    Can you please tell me whether we use can use order combination fuction from Mill products in normal manufacturing environment. if so can any one tell me what are the seeting we have to do. When i am trying to do it is giving me a error on the controlling side. Any help will be much appreciated.

    Jags,
    If you are talking about capacity calculation while creating/releasing the production order, then that can be stopped through Config settings for the checking control (OPJK). In this tick the "No Avail check" under Capacity availability section for 1 and 2 business function.
    Try this and revert back.
    Swapnil

  • Use in production environment

    Hello,
    My company is extremely restrictive in terms of tools permitted for use in the production environment and have recently requested that support staff discontinue using SQL Developer.
    Are there any recorded incidents of data loss, corruption or database performance and stability problems caused by SQL Developer?
    Thanks,
    Tony

    No, but I suspect that won't convince anyone.
    These things can rarely be argued on logical grounds, but what reasons have they given, or what criteria do they use to decide what is allowed?
    Production environments should be protected using appropriate database privileges and resource management profiles.

  • FAQ: Can I use the Photoshop CS6 beta in my production environment?

    Although some may find the Photoshop CS6 beta quality good enough to use in a production environment, the nature of beta software is that it is not production quality, so not everything may work as expected. Customers should be aware that Adobe will not offer any technical support for the Photoshop CS6 beta.

    Please quit/close Lightroom 4, and any other Adobe software on your system, prior to installing the Photoshop CS6 Extended Beta:
    If you encounter the dialog (below) that references the background process named 'dynamiclinkmanager' during installation, please quit Lightroom 4, and any other Adobe software on your system. Then click [Continue] to continue the installation of Adobe Photoshop CS6:

  • MSDN and Production Environment (again)

    I started this on another forum before I found this one, but this seems a more suitable place.
    The definition of "production environment" seems rather odd. In some responses on this forum it appears to refer to "soft" systems whereas the latest MSDN licence refers to environment and physical kit.
    Below is a conversation I had over email with someone from MSDN and I find the whole thing utterly bizarre. I cannot for the life of me see how this helps anyone apart from MS being able to charge for non-production software. It renders having a powerful desktop
    for local lab experimentation pointless as you're not allowed to install anything and effectively doubles the hardware cost to small companies if they have to buy a separate server for any testing work (yes, best practice and all that, but budgets...) or pay
    out for a Windows Datacenter licence.
    Question:
    “If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs hosted on that physical
    system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately.”
    Is this actually saying that if I have a physical server licenced with a purchased (not MSDN) Server 2012 R2, running Hyper-V with, say, a production file server VM on it,  that ALL Windows VMs on that machine must have purchased licences even if they
    are only for development & testing purposes?
    Is this saying that all production and development Windows VMs must be only completely separate hardware, cluster, SAN, etc otherwise you must pay for full licences for the VMs?
    Or does it just mean that the bare metal licence (plus any additional ones required for running further production VMs) must be purchased if the VMs are a mix of production and development?
    Answer:
    We kindly inform that any products licensed under the developer tools model (e.g. SQL/BizTalk developer and/or MSDN) must be installed on their own separate physical hardware.
    You are not allowed to run test or development products on a server where production workloads are running at the same time.  Kindly run your developer software on a device/host that is dedicated to testing and development.
    Explanation:
    The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
    dedicated hardware and software to provide "live" service.  If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
    it says environment.
    See current PUR, page  51:
    Developer Tools (User License)
    You have the rights below for each license you acquire.
    #      You must assign each license to a single user.
    #      Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
    #      The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
    #      The software is not licensed for use in a production environment. #      Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict
    with these product use rights, except for superseding use terms outlined below.
    Question:
    Classifying an entire physical infrastructure as "production" in these days of virtualisation and shared storage really does not make any sense at all. Not using the software for production purposes makes perfect sense, but not being able to locate
    it alongside production OS installs is mad. Does this only apply to the server running the VM (CPU and RAM)? If the VHDX is hosted on shared SAN storage does the SAN have to be dedicated to non-production storage?
    Answer:
    We kindly inform that after double-checking the case we would like to confirm the development software cannot be run on the same hardware with production software.
    We have also received a feedback from the responsible team regarding your request about a dedicated SAN (Storage Area Network) for MSDN software.
    They have confirmed that the SAN has to be dedicated to the development and testing environment if it is used to run the software acquired through MSDN.
    Question:
    OK, so if I have my desktop (which is a production environment as I use it for email and other day to day office tasks), can I turn on Hyper-V and install an MSDN Windows Server 2012 instance for development purposes?
    Answer:
    We kindly inform it is not allowed to install and run software from MSDN subscriptions in production environments. Please do not install MSDN software on a desktop in a production environment:
    "[.] The customer will need to run the developer software on a device/host that is dedicated to testing and development.
    Explanation:
    The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
    dedicated hardware and software to provide "live" service.  If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
    it says environment.
    See current PUR, page  51:
    Developer Tools (User License)
    You have the rights below for each license you acquire.
    -      You must assign each license to a single user.
    -      Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
    -      The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
    -  The software is not licensed for use in a production environment.
    -      Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict with these product use rights, except for superseding use terms outlined below.

    Hi Mike,
    It sucks that MSDN software can't be run in a production environment, that means you have to have two entirely separate hardware environments, which are costly, and it seems unnecessary.  
    That's essentially it. I'm not saying for one second that it should be used for production purposes, just that it's physical location shouldn't be relevant. Also, the word "environment" is a very bad choice in the documentation simply because it's very open
    to interpretation.
    A production environment is defined as an environment that is accessed by end users of an application (such as an Internet Web site) and that is used for more than
    Acceptance Testing of that application
    or Feedback. Some scenarios that constitute production
    environments include:
    Environments that connect to a production database.
    Environments that support disaster-recovery or backup for a production environment.
    Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity.
    So I dont think (here's that inconclusive language) but am not sure that your desktop machines count as production environments, based on that, unless end users are connecting to them. (I dearly hope they are not!)
    My reading is based on the "Other Guidance" section:
    "If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs
    hosted on that physical system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately."
    <o:p>This is the crux of the matter and the interpretation of "licensed separately". A (to my mind) sensible reading of that would be "if you're running any production purpose VMs on a server then the physical host OS must be a full licence
    [presuming it's Server 2012 and not, say, VMWare or Hyper-V 2012] as must all production purpose VMs on that server". This has been getting interpreted by others (I'm not the first) and backed up by MS as meaning that if you want to run any dev/test VMs on
    a server that also runs production VMs then you can't use MSDN for those dev/test VMs.</o:p>
    Also, there is a section
    here, on the MSDN Licensing help page that says (with my added emphasis):
    Many
    MSDN subscribers use a computer for mixed use—both design, development, testing, and demonstration of your programs (the use allowed under the MSDN subscription license) and some other use.  Using the software in any other way, such as for doing email,
    playing games, or editing a document is another use and is not covered by the MSDN subscription license. 
    When this happens, the underlying operating system must also be licensed normally by purchasing a regular copy of Windows such as the one that came with a new OEM PC.
    Now to me, it seems this might be saying that the underlying operating system on a work
    machine cannot be licensed using MSDN if that work machine is going to be doing non-msdn things in addition to MSDN things.  It doesn't say "This can't happen" it just says "When this happens, the underlying
    OS must be licensed normally..." 
    So, based on what I'm reading it seems that this quote from you might not be true:
    "We can't install a local MSDN instance of Server 2012 or 8.1 for dev and test under Hyper-V on desktops
    because desktops used for email, writing documents, etc are production. "
    I wouldn't have expected this to be true either, but this is the response I was given. It may well be
    that my question was misunderstood. I hope this is the case otherwise one of the big reasons for turning on Hyper-V on  expensive, powerful desktops enabling the running of personal test environments goes out the window!
    Thanks for your time on this.

  • XE in production environment

    Hi all,
    I wanna ask who is using XE in production environment. I'm especially interested in following info:
    - application type and sector
    - commercial/non-commercial application
    - time from release
    - # of users, typical # of concurrent users
    - client-side technology
    - server OS and hardware configuration
    - significant experience with (in)stability and performance, maintenance troubles
    Many thanks

    hawkeye wrote:
    Hi all,
    I wanna ask who is using XE in production environment. I'm especially interested in following info:Note that by it's very nature (SGA/PGA limits), XE is not designed to handle very many concurrent users. I'd guess that 6-20 concurrent users would be a practical limit, depending on the workload type. ApEX workload, using Shared Servers, could go slightly higher, at the risk of user waits.
    I've used it in production for a year and been quite happy against a simple internal (not Internet) APEX 'Billing / Invoicing' app.
    Interestingly, OracleVM uses XE by default as the default production repository for OracleVM Management. And Oracle uses XE as the default repository for SOA Suite installs (with recommendations to upgrade for HA.)

  • How to use connection pools in production environment

    Hai
    We are using Statless Session beans which will call bean managed entity beans
    as a developer we completed the first phase of our project successful but when
    comming to the production environment they(Higher authoritites of the company)
    are asking abt the connection pools. Suppose if my wlserver5.1 has 100 hits per
    a second how many connection pools i need to put in the production envirornment
    and also is it the right way to increase the connectionpools depends upon the
    clients hits????. Can anybody help me regarding this It is very urgent for us.
    Cheers Kiran Nallam

    Hi Aravind,
    It can be used only for calculation kinda "minimum size".
    Nothing can prevent a developer from writing something
    like this:
    Connection con1 = ds.getConnection();
    Connection con2 = ds.getConnection();
    Connection con3 = ds.getConnection();
    Regards,
    Slava Imeshev
    "Aravind Krishnasamy" <[email protected]> wrote in message news:3bfa85f6
    You can fix the size of the weblogic connection pool depending on yourexecute
    thread count value. For example the default value of execute thread countvalue
    is 15. So at a given point of time you cannot use more then 15 databaseconnection.
    Database connection pool size should be equal to or less then the size ofexecute
    thread count
    "Slava Imeshev" <[email protected]> wrote:
    Hi Kiran,
    It's hard to provide exact dependence between number of hits
    and actual number of consumed connections because it's a highly
    variable distributed environment. But the general approach is
    simple - before rolling out your application, make sure you
    tested it under simulated peak load. Your connection pool should
    have enough connections to serve peak load. Without such a testing
    you will never know whether your app scales or not.
    Regards,
    Slava Imeshev
    "Kiran" <[email protected]> wrote in message
    news:3bf9d676$[email protected]..
    Hai
    We are using Statless Session beans which will call bean managed entitybeans
    as a developer we completed the first phase of our project successfulbut
    when
    comming to the production environment they(Higher authoritites of thecompany)
    are asking abt the connection pools. Suppose if my wlserver5.1 has100
    hits per
    a second how many connection pools i need to put in the productionenvirornment
    and also is it the right way to increase the connectionpools dependsupon
    the
    clients hits????. Can anybody help me regarding this It is very urgentfor
    us.
    Cheers Kiran Nallam

  • Use of Emigall for creation of masters in the production environment

    Hi,
    The EMIGALL objects are normally used for migrating legacy master data and/or cut-over data before production environment is up.
    I am contemplating to use EMIGALL object for creation of contract account masters in production environment. One more option that I have is to use standard BAPI for creating contract account masters.
    Can anyone tell me whether it is proper to use EMIGALL object for day to day creation of master day in production environment. Is there any disadvantage or risk involved in it.
    Kindly reply soon.
    Regards,
    Ganesh

    I've already used emigall multiple times to do delta migrations into an operational prod environment.
    Purely looking at the functionalities, it should/would/must be possible to use emigall as a master data generator. I just think you need to look into the requirements:
    who will use it? end-user/application manager/...
    what's the amount of data to be loaded?
    what's the time window of the load? Day/night
    how is the data supplied?
    As you know, emigall EATS system resources like mad, so using it during the day might not be preferable. emigall is also very picky about the file format, whereas in a custom report you can define the input structure yourself.
    On the other hand, the error handling and follow-up of emigall is great...
    Personally, I'd go for a custom report with a BAPI... It'll give you more flexibility than emigall.

  • Suggestion for Iridium I/O third party tool use in production environment. Is Good or bad to use?

    Hello Everyone,
    we are planing to use Iridium I/O third party tool in one of our critical production environment to improve the performance.
     but i want to know is it recommended  for such type of critical servers?.
    if i use this tool find any performance improvement.

    Hi Baraiya,
    Iridium I/O is certified by Microsoft. It can help to fix SQL Server performance instead of just pointing out performance problems . Benefits of using Iridium include the following aspects. Refer to:
    Iridium I/O for SQL Server.
    •Faster transactions
    •Faster batch jobs
    •Reduced blocking and deadlocking
    •Faster sorting in tempdb
    •Speeds up queries from 3rd Party apps that can't be tuned
    •Speeds up queries that are already "fully tuned"
    •Speeds up the 95% of queries that the DBA never has time to tune
    In addition, there will be no impact on the SQL databases when Iridium is removed. Personally, I recommend you install the Iridium I/O in a test environment, and check if it meets your requirement, then use it in the production server.
    For more details , you can also review this blog:
    SQL SERVER – Iridium I/O – SQL Server Deduplication that Shrinks Databases and Improves Performance.
    Thanks,
    Lydia Zhang

  • Anyone using the Unified Inbox in a Production Environment yet?

    Hi,
    I am currently assessing the different SAP Workflow Inbox options, with the Unified Inbox being the first choice.
    With it being so new, it still seems to be a bit of a "Work in progress" from SAP's side.
    With the BSP application (/IWPGW/TGW_UNIF_INBOX) and Gateway service (/IWPGW/TASKPROCESSING version 2) still evolving in the latest Support Packs and the UI5 Inbox API still being expanded with each release.
    Not to mention the fact that the Inbox API has a very clear warning "Experimental API:Since version 1.5.2. API is not yet finished and might change completely" in the API Reference Documentation.
    Just wondering if there are any SAP customers out there who are using it in a Production Environment yet?
    If so I would really love to get some feedback regarding the following points:
    Performance
    Stability
    Functionality
    Or any other feedback will be appreciated.
    Thanks,
    Brad

    Thanks Jocelyn, looking forward to that webex session.
    We waited patiently to upgrade to IW_PGW SP06 which contains all the improvements and latest functionality you are referring to. As it had a dependency on SAP_GWFND SP08 which was released only 2 months (Mid September) after. Where as it was available for Gateway add-on IWFND SP09 in July.
    It really does contain massive improvements to the Unified Inbox with the extra features you're referring to. The /IWPGW/TASKPROCESSING version 2 Gateway service is way more complete now and the /IWPGW/TGW_UNIF_INBOX Unified Inbox BSP has been completely re-written using UI5 Components approach which has proven extremely useful in our case in order to enhance the Inbox by re-using the Unified Inbox component and not needing to modify anything SAP standard.
    I'm really impressed with it so far! I'm a big fan!
    Cheers,
    Brad

  • Best practice for a deplomyent (EAR containing WAR/EJB) in a productive environment

    Hi there,
    I'm looking for some hints regarding to the best practice deployment in a productive
    environment (currently we are not using a WLS-cluster);
    We are using ANT for buildung, packaging and (dynamic) deployment (via weblogic.Deployer)
    on the development environment and this works fine (in the meantime);
    For my point of view, I would like to prefere this kind of Deploment not only
    for the development, also for the productive system.
    But I found some hints in some books, and this guys prefere the static deployment
    for the p-system.
    My question now:
    Could anybody provide me with some links to some whitepapers regarding best practice
    for a deployment into a p-system ??
    What is your experiance with the new two-phase-deploment coming up with WLS 7.0
    Is it really a good idea to use the static deployment (what is the advantage of
    this kind of deployment ???
    THX in advanced
    -Martin

    Hi Siva,
    What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
    From my basis experience some of the best practices.
    1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
    2) It should have backup configured for which restore has been already tested
    3) It should have all the monitoring setup viz application, OS and DB
    4) Productive client should not be modifiable
    5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
    6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
    7) Relevant Database and OS security parameters should be tested before golive and enabled
    8) Pre-Golive , Post Golive should have been performed on Production system
    9) EWA should be configured atleast for Production system
    10) Production system availability using DR should have been tested
    Hope this helps.
    Regards,
    Deepak Kori

  • VB6 applications crashes when calling C# dll's in production environment

    Hi All,
    I'm basically .NET developer, not much aware of VB language or VB visual Basic 6.0.
    We are trying to work out with VB application running/ using C# dll's. The scenario is like VB exe applications using C# dll's and C# dll's are referenced to VB application using .tlb file.
    In development environment(debug mode) the application looks fine and working as expected. But when the same code is put into production environment VB applications are crashing when pointing to C# method calls. We trying to know the reason but application
    is getting killed. The issue seems to be sporadic and not able to catch in MsgView(debug tool).
    In one more scenario, the VB application is loading C# form and getting data back to VB but when we repeat the same workflow again application is crashing either in 2nd attempt or 3rd attempt.
    Has anybody seen such issue? Any input is welcomed.
    Thanks,
    Shesh

    Hi Shesh.ugare
    Welcome to MSDN.
    I am afraid that these forums donot support VB6, you could refer to this thread:
    Where to post your VB 6 questions
    If this issue regarding VB6 then you could consider posting this issue in these forums below:
    These forums do not support Visual Basic 6, however there are many third-party support sites that do. If you have a VB6-related question please visit these popular forums:
    VB Forums
    VB City
    If not, then you could share more detailed code with us.
    Thanks for your understanding.
    Regards.
    Youjun Tang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to manage connections in production environment

    Hai
    We are using Statless Session beans which will call bean managed entity beans
    as a developer we completed the first phase of our project successful but when
    comming to the production environment they(Higher authoritites of the company)
    are asking abt the connection pools. Suppose if my wlserver5.1 has 100 hits per
    a second how many connection pools i need to put in the production envirornment
    and also is it the right way to increase the connectionpools depends upon the
    clients hits????. Can anybody help me regarding this It is very urgent for us.
    Thanks in advance
    Cheers Kiran Nallam

    Hi,
    It all depends on your infrastructure and what products you are using.
    In most cases dev/prod are on different servers and are separate installs, this is the route I would promote.
    Some clients do share an environment for dev/test but not all, not everybody is the same.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • OWB 10g R1 : Installation required in Production Environment?

    Hi All,
    We are using OWB 10g Release 1.
    We are planning to create a production environment, where we will only deploy the code generated by OWB. But, the mappings(packages) that are generated using OWB , use some audit tables. So , we are wondering if we have to install OWB in production environment also.
    Anybody who is having idea abt this , please reply
    Thanks in Advance

    No; you CAN have only one design repository and in this, as many runtime connections as you would like: (development, test, education,pre-production, production etc). This might go against good application development practice, but it is possible, and can be perfectly ok in smaller warehouse projects with few developers. And thenyou don't have to go through the hazzle of moving metadata between repositories, in the correct order. One advice though: Have different passwords for the runtime connections, so you don't connect to the wrong runtime environment by mistake ;-)
    best regards
    Henrik Verup

Maybe you are looking for