Bring one more LDAP in production environment

Hi All,
I am running Sun Java Enterprise System 2004Q2 on Solaris 9 (sparc) platform. JES applications that I am using, are;
1-Directory
2-Messaging
3-Calendar
I have 2 LDAPs and both are masters (1 is primary and other is failover). Now I want to bring another LDAP in the production environment. What do you suggest to make it possible without any downtime?
Regards,
Shujaat Nazir Khan
Senior System Engineer
Network Operations Center
Cyber Internet Services (Pvt) Ltd.
A-904, 9th Floor,
Lakson Square Building # 3,
Sarwar Shaheed Road, Karachi-74200
Mobile: 0300-2033146
DID: 5698793
UAN: 111-44-55-66
Ext: 5793

There is no downtime required. Bascially i would suggest that you add a 3rd master into your enviroment. However depending on the exposure of the 3rd server (i.e. if it is exposed to the outside world) you could also consider a consumer since it is read-only.
Anway the procedure is thoroughly laid out in the docs.
http://docs.sun.com/source/817-7613/replicat.html
I would suggest that you read the documentation for the full details of steps required but very briefly the outline is...
1. Build the new server and tune it according to your environment.
2. Enable replication on it. Choose master, hub or consumer.
3. Create replication agreements to it from the existing masters.
4. Perform an online initilization from the console from one of the masters or export ldif via "db2ldif -r" on one master and then import the file via "ldif2db" on this 3rd machine.
5. Check that replication is working either by manual inspection or insync utility.
Note that depending on the load on your server(s) and network this should be done at night time or non-peak hours. The ldif export/import is recommended if you have hundred of thousands of entries or more.
Regards,
-Wajih

Similar Messages

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

User can not add more then two products against one order

Hi frnd,
My requirement is in CRM while creating order using CRMD_ORDER transaction. The user can not be entered more then two products against one order.
I am using CRMD_ORDERADM_I_BADI badi to give error I am unable to use this badi. Is there any other options are there.
Please do need full help.
Regards,
Ashish.

Hi Amit,
DATA: gt_header TYPE crmd_orderadm_h. "OCCURS 0 WITH HEADER LINE.
data: ET_PRODUCT_I     TYPE     CRMT_PRODUCT_I_WRKT.
data: gs_PRODUCT_I     TYPE     CRMT_PRODUCT_I_WRKT.
DATA : gt_header_guid     TYPE     crmt_object_guid_tab.
DATA : gs_header_guid     TYPE     crmt_object_guid.
gs_header_guid = IV_HEADER.
*INSERT gs_header_guid INTO TABLE IV_HEADER.
CALL FUNCTION 'CRM_ORDER_READ'
    EXPORTING
      it_header_guid       = gt_header_guid[]
    IMPORTING
      ET_PRODUCT_I         =   ET_PRODUCT_I[]
    EXCEPTIONS
      document_not_found   = 1
      error_occurred       = 2
      document_locked      = 3
      no_change_authority = 4
      no_display_authority = 5
      no_change_allowed    = 6
      OTHERS               = 7.
endmethod.
I am using ds code. Its working fine records are coming in Product. But how i will save product into one
itab.
Regards,
Ashish S

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.

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.

Weblogic 8.1 Server log size increase in Production environment

Hi,
Issue:: One of the log file is increasing in size and exceeding beyond the size mentioned in the configuration file resulting in application outage.
Issue description:
We are having problems with the log size in the Weblogic 8.1 server. The fileminsize has been mentioned in the config.xml.
New log files like MYsvr.log00001,MYsvr.log00002, MYsvr.log00003, MYsvr.log00004 etc are also being generated appropriately when the max file size has been reached. But simultaneously, one of the files is growing in size, exceeding the limit mentioned in the configuration file. Eg.. the MYsvr.log00001 file is 800MB in size while the other files(MYsvr.log00002, MYsvr.log00003 etc are 10MB in size)
This increase in size of the log has been resulting in an application outage.
More Details:
1. Server: BEA Weblogic 8.1 server
2. Log size is fine in other environements. This is a problem only in the production environment.
3. The entry in the config.xml is as follows:
<Server ListenPort="6313" Name="MYsvr" NativeIOEnabled="true" TransactionLogFilePrefix="./">
<ServerStart Name="MYsvr"/>
<Log FileMinSize="10000" FileName="MYsvr.log" Name="MYsvr"
NumberOfFilesLimited="true" RotationType="bySize"/>
<SSL Name="MYsvr"/>
<ServerDebug Name="MYsvr"/>
<WebServer Name="MYsvr"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="MYsvr"/>
</Server>
Could you please help with this issue ?
Thank you.

Can someone please provide a solution for the issue

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.

RE: Production Environment Definition

Brad,
We use connected environments so that we do not have a single point of
failure.
We use multiple environments and connect them together in a star topology
for reliability of service. Our servers (23 in total) sit out at branches
in the back of beyond and the WAN connections between the servers are
unreliable. One needs a reliable connection to the Name Service which sits
on each Environment Manager. We have thus created 23 connected
environments with an Environment Manager on each LAN. Connected
environments are still a bit buggy but Tech Support is currently working on
fixing the last of the problems. We are still on ver 2H15 for this reason.
Disadvantages of this topology are that making distributions take a long
time because referenced partitioning cannot be scripted in fscript and
econsole only connects to one environment at a time.
There is a Forté consultant in Denver called Pieter Pretorius who has had a
lot of experience with our connected environments. It may be worth
chatting to him.
Regards,
Richard Stobart
Technical Consultant for Forté
E-mail [email protected]
Quick-mail: [email protected]
Voice: (+ 27 83) 269 1942
(+27 11) 456 2238
Fax: (+ 27 83) 8269 1942
-----Original Message-----
From: Brad Wells [SMTP:[email protected]]
Sent: Tuesday, February 10, 1998 11:52 PM
To: 'Forte Users - Sage'
Subject: Production Environment Definition
Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

What level of access a DBA should have on production Environment

We are in the process of auditing
I want to know what level of acccess a DBA has on a production server..How about the Backups ONLINE/EXport backup? Which account should be used for those purposes...
Can i DBA login as SYSTEM or SYS user? or he should have separate account to do all the activities..
I am more on protecting the data from unauthorized user..Any standards followed for that
Best Regards
Maran

Hi Maran,
What level of access a DBA should have on production Environment
root
However, there have been cases of dishonest DBA's and SA, manipulating data for profit and stealing data:
http://www.dba-oracle.com/art_lumigent_whitepaper.htm
Kevin Mitnick, the noted computer felon likes to show how security breeches are commonly the result of employee errors. In his book “The Art of Deception”, Mitnick talks about his techniques to get trusting employees to disclose confidential information and privileged passwords. In one case Mitnick was able to secure a privileged password using the name Lemonjello, and then bragged about the naïve employee who handed-over a system password to someone called “Lemon Jell-O”. In this case the IT staff was never able to ascertain the root cause of the breech because their mechanism for the dissemination and auditing of secure information was inadequate.
Today, there are ways to seregate the audit trails, giving the DBA what they need to do their job, while not giving them the keys to the kingdom.
Hope this helps . . .
Donald K. Burleson
Oracle Press author
Author of "Oracle Tuning: The Definitive Reference"
http://www.rampant-books.com/book_2005_1_awr_proactive_tuning.htm

Subversion Production Environment Setup

Hi Everyone:
We are trying to set up our production environment. We are using Tortoise SVN for our repository. We have 2 servers "devl" and "prod". We have 2 runtime environments, one on each server. Currently we have only one copy of the applications on "devl" in Tortoise SVN.
There has been some discussion lately on whether or not we need to keep a copy of the application in its production state on "prod".
For those of you already in production environments using Tortoise SVN (Subversion), what have you found works best and your reasoning behind it.
Thanks very much in advance.
Mary
UofW

Hi Mary,
This isn't really a JDeveloper question, but relevant nonetheless. Let clarify some issues before answering though.
1. From what I understand you have two server for RUNNING your application, is that right? One is devl for development, integration and acceptation? While the other is prod for production? If so, then your question is not really valid. Normally you keep your repository on a single server (or a more complex topology if you have a really huge development team) that is NOT necessarily (and often not) the same as the runtime servers. This is quite useful for backup purpose, maintainability and scalability among other things.
2. What do you mean by "you already in production environments using Tortoise SVN (Subversion)"? If you mean having a system in production that used SVN as a versioning system, then yes, and it work just like I mentioned above using the branch and tag features of SVN to mark the code when it goes in production and when an experimental feature needs to be developed.
Regards,
~ Simon

Topology for production environment

this question is related to production environment deployment and clustering.
we have 1 physical server where we have webcenter domain. this domain has 1 admin server and 1 managed server (custom web center portal managed server).
our plan is to deploy our application on this managed server.
this is no clustered environment and not recommended (no failover, no load balancing).
what shall we do?
shall we create another managed server (custom web center portal managed server) and deploy our application on these 2 managed servers? there will be a load balancer in front to take care of transferring request to both the servers...
what's your suggestions?
please note that i know specific answer will depend on NFR (user load, performance etc) but i am looking for general guidance and reference around same like -
how many managed server recommended?
what kind of topology recommended for web center application?
etc
thanks.

jiri.machotka wrote:
I'd recommend you to start with this document: http://docs.oracle.com/cd/E11035_01/wls100/cluster/overview.html as a lot of this question is related to Weblogic clustering than WebCenter.
Note that whilst clustering has many pros, it has also few cons; among those:
- you might require additional hardware/software, or used components (like filesystem) will have to have features that you don't need in a non-clustered environment
- though small, scaling does consume some resources (I've heard that WebCenter Content takes 1-2% of Solaris, but up-to 25% on Windows Servers!)
- it's always at least a bit more expensive
Therefore, you should not go for a cluster, because it's cool, but because you have damn good reasons for that (that you didn't mention!), stemming from SLAs, or requirements for Disaster Recovery.
You write that you have just one physical server, so you already have one potential single point of failure.
I think I've heard that Weblogic Server itself is capable of self-recovery; this means, that a server may go down (you will lose all the current sessions), but is capable of auto-recovery. If your users survive that from time to time they will lose uncommitted work, then maybe a need for clustering (HA) won't be that strong (you might also go just for tuning your Weblogic Server).
On the other hand, where clustering might be necessary, if you need to scale, especially, if you need cloud-like increase/decrease of resources. I doubt it is possible to say up-front how many servers is recommended, but you may tune this later - whilst going from 1 node to 2 is relatively a big leap, going from 2 to 3, or 3 to 4 is then quite easy.
Either way, I'd recommend you to be in sync with your app server admin.thanks jiri. this was helpful.
while i agree that any architectural decision should be justifiable to requirements but as far as my experience goes clustering is basic thing in any production environment... in case 1 managed server goes down, other can still serve requests...
i'll read link provided by you and ask specific questions if any...
thanks.

Automatic Deploying of Portal Configuration from Staging to Production Environment

Hello,
I'm anlyzing the opportunituy to write an automatic procedure that synchronize
our WebLogic Portal production environment with the staging one. These two environments
are physically separated.
I have found the BEA Propagation Tool. However it seems that is not possible to
define a procedure that is really totally automatic.
Firts of all, it is necessary to hava an manual operator that selects the objects
that have to be propagated and after starts the propagation process.
Besides it is necessary to have database connections beetween the progation tool
and both the environments.
What I'm looking for is a solution that
1. analyze the staging environment
2. export some files that contain both code, configuration and data (code, LDAP
and DB data)
3. import these files into the second enviroment
has someone deal with this problem?
Thans in advance
Ciao

Manish,
to answer your questions -
1. You can find the exact date and time for these refreshes/maintenance schedule on your production pod. Just go to 'Training & Support' in your production. There will be a calendar in which you can see the maintenance schedule. The details are quite accurate. to be sure of the time I would suggest you get in touch with the Service/Support rep at Oracle.
2 & 3) Oracle CRM On Demand provides a Migration Tool that can be used to migrate configuration changes from on POD to another. This can be between Staging --> Production and vice versa. Although, I would recommend that you go through the migration tool bookshelf and understand in detail the use of this tool. There are limited configurations that can be migrated. So it would be wise to create a plan based on what changes you are looking to migrate.
Note: Reports are copied on the Staging after the refresh only from Prod to Staging. This does not happen from Staging to Production. Reports will have to be created in Production and will be copied on Staging on a Quarterly basis (Check your refresh schedule)
4) You can use the migration tool to migrate configuration changes from a live environment into another instance.
The migration tool can be downloaded from:
Admin --> Import and Export Tools -->Oracle Migration Tool On Demand
You can download the Migration Tool Bookshelf here:
http://docs.oracle.com/cd/E22393_01/books/OnDemMigrTool.pdf
Thanks,
Royston

Java Production Environment

I am trying to figure what pieces of software/components that I would need to run a java client-server application. Using a web browser accessing information from a server.
I have programmed with Java using struts in the past, but have not ever set up the environment. (We used broadvision)
It seems like with the development environment (like Tomcat) all the pieces are included, but if I don't want to use Tomcat....what can I interchange.
I figure I need the JVM.....do I need J2EE latest version? Is there a piece that can be the servlet engine seperate from the web server. It seems like all I see is a mix of the web server and the servlet engine?
Any help is greatly appreciated.

Thanks for responding!
I am thinking about using Tomcat. However, business wants to have other options available.Other options are indeed available, but Tomcat is a pretty good one. Don't dismiss it out of hand.
We will probably be running in a Windows 2000 server
environment. Is IIS usually the preferred web server?Preferred by whom? I think that's a question for your sys admin. You'll want to have the Web server you're currently using to listen to the outside world forward requests to the servlet/JSP engine.
I'm not sure how the market shares of Apache and IIS break down, but I believe Apache's more common. IIS is built into Windoze servers.
Is Tomcat supported in a production environment?I'm sure you can find examples of Tomcat in production environments.
I'd ask again: supported by whom? Are you asking if there's somebody you can phone at Apache if there are problems? I don't believe so, no more than you can for any open source project. If that's what's bothering your business folks, by all means have them ante up for a license to WebLogic or something that has support.
A couple of other questions...since I don't know for> sure. I am trying to get more technically inclined.
I beleive the JVM is free and downloadable (probably
installed on most machines by default anyways). Is the
J2EE package also free? (is it the same as the J2EE
SDK 1.4).I would defer any questions about licensing to a lawyer. Have them review the licenses and explain the consequences to you.
If I am looking at this correctly, is it fare to say these are the essential components to deploying a
production java client-server application:
1) Server (i.e. Windows 2000 Server)Gotta run it on some hardware.
2) Java Virtual Machine (JVM - installed on the server)Can't run Java without it.
3) J2EE 2.4/2.0 ( installed on the server)Not essential unless you're using EJBs.
4) Servlet/JSP engine (i.e. tomcat on server)Essential if you're using servlets/JSPs.
5) ** IF needed ** Seperate Web Server (If not wanting to use Tomcat to do both)Your call. Depends on load. How many clients do you expect? Tomcat's Web server might perform well enough.
6) Client - BrowserThat's the usual lightweight UI for Web-based client/server.
You don't mention a relational database. Were you planning on having one? Which vendor?

Migrating Trading Partner from test to Production environment

Hi,
My Production environment has configuration for two trading partner.
I need to migrate one more trading partner from test environment to (the existing) production environment.
I see Agreement level export, TP level export, Config level export options in Oracle B2B.
Can you please suggests as to which is the fastest and most accurate way to migrate new trading partner configuration?
Regards,
Ravi Shah

There is nothing as preferred option. However you can keep few things in mind.
1. Agreement Export - Preferred option , if you would like to export only specific Trading Partner and Agreement details.
2. Repository Export - For full repository export.
3. Trading Partner Export - This option do not keep any TP in mind while taking the export, hence you may not information about Delivery channel and Agreement. This provides information about Trading partner profiles and Supported Document defition of the trading partner.
Let me know.

Development and product environment

Dear all,
I want to setup two databases in seperated server. One for development purpose and another for product environment.
Which good method/tool in oracle can transfer data (like pl/sql,tables,fields) from
development to product environment?
Thanks you

I would strongly suggest cloning the database from Development to Production, using RMAN. You get a proper copy that way - and it isn't hard to do. Howard Rogers has all the answers here: http://www.dizwell.com/prod/node/9

Bring one more LDAP in production environment

Similar Messages

Maybe you are looking for