Development and Production SLDs

We have completed Development and testing of XI objects and are at a stage to transport the objects to Production. We have two SLDs for XI, one for Non-productive systems and another for the Prod system. As regards to SLD entries for transport to Production, I though the following is the process
1.     Create Production Business systems in DEV-SLD putting them in the right Business group
2.     Export DEV-SLD entries
3.     Import the file into PROD-SLD
4.     After go-live only delta SLD entries would be exported and imported into PROD-SLD
In the following Weblog, /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation, Yuvaraj talked about SLD data supplier bridge from Dev SLD to Production SLD. Is this absolutely necessary? With the bridge operating, what happens if somebody deletes a business system by mistake in Dev SLD?
Any inputs would be appreciated and rewarded

Bhavesh,
My reason for not having prod entries on Dev SLD is that if Prod Entries are going to be on dev SLD, then why have a separate SLD for Prod itself?
My logic for this would be during development, create all the Production Business Systems in DEV-SLD and transport them to PROD-SLD. At runtime system uses Prodcution-SLD. I guess the differernce is design time vs Runtime.
But once again, SAP recommends a single SLD and so when the landscape contains multiple SLD's there are no rules on how to go about this and so either way things will work fine :-)
SAP's recommendations seem to have changed off late. Though in online help they have again and again mentioned that one SLD is recommended, I do know that some internal SAP Consultants recommending separate SLDs for non-productive and productive purposes. There are also documents on Service market place providing information on how to set-up two SLDs for productive and non-productive purposes.

Similar Messages

Development and Production Requirements for a Forms/Report application

Dear all,
We have an application witch run in client/Server mode using Forms/Reports 6i For 300 users.We want to migrate it on Forms/Reports 9I using Oracle 9IAS and Oracle 9IDB.
I would like to have advises about material requirements of both development and production environment((developer deskop, development appServer and databaseServer, end user desktop,production databaseServer and production AppServer).
Thank u for giving more details about my request.

I have my dev and production on 2 different databases/instances, and the workspaces have a different name aswell (think 'dev' and 'prod').
I do reuse my application ids, which makes the whole process a lot more manageable: easier for me to identify and replacing a whole application.
However, when i want to replace only 1 page, apex stumbles over the workspace. Bummer.
So i took an export of a page on both workspaces, and opened the files.
prompt Set Credentials...
begin
-- Assumes you are running the script connected to SQL*Plus as the Oracle user APEX_040100 or as the owner (parsing schema) of the application.
wwv_flow_api.set_security_group_id(p_security_group_id=>nvl(wwv_flow_application_install.get_workspace_id,1377027056414870));
end;
wwv_flow_application_install.get_workspace_id,1377027056414870));
I took both workspace IDs and keep them in a simple txt in my installation-files folder. Each time i need to import a page from dev->prod i go in the exported file from dev and change the workspace id to the id of my production workspace id. Everything works magically after that.
If your application ids also differ, you can try changing the id in the exported file aswell, but i can't tell if it works or not since i've not done that yet.
prompt Set Application ID...
begin
   -- SET APPLICATION ID
   wwv_flow.g_flow_id := nvl(wwv_flow_application_install.get_application_id,130);
   wwv_flow_api.g_id_offset := nvl(wwv_flow_application_install.get_offset,0);
null;
end;where of course you'd change around nvl(wwv_flow_application_install.get_application_id,130);

URL Link Difference in development and Production

Hi all ,
im seeing the URL for support desk BSP page different comaparing in development and production .see the below
http://s01tdi135.intra.tm:8003/sap/bc/gui/sap/its/webgui?sap-language=E&sap-client=011Code=/08&pcmd=CRMVW&pnumb=45CB5F7BE4030746000000000A0135AD&pvariant=&
in the above URL is available in Dev server. we are passing the GUI here , so in program we are concatenating the GUID with the URL.
But in production , when you concatenate this , its not coming ...becuase when u see the URL for message,refer below
http://s53kj173.intra.tm:8001/sap/bc/gui/sap/its/webgui?sap-language=E&sap-client&transaction=DSWP_SAPSHORTCUT&OkCode=/08&pcmd=CRMMR&pnumb=&pvariant=&paarg=X&
Here im not able to see the GUID ... how to show the perticular message in e mail ...
actualy how i can pass the parameter ..that means support no to this URL.
pls explain ...

Actualy problem with user authorization. solved.

How to populate SNDPRN with different values in Development and Production?

Hello experts,
I have to fill the field SNDPRN in the message mapping with a different value in Development and in Production. As I am new to PI, I used a simple solution - but it is rather ugly: I set a constant value in the mapping in development and a different one in Production. However, I would like to know if there is any solution to have a condition in the mapping like:
IF system is Development, set SNDPRN as Constant1.
IF system is Production, set SNDPRN as Constant2.
(And eventually IF system is Test, set SNDPRN as Constant3)
Thanks in advance for your help,
Luis

Hi Luis,
      You can go with the parameterized mapping , where you can provide different values for SNDPRN in interface determination for development and production.
      At point of time if you want to change the values it requires only a change in the configuration.
      Please refer the below links for reference;
Parameterized Mapping Programs - Enterprise Services Repository - SAP Library
http://scn.sap.com/people/jin.shin/blog/2008/02/14/sap-pi-71-mapping-enhancements-series-parameterized-message-mappings
     We are following the same approach for some of our interfaces.
- Muru

Crystal Develop and Production Guidelines in SQL Server (Crystal 9)

We have development and production environment on 2 different machines.
It seems when we want to migrate a report from dev to prod, we need to reset the DSN or connection and crystal then forces us to respecify all field names in a report.
It is a big pain. Has anyone seen this?
Thanks
Ken Light
DBA Interior Health

Hi
When you migrate a report, you need to
- Create a DSN with same name on Production as it was on Test.
- Do a set Datasource location.
- Verify database to ensure all changes made in the database are reflected.
- If you have used stored procedure with parameter in your report, then uncheck the above option and then refresh the report.
Hope this helps!!!
Regards
Sourashree

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

Development and Production System

Hi,
I have Configured some settings,Integrated R/3 System and developed some portal components in the Development SAP EP Server.
Now i want to know shud i do all these things once gain in the Production Server.....Not Obviously right
Then what is the procedure and how actually i can acieve my goal
Regards,
Ricky Ford

Hi!
Welcome on SDN.
There might be a problem with the spooler configuration, or the spooler capacity is too small. Check it out in SPAD transaction or ask someone from the basis.
You might check the user name as well. If the job is scheduled by user XY, then the spool request will be uner XY's name.
Regards
Tamá

Development and Production

Hi All,
I had to append a field in development. I appended in dev. already there is init and delta happening. Every half an hour delta is uploading. so after I append the field, do i do a full upload or init again or do a delta again? so what happens to the data already in the data target?
thanks in advance
Abby

Hi Abby,
If you want the newly added Info Object to have values for historical data also, you have to do an Intialization or Full Update and then Initilalization w/o data transfer.
In this case, you'll have to delete the existing data and load it again from the source.
Before delta extraction to occur, there should necessarily be an Initialization. Init load will help the source system to keep track of the changes to existing records or new records sothat only these records is extracted to BW as Delta.
If you've already done a full update, then Intialization without data transfer is used to enable the data source for the further delta loads. In this case no records are transferred to BW.
If data is already present in cube, it's not recommended to be loaded again.
If the data is already present in cube, it'll be aggregated(Cube supports only Addition). However the request numbers will be different.
For ODS, there are two options. Addition and Overwrite. So if it's set to addition your records will be added to the existing one's and in case of overwrite, the previous data will be overwritten.
If you don't want the new info object to be populated for the historical data, you can keep the existing data as such. Add the new info object in cube after deactivating the update rules, maintain the transfer rules for this new info object and then go for delta updates. Only the new deltas will have values for this newly added object.
It all depends on your business requirements.
You can go for an export data source also.
Hope this helps.
Regards
Hari

Questions on Analyzer Upgrade and Moving Analyzer Reports from Development to Production

Hi,We run Analyzer 5.0.3. We are planning to go to Analyzer 7.2. Did any body go thru this upgrade? If so, what is your opinion and tips that may help. Also, we never had Analyzer development environment. We are planning on having Analyzer development environment. In our installation, all of the Analyzer reports are centrally developed based on user requests. Once we have development and production at the same Analyzer version, if a report is developed in the development system, how can the report be mirateed/moved from development to production system?Thank you for your help,Prasant

Balaji,
Has this been done yet?
Gary
<BLOCKQUOTE>quote:<HR>Originally posted by [email protected]:
We are working on a document using which one should be able to move a portal instance from one database to another. It is still in draft version, once it is finalized we will be putting it on otn.
Thanks and Regards
Balaji<HR></BLOCKQUOTE>
null

XI Development , QA , Production Landscap

Hi All,
I need to design a document that shows the XI dev,QA & Production systems. Can anyone tell me where can i find such a image.
Also do we create seperate SLD for development and production or only create one SLD and export that as a file and finally import in the production.
And how do we transport objects from development from dev to QA or production.Is there any other way apart from exporting tbz file and then copy the tbz file and put it in the import directory in the QA server. I mean the way we do in R/3.
Thanks
Sumit

Hi Sumit,
>I actually want a pic wherein apart frm XI all the other business systems are also there.
of course you have to create a picture of your individual system landscape for your own. Come on, take powerpoint.
>And also want to know if more than XI servers are installed or only XI server is installed.
Sometimes you should read again what you wrote before pressing the "post" button
>My question is that what if the XI server fails? Do we have a switchover software in that case ?
This is not a special XI theme. Read the guid "SAP Exchange Infrastructure in High Availability Environments" at service.sap.com/ha ->Media Library ->Documentation->Misc. Documentation
or read
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/5741114ae611d1894f0000e829fbbd/frameset.htm">SAP High Availability</a>
Regards,
Udo

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.

OWB propagation from development to production environment

Our department is in need to implement overall security around our production data warehouse.
One issue that seems to bother our management is having only one OWB Designer where developers would have to be responsible enough to use snapshots and export mappings to mdl files. Management would like to have development and production OWB Designer Repository where production designer would always be in sync with what is deployed in prd database. Also prd OWB Designer Repository would be like a source safe so we have to always get a mapping from prd designer move it dev designer and when done propagate changes back to prd designer and then deploy to prd database.
Would this be a good approach?
Any input on how to handle propagation from development to production environment, and if you are aware of "best practices" when it comes to OWB environment is appreciated.
Best Regards,
Vlasta

Hi,
Copy whole catalog and rpd from dev to prob.
If you want to copy specific report go to OracleBIData\web\catalog\samplesales\root\shared\sample+sales(group folder name)
You can copy reports under folders and dashboards in _portal in Sample sales group folder...both file and .atr file.But you may miss security applied on those dashboards.
http://www.rittmanmead.com/2008/04/28/migration-obiee-projects-between-dev-and-prod-environments/
Best practice is to copy whole catalog and rpd (or) Copy shared and system folders and their .atr files from OracleBIData\web\catalog\samplesales\root so that you will not miss security and you will not over ride users folders which may contain some data created by them.
Thanks,
Srikanth

Best methodology to have dev and production?

HTML DB users-
A customer asks what are some of the better methodologies to have a development and production environment with HTML DB? They are used to having controlled releases of new features and fixes into the production environment and want to do that as well with HTML DB.
We would like your thoughts...
The customers exact question:
Our thinking is that we develop in a development workspace and app and then migrate via export and import to a production workspace and app.
What we have encountered is several issues:
1) After the workspaces have been set up the user can only point to one at a time.
2) We get integrity violations in the export an import.
Is there a better methodology/solution?
You help is greatly appreciated.
Cheers,
-david

david,
Different options for separating production from development environment are discussed in this best practices whitepaper:
http://www.oracle.com/technology/products/database/htmldb/pdf/Oracle_HTML_DB_Best_Practices.pdf
Do you have more details on the two issues that were raised about the current approach:
1) After the workspaces have been set up the user can only point to one at a time.
2) We get integrity violations in the export an import.
Why can the user only point to one at a time? What does that mean? Can you describe the steps used to export and import and show as error messages?
Sergio

Enterprise Deployment for Hosted Devlopment and Production

We are moving from a 11G dev environment to 11g production. We chose Installation scenario#3: Enterprise Deployment for Hosted Development and Production so we could scale out the load to multiple servers. I am at the point now where I need to load my repostory and webcat(dashboard files) and I want to make sure I understand what needs to be done.
Do I load my Repository and Webcat directory on the first node and it deploys it automatically to the 2nd node or are there other steps to do this.
Thanks!

Hi,
I thought about that possibility, but since in the Apple website I read that
"Deploy proprietary, in-house applications to authorized users in your company, the iPhone Developer Enterprise Program is available to companies with 500 or more employees and a Dun & Bradstreet number."
Since I'm freelancer,I don't have 500 employees, neither the Dun & Bradstreet number.
Can I subscribe to the program in the same way?
Also, if I subscribe the Enterprise program, I can also develop and publish "normal" apps for the iTunes, or do I need to have another subscription?
Best regards and thanks for the fast answers
Paulo Correia

Is SQL Developer free product?

Is SQL Developer free product?
It says "Free product" on the OTN site, but when I read the License Terms it is different.
Can we use this free product for commercial purpose on the licensed Oracle database?
or
do we have to purchase a separate license for SQL Developer also?
any reply is appreciated
Thanks!
RG

Lets be specific.
SQLDEveloper is available without charge under the terms of the OTN license, which has been amended to allow one download to be used in several machines. This includes both development and production use of same. All other terms such as ownership, decompilation etc still hold.
Barry
Edited by: Barry McGillin on Dec 9, 2009 9:33 AM

Development and Production SLDs

Similar Messages

Maybe you are looking for