OSB Installation in production environment

I am trying to install OSB 11g in production mode. But, the problem is its always pointing to the evaluation database, even though I don't require any DB (not using the reporting feature or OWSM). I saw the following workaround and it worked fine, but is it the only way?
This error you will normally see if you use the built in pointbase db with production domains only.
I would recommend you use different database in pointbase or better an oracle database. Work around would be to delete WL_LLR* from you point base and the domain will start with out problem.
If you are not aware of how to delete the table in Pointbase/Derby, then other workaround (I normally use when using production domain with Derby/Poinbase) option would be to open config .xml and delete <jdbc-system-resource>
<name>wlsbjmsrpDataSource</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/wlsbjmsrpDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Even if i configure a different DB, but it still pointing me to Derby?
Is this a bug with OSB 11g installation in a production env?

Hello Bijoy,
The evaluation database is provided for use by the sample applications and code examples. If you do not want to use evaluation DB then don't install it.
To not install evaluation DB, while installing weblogic, select custom installation type, uncheck the "Evaluation Database" checkbox ("Server Examples" will automatically get unchecked) and proceed. Now your weblogic will be installed without an evaluation DB.
Regards,
Anuj

Similar Messages

OSB 11g Installation in production environment

I am trying to install OSB 11g in production mode. But, the problem is its always pointing to the evaluation database, even though I don't require any DB (not using the reporting feature or OWSM). I saw the following workaround and it worked fine, but is it the only way?
This error you will normally see if you use the built in pointbase db with production domains only.
I would recommend you use different database in pointbase or better an oracle database. Work around would be to delete WL_LLR* from you point base and the domain will start with out problem.
If you are not aware of how to delete the table in Pointbase/Derby, then other workaround (I normally use when using production domain with Derby/Poinbase) option would be to open config .xml and delete <jdbc-system-resource>
<name>wlsbjmsrpDataSource</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/wlsbjmsrpDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Even if i configure a different DB, but it still pointing me to Derby?
Is this a bug with OSB 11g installation in a production env?
Thanks,
Bijoy

Hello Bijoy,
The evaluation database is provided for use by the sample applications and code examples. If you do not want to use evaluation DB then don't install it.
To not install evaluation DB, while installing weblogic, select custom installation type, uncheck the "Evaluation Database" checkbox ("Server Examples" will automatically get unchecked) and proceed. Now your weblogic will be installed without an evaluation DB.
Regards,
Anuj

Oracle Installation for Production Environment.

Hi All,
We need to install Oracle in our production environment.
But since there is no DBA in our project, we need to do it by ourself.
I was just wondering what all steps and cautions I need to take to install it.
I was told just double click on Setup.exe :-) and that would suffice.
I am pretty sure its not that easy, atleast for a production environment.
We might need to set some params, may be.
We are at present using Oracle 10g Rel 1.
Any help/suggestion would be highly appreciated.
Thanks in Advance,
Tanuja

Well, it does more complicate than a double click of setup.exe, especially for a production database.
It's not only about the installation, also think about how do you want to create your database, the storage configuration, database configuration, and backup/recover strategy etc.
For installation, make sure you follow Oracle installation guide,
http://download.oracle.com/docs/html/B10130_02/toc.htm
And there are many other document here
http://www.oracle.com/pls/db10g/portal.portal_demo3?selected=1

ORACLE NOSQL INSTALLATION ON PRODUCTION ENVIRONMENT

Hi ,
I have already installed nosql in my test server using kvlite. My doubt is how to setup ORACLE NoSQL on production environment ?
Please suggest .
Thanks
Edited by: 861012 on Sep 3, 2012 12:54 PM

Hi Kamran,
I am using doc - http://docs.oracle.com/cd/NOSQL/html/AdminGuide/Oracle-NoSQLDB-Admin.pdf
Here on page-26 while "Create the Remainder of your Storage Nodes" i am getting following error -
kv-> plan -execute -name "Deploy n02" deploy-sn 1 node02 5000
Exception while executing command plan: Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 9[Deploy n02] finished in state ERROR. Problem during plan execution: Exception creating connection to: node02; nested exception is:
java.net.NoRouteToHostException: No route to host
kv->
I have already configure iptables to allow network traffic to port 5000. Still i am getting this error java.net.NoRouteToHostException: No route to host
Please suggest how to resolve this.
Thanks
Edited by: 861012 on Sep 4, 2012 3:42 PM

Biztalk Server 2010 installation in production environment

Hi All,
Our client is undergoing an envirorment upgrade.
here i have to migrate biztalk server 2010 from production old envirorment to production new environment.
can anyone please suggest the links how to instal the biztalk server in production envirorment as visual studio is not present.
And what all the requirements to be considered before installation.
And if posiible please suggest in steps..
Thanks

The BizTalk Server documentation download (http://www.microsoft.com/en-in/download/details.aspx?id=11503) and specifically the Installing BizTalk 2010 and BAM in a multi-computer
environment document should get you up and running.
After that refer to the BizTalk 2010 Performance Optimization guide for the various SQL and OS related settings that should be configured. Examples being the registry key to address TCP/IP Port exhaustion, etc. (refer
http://www.microsoft.com/en-in/download/details.aspx?id=10855)
The BizTalk Server 2010 Operations guide is an excellent document for various Hot To's such as clustering the Master Secret, configuring the BizTalk Log Shipping, DR preparedness, etc. (refer
http://msdn.microsoft.com/en-us/library/gg634499.aspx)
Visual Studio on Production servers is not recommended. If gacutil is what you want then, you may choose to install ONLY the Visual Studio Developer Tools which would get you the required utilities.
You have not mentioned the version you're migrating from? As part of the BizTalk documentation there are migration documents such as for TPM Database, Parties, etc. which you might require.
For the applications (BizTalk), they would need to be migrated to .Net 4.0, recompiled and deployed.
Ideally you should setup a migration environment T & D where you'd examine and explore these various options including the suitability/applicability of the 3rd Party adapters/components that you currently use.
Regards.

SOA OSB Deployment best practices in Production environment.

Hi All
I just wanted to know the best practices followed in production environment for deploying OSB and SOA Code. As you are aware that both require libraries from either (Jdev or SOA Suite) and (OEPE and OSB)? Should one rip the libraries and package them with the ANT scripts (I am not sure but SOA would require its internal ANT scripts and lot of libraries to be bundled, OSB requires only a few OEPE and OSB libraries) or we simply use the below:
1) Use the production run time (SOA Server and OSB Server) to build and deploy the code. OEPE would not be present here, so we would just have to deploy the already created sbconfig.jar (We would build this in a local environment where OEPE and OSB would be installed). The code is checked out from a repository and transferred to this linux machine.
2) Use a windows machine (which has access to prod environment) and have Jdeveloper, OEPE and OSB installed to build\deploy the code to production server. The code is checked out from a repository.
Please let us know your personal experiences with the deployment in PROD. Thanks a lot!

There are two approaches for deployment of OSB and SOA code.
1. Use a machine specifically for build and deployment which will have access to all production environments (where deployment needs to be done). Install all the required software (oepe, OSB etc..) and use remote deployment for deploying the code.
2. Bundle all the build and deployment related libraries and ship them as a deployment package on the target server and proceed with the deployment.
Most commonly followed approach is approach#1.
Regards
Vivek

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

OEPE installation for production server

Does Oracle Enterprise Pack for Eclipse (OEPE) is required for WebLogic server installation (SOA 11g) for production environment ?
Or this is needed only when you need to develop some some SOA stuff ..

I got the answer that this is needed for OSB 11g.

Production environment, error in BPELConsole

Hi there,
I had installed, following step by step the installation guides, a production environment on three linux boxes RHE3; one for the DB v10g and in the others two an AS whit j2ee and web cache and obviously BpelPM. I do not installed WebCache AS component because an Oracle guy told me that bpel go crazy if webcache runs.
I can connect BPELConsole, but after the login I get this error message:
==========================================================
ORABPEL-04001
Cannot find instances.
An attempt to fetch the instances using the where condition " ( ci_state = 1 OR ci_state = 2 OR ci_state = 3 ) order by ci_modify_date desc " from the datastore has failed. The exception reported is: ORA-00942: table or view does not exist
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: Select * from ( select a.*, ROWNUM rnum From ( SELECT * FROM admin_list_ci WHERE ci_domain_ref = 0 AND ( ci_state = 1 OR ci_state = 2 OR ci_state = 3 ) order by ci_modify_date desc ) a Where ROWNUM <= 20 ) Where rnum >= 0
at com.collaxa.cube.engine.data.AdminFinder.getXInstanceCount(AdminFinder.java:583)
     at com.collaxa.cube.engine.data.AdminFinder.getOpenInstanceCount(AdminFinder.java:529)
     at com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getOpenInstanceCount(BPELProcessManagerBean.java:117)
     at IBPELProcessManagerBean_StatelessSessionBeanWrapper46.getOpenInstanceCount(IBPELProcessManagerBean_StatelessSessionBeanWrapper46.java:955)
     at com.oracle.bpel.client.BPELProcessHandle.getOpenInstanceCount(BPELProcessHandle.java:519)
     at displayProcess.jspService(_displayProcess.java:508)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:798)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:211)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:127)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
==========================================================
Can Anyone help me?
Thanks in advance
Stefano
null

Hi,
as you know, your help was very useful.
Maybe is better to add the whole path of file that have to be changed
(only for beginners like me)
IRCA/integration/bpelpm/admin/sql/bpmuser.sql
This is true for DB version 10g release 2 or upper. For the previous versions the original string is enough.
Thanks again,
Stefano.

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.

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/

Configuration Tasks in a Production Environment

Do I have to configure SSL for Oracle Apps ? Use Oracle Wallet Manager to do so?
Also do we have to generate Server ids for security purpose in a production environment ?
These steps are stated as an initial task after installing Oracle Apps ?
Is there a document for Post Install Tasks after installation of EBS 12 ?
Thanks
RK

Refer to the following note to configure SSL in R12.
Note: 376700.1 - Enabling SSL in Release 12
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=376700.1
Is there a document for Post Install Tasks after installation of EBS 12 ?Refer to the installation manual and the release note Metalink note. You can also apply all recommended patches (Check Patches & Updates tab in Metalink for more details).

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.)

Disable ACC in production environment

Hi,
How do i disable the ACC link (just that link alone) that appears in dyn/admin in production environement?

As Nitin said by default the link of dyn/admin will be disabled for standalone ear.
If its not a standalone ear then in your ATG installation on production box modify the below file to remove the link.
C:\ATG\ATG10.1.1\DAS\admin\atg\dynamo\admin\en
Peace
Shaik

OBIEE 11.1.1.6 Production Environment on AIX

Hi Friends
Consultant from Oracle installed OBIEE on three AIX machines.One is database server,web logic and OBIEE server installed on one machine, Informatica and DAC server installed on one machine.Ii is our Dev environment,My boss is planning for Production environment.
To build production environment, Do we have to start the installation process from the beginning or is there anyway we can copy from existing Dev environment
Please suggest
Thanks,

The process is basically setting up a Secure Shell (SSH) and then using RCP or SCP to copy files over. Again, details can come from a System Administration expert. Also, you may need to change some things around once the OBIEE components are moved to a new server.

OSB Installation in production environment

Similar Messages

Maybe you are looking for