SD quotation managed through version control

Hello all,
How can I active the version control for a SD quotation? What I need is, check the changes made in a SD quotation using the version control.
Thnks in advanced.
RB

In our current J2EE environment an ant script builds a war and copies it to a staging file server, then there is a java app that deploys the war to weblogic with the weblogic scripting extensions. We are thinking of modifying this app to also deploy the PTE files that any portlets in the war depend on. Day one a jsp portlet requires a single session preference. The next day it needs a login token to use the PRC. How do you coordinate this? For us it will probably be done with custom scripting.
A developer modifies the jsp and checks that in along with a revised remote service pte file which has the new settings. The ant script will then build the war and package it into a tar with the pte file and finally drop it on the staging server. From there our existing java deployment web app can extract the tar, deploy the war and run a migration import on ALUI. Hopefully all this can happen in a transactional context so that that if the import fails, the new portlet is not deployed.
I don't want to run into the case where a new portlet is out on the QA box and the portlet service is misconfigured and isn't supplying the correct headers to the portlet tier.

Similar Messages

Source Configuration Management / Version Control

I was wondering what the Forte raving masses out there are doing about Source
Configuration Management and Version Control type of issues?
Have you been able to implement or "skunk work" a packaged product with your
Forte development environment?
Our shop consists of WindowsNT Forte developers coding for predominantly
Windows95 clients and a HP UNIX Central Server. At this time we currently use a
home grown "system" to handle Source Configuration Management and Version
Control issues. We are now looking to see if there is a better way to do this.
We've identified several Industry Standard packages (SCCS, CVS, Microsoft
SourceSafe etc.) and still haven't found anything very useful.
What I am seeing is that all of the packages so far have direct hooks in C++,
Visual Basic etc.
I have yet to see something with Forte hooks.
Kelsey PetrychynSaskTel Forte Technical Analyst
ITM - Technology Solutions - Distributed Computing (OTC)
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:[email protected]
Quality is not job 1. It is the only job!
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Kindly specify the email address to apply to for the mentioned job

Project Not Checking out From Version Control

All of our help projects are managed using version control
(Team Foundation Server).
I recently had an XPJ file that became corrupted. As per
Adobe's instructions, I deleted the XPJ and CPD files and
regenerated the project from the HHP file. That worked fine, but
now launching the project from the XPJ file opens the project
outside of version control. (I'm no longer being prompted to check
the files out.) I think this is because the newly created XPJ file
now disassociated with the source control. If this is true, how do
I get the XPJ file back into source control?
Hopefully this makes sense.
Christina Stommel

Hi Christina,
My understanding of the entire "version control" process is
limited but since no one else has thrown in, I will try to pass
along what little I know. What I have learned is that version
control works great until it doesn't.
What I've had to do in the past, when I've had these sort of
synchronization problems, is to remove the entire project from
version control (I would be sure to back up your local project as
well as your version-controlled project). Then, you should be able
to add the repaired project back to your source control software
(we use MS VSS but I think it shouldn't matter).
I have tried, in the past, to add individual files to the
database from the RH interface (you could try "check in all files")
and I have gone into the database and manually added the necessary
files, but I have had mixed results. In the end, it seems that
removing the project from version control, then adding it back, is
the only thing that is guaranteed to work.
Good luck!

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

I tried repairing iTunes through the control panel but there is a new message that "the file 'itunes library.itl' could not be read because it was created by a newer version of iTunes"

I tried repairing iTunes through the control panel but there is a new message that "the file 'itunes library.itl' could not be read because it was created by a newer version of iTunes"

Unless you deliberately downgraded iTunes this may be a sign of a corrupt library. See Empty/corrupt library after upgrade/crash.
tt2

Right tool for Configuration Management (version control) for Jdeveloper

All
Please share your idea and exepeience about right tool for Configuration Management (version control) for Jdeveloper Development. I used CVS in the past. Now In new company we are planning to use Oracle SCM. Is anybody used it before for Jdev Developmet ( BC4J/ADF and Struts project). Is SCM also intergrated with Jdev just like CVS.??
Jdev Team please guide us.
Thanks

Before you go with SCM you should read these two papers:
http://otn.oracle.com/products/designer/Schedule_2004.htm
http://otn.oracle.com/products/designer/FAQ_Schedule_2004.htm

Version Control Repository Manager could not be reached or is invalid

Hi All,
My Version Control Repository manager just stopped working for the reason I am not able to determinate, giving the below message: "The specified repository, %server name% , is invalid or not reachable"
There are no usefull messages in the system log, or the VCA / VCRM logs.
Please assist.
My OS is Windows 2008 R2 x64 for both the VCAnd VCRM.
HP SIM / VCRM version is 7.2
VCA version is also 7.2
I've tried both a domain account and the certificate.
This was working fine for 600+ servers, now it doesn't work for any of them.
Why doesn't this tool leave ANY usefull logs... ?

Tonkers just to point out VCRM stuff usally goes here
http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/bd-p/itrc-455#.VSweOMLD9aR
This can be caused by a restart of the VCRM server as it causes a reindex of the entire repositry which can take a few hours and causes clients to have the repository to appear as "down".
Can also be caused a failed login from a server with an old version of VCRA I believe this is a bug, basically the failed logon causes a manager service restart which of course causes a reindex of the system. Why it works this way I do not know nor have I logged a bug with HP. Its hard because I cannot repro it every time and it also sometimes happens randomly but its far more prevelant on boxes with old agent versions. Note here the current version of the agent that is in the HP repositry is like 7.2.2 but the current release is 7.3.X not sure why the have not allowed the new version to download.
VCRM is very finnacky they really need to nail down some addional preformance and reliability enhancements.

Version control and configuration management

How is version control and configuration management done for iPlanet6 web
and app servers?

I'm not sure if I understand exactly what you are asking. Neither iWS or
iAS have built in version control or configuration management. But
pretty much everyone integrates them with version control or SCM in some
way. Ranging from the complex (say integrating iAS and Interwoven) to
the simplistic (using CVS to track HTML documents or source code).
David
Chris Valliere wrote:
How is version control and configuration management done for iPlanet6 web
and app servers?

Version Control/Configuration Management

I am implementing version control at our site and would like to know the best approach to do this with Designer9i and whether I need another product like PVCS in conjunction with Designer? Also, can I access/control the versioned objects in the database?
Thanks in advance

Hi Irena,
9i Designer includes the Designer repository, otherwise
known as Oracle9i Software Configuration Manager (SCM).
This will give you all the version control/configuration
management functionality you require without any need to
use PVCS.
There are white papers and demos etc here on OTN to help
you set up and understand how to use 9i SCM. Please see
our Designer home page here on OTN for Designer specific
stuff and also the 9i SCM Home page for SCM only stuff.
Finally, there is also an SCM discussion forum too if you
have any SCM specific queries.
Hope this helps.
Regards,
Dominic

Version-Control / Change-Management

Hi there,
I know there is a nice function in Enterprise Manager controlling your versions of your database-design and your schemas.
That means: I can compare to schemas and the enterprise manager shows me the difference and what was changed during the last check.
Does anybody know, how this feature is called and where I can get more infos?
Thanx for help,
Christian

Hi Joe,
we are using Subversion and the Tortoise Client for version control of project files. For the forms modules we inheritated via OLB a parameter in each forms module with initial value like "$Revision:: 1234 $" which can be overwritten by subversion in case of check-in. For libraries/reports we use a dummy function which returns the revision string. So the revision can be set by Subversion on check-out/check-in and can be displayed/retrieved at runtime in the application.
Subversion/Tortoise can be configured to lock files on check-out, and to enter some comments on check-in. We use it for every kind of project file, e.g. database scripts, documentation, specifications, etc.
For the deployment of final solutions we have created a small PHP-script which compiles all source files newer than the compilated files. This script is able to "distribute" all compilated files into a specified directory. Then we have to call our administrator who will copy the contents of this directory to the live servers.
Hope this infos may help you.
Regards
Kai

Version control, build, deploy and release management of eBS applications?

Hi All
I am setting up a standard configuration management, build & deployment automation and change & release management process for all types of applications including Oracle eBS, Informatica, Siebel, Cognos, Java etc. As you know, SCM for Java and .Net types of applications are very matured, but not for other types of applications such as Oracle eBS.
Can you give me some hint or point me to some documents on how to manage Oracle eBS applications from SCM's perspective? For example,
1. How to version control eBS artifacts? e.g. what kind of eBS artifacts need to be version controlled?
2. How to build eBS artifacts and then deploy to a new environment? How to move an eBS application from one environment (DEV) to test environment?
3. How to manage changes?
We have a standard SCM tool called RTC from IBM, which has version control, build and change control functions.
Thanks
Jirong

hujirong wrote:
Hi All
I am setting up a standard configuration management, build & deployment automation and change & release management process for all types of applications including Oracle eBS, Informatica, Siebel, Cognos, Java etc. As you know, SCM for Java and .Net types of applications are very matured, but not for other types of applications such as Oracle eBS.
Can you give me some hint or point me to some documents on how to manage Oracle eBS applications from SCM's perspective? For example,
1. How to version control eBS artifacts? e.g. what kind of eBS artifacts need to be version controlled?
2. How to build eBS artifacts and then deploy to a new environment? How to move an eBS application from one environment (DEV) to test environment?
3. How to manage changes?
We have a standard SCM tool called RTC from IBM, which has version control, build and change control functions.
Thanks
JirongPlease do not create duplicate threads -- Software Configuration Management of Oracle eBS

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Version Control for adobe forms

Dear All,
We have a situation where we already go live with version 0 of our adobe form. Now, we have an enhancement to the form i.e.: some new functionalities and new field. Previously we have tried to transport the new changes to the production without any version control and those processes that have been already started prior to the new changes encounter error when the user continues the process.
I am wondering how do the version control works and any documentation on how to configure it?
Thanks in advance
Regards,
Bryan

Hi Brian,
Here is some information that I found in the IMG on Create ISR Scenario...
Create ISR Scenario
Use
In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.
In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.
ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.
Note
If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.
This is from the Create Form Scenario documentation...
Create version
Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.
You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.
If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.
Hope this helps...
Cheers,
Kevin

Version Control and Dreamweaver CS5.5

Hello-
I want to install version control on both a shared Bluehost server and a dedicated Hostgator server, sites on both I manage with DW CS5.5.
I've read the help articles but it seems they are targeted at installing svn on your local machine, and I want to install it on my remote servers. I realize this is not a Dreamweaver specific question but wondered if there are any obvious paths to this someone might know of.
I do have svn installed on my bluehost server, but haven't yet been able to figure out how to set up a repository there yet. So when I do
svn --version, it shows me all the version info, indicating it was successfully installed, but I haven't been able to set up a repo yet, via ssh. Can this be done in DW or do I have to get it done via SSH on the server first, then set the path to it in the version control tab of the site set up/management tabs AFTER I accomplish setting it up via SSH on the server first?
Thanks very much in advance...
Laura

So here is where I am with it if you have any suggestions I'd appreciate it:
Hostgator tech support helped me get it back to 1.7.5 (no explanation for how it became 1.6 after I installed and verified 1.7.5, odd)
So here was the interaction but I'm still (stupidly I'm sure) stuck:
From tech support:
You *should* be able to communicate with a SVN 1.7.5 server with a svn 1.6 client without issue.
1) When I run svn --version on your , I show version 1.7.5:
[~]# svn --version
svn, version 1.7.5 (r1336830)
compiled Jun 28 2012, 22:37:11
Yes, the user and password for SVN must be set up within svn. Here is a brief outline of setting up a repository.:
First, create the repository:
svnadmin create ~/myrepository
Edit the configuration file for the newly created reposiroty:
nano ~/myrepository/conf/svnserve.conf
Add the following, presuming you want no anonymouse access and write access for authenticated users:
anon-access = none
auth-access = write
password-db = passwd
Open up the passwd file to create it and ready it for editing:
nano ~/myrepository/conf/passwd
Add your password to it like so:
exampleuser = examplepassword
Import your project to it (if any):
svn import /path to your project/myD5project file:///home/juicyserveradmin/myrepository
Start and daemonize the svn server:
svnserve -d
You should now be able to check out your project from DreamWeaver.
4) SVN typically runs on port 3690. Port 2223 is your SSH port. If DreamWeaver allows your to connect to SVN via SSH, then it will be over port 2223 - in this case you would need ot provide your SSH login credentials.
What I'm still stuck on:
I added the repo as he said, ~/repos
I added two users/passwords to the file (not sure how to confirm I did it right though)
I'm stuck on this step:
svn import /path to your project/myD5project file:///home/juicyserveradmin/myrepository
Here is how it's set up now, if you could help me think through what makes sense I'd really appreciate it.
I've got my live site, example.com
We've been doing all of our development work live on the front end which is of course a terrible idea and constantly causes issues where problems are showing up live.
So i set up dev.example.com which is within the main example.com directory called /dev and as a subdomain.
I also set up /dev2 the same way.
The only difference is that /dev is set on cron to have all of example.com main files copy to it once a day, so it stays more or less in sync.
/dev2 is not being synced that way.
My idea was then I've got two dev folders we can do work in, one that syncs and one that stays static.
I want to have svn working for all 3....the live site, the /dev and the /dev2.
So would I need to create repos in each of those 3? Or just one repo? file names would be the same in all three so it seems like there would need to be repolive, repodev , repodev2 or something like that?
I want the same user/pass at the moment for all 3.
Then I'm back to not quite sure how to set that up in DW, and, what to import into each if that's the best way to do it?
Also I was confused about the path command above.
In the scenario above can you create that path for me to see exactly how I should paste it in if I do three repos, if, and please tell me, if doing it that way even makes sense?
For DW server settings, is the sever address the IP address of my dedicated server?
And I'm not sure what to put for Repository Path given the questions above.
Thanks again for your patience and help...
Also:
I see from this link
http://civicactions.com/blog/2010/may/25/how_set_svn_repository_7_simple_steps
That I would maybe want to set up different directories within the /repos directory for the three versions of the site, live, dev and dev2?
I'm still confused about the format of the path.
Would it be like
svn mkdir file:///nameofmyhomedir/repos/live
svn mkdir file:///nameofmyhomedir/repos/dev
svn mkdir file:///nameofmyhomedir/repos/dev2
Where I want the directories to be named live,dev and dev2?
Can you correct that path for me if that's not quite right?
I do see in DW now for my local site that I've got + next to all the files after setting up the Version Control server, but, because I don't have the path to the repo right I guess or the server address right...it says it can't connect:
Access: Subversion
Protocol: SVN
Server Address: My IP address?
Repository Path: Not sure if I did ~/repos what the full path to it on my server is?
Server Port: 3690
username/pass what I set up in the file according to his directions.
Can you steer me towards dialing this in right pretty please?
Thanks in advance for any help.

Version control practices

I looking for information on how others employ version control on all the
various portal resources. Versioning custom development around remote
services and the like is easily handled through the IDE or normal version
control practices. What I am wonding about is how people version admin
objects, kd items, and other resources managed in the portal.
Any info would be appreciated.
Thanks.

In our current J2EE environment an ant script builds a war and copies it to a staging file server, then there is a java app that deploys the war to weblogic with the weblogic scripting extensions. We are thinking of modifying this app to also deploy the PTE files that any portlets in the war depend on. Day one a jsp portlet requires a single session preference. The next day it needs a login token to use the PRC. How do you coordinate this? For us it will probably be done with custom scripting.
A developer modifies the jsp and checks that in along with a revised remote service pte file which has the new settings. The ant script will then build the war and package it into a tar with the pte file and finally drop it on the staging server. From there our existing java deployment web app can extract the tar, deploy the war and run a migration import on ALUI. Hopefully all this can happen in a transactional context so that that if the import fails, the new portlet is not deployed.
I don't want to run into the case where a new portlet is out on the QA box and the portlet service is misconfigured and isn't supplying the correct headers to the portlet tier.

SD quotation managed through version control

Similar Messages

Maybe you are looking for