How to manage a debug deployment in a production environment

One of the advantages of the Base Deployment is that the test station is locked down, for example operators cannot open and edit LabVIEW VIs. AFAIK a debug test station is wide open like a development machine, except for TestStand User Manager restrictions.
How can I have a test station that is locked down, and then open it up for debug as needed? Dual booting the computer seems like a solution. Or maybe just have an open debug station and trust the trained operators to not mess with it. Can anyone share their solutions? Thanks.
cc

Hi,
You make a good point about TestStand editing. That really leaves only the issue of LabVIEW development environment allowing uncontrolled editing of VIs.
Personally I'm good debugging with base deployment, however I have worked with many companies who want full debug capability.
Here’s my refined questions,
1. Can I create one deployment image that works both with TestStand Base Deployment license and Debug license? Do I have to add anything special other than the Sequence Editor to get TestStand to run as debug?
2. If I install LabVIEW development environment onto the same machine as the deployment image in 1, will I be able to step into and edit LabVIEW VIs? (As long as I set the LabVIEW adapter to development.)
Then the debug station would be locked down with TestStand User Manager and LabVIEW adapter set to runtime. And it would have the same TestStand and LabVIEW and support files as all the base deployment machines. Does that sound logical to you? Thanks
cc

Similar Messages

Create a new portlet in Deployed Portal in production environment

are there any ways to import or create a new portlet in Deployed Portal in production environment?
Edited by: user8322798 on May 1, 2011 7:26 AM

This can done via WSRP proxy portlets and streaming desktops. First, you'll need to have a WSRP producer setup somewhere. This could be another WLP webapp with portlets, or another server altogether. Or, you can use the JSR 286 WSRP import tool from within the Portal Administration Console (I think it's under Services | WSRP | Import Tool) -- this will allow you upload .war(s) of JSR 168 or 286 portlets, which will be turned into WSRP producer(s).
Then, you can use the Portal Administration Console to register a WSRP Producer, and then add portlets from the producer to your desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14235/chap_fed_books_pages.htm#FPGWP690). Additionally, once the producer has been registered in Portal Adminstration Console, an adminstrator user can use the Dynamic Visitor Tools from within the streaming desktop itself to add wsrp proxy portlets to the desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14243/dvt.htm#PDGWP691).
It is not possible to add new local .portlet files to a deployed application in production mode. This requires adding the file artifacts to the .ear/.war and redeploy the application.
Greg

SAP ME SDK - WebServices Deployment to a Production Environment

Hello all,
I was wondering if anyone else out there was having the same problems that I was having while developing a Web Service through the SDK Eclipse environment?
I followed the tutorials within the "SDK Training.pdf";; that came with taking the SDK class and was able to create the Web Service (page 264) without any problems on my development server. Deployed through the Eclipse environment. However when performing an actual build to be deployed on a Production server the Web Services were not carried over cleanly.
I did manage to get it all working after a lot of trial and error as well as creating a new directory structure to place the wsdl files in, which ironically is the same directory structure on the development server (a good thing that I have a D: on both the dev and prod server). Not a very pretty situation. It should come all nice and neat for a production build similar to deploying the SAPME.sca file.
I was just wondering if anyone else in the community had the same problems that I did?
Also, was wondering if there was any future enhancements to the SDK to make this process more streamlined?
Thanks,
Mike

Hi Troy,
I have already done exactly as you suggested, which is also documented in the training information for a production build. I am able to get all of my custom code/activities/jsp pages working within ME without any issues. However, I was not able to get to my web services through the JSP pages that I wrote. Following the example in the Training Documentation given to us from the SAP Trainer.
To get this to work I had to take the <vendor>Web.sda.ear file and move that to my Production server to install and run. That is the part that I was dicussing it not being a clean install.
I will take another look at the SDK Implementation Guide, however the Training Doc has examples, which many people, including myself learn best from.
My question was really has anyone else in the community run into this same issue? As well as, are there any improvements?
You have answered the second question with regards to ME 6.1. I appreciate and thank you for that.
I am looking forward to the ME 6.1 ramp up and release.
Thanks,
Mike

How to download run time ABAP dump in production environment

Hello,
I am getting run time ABAP dump in production environment. Please guide me onHow to download run time ABAP dump in production environment?
Also, please tell me how best can analyze that dump. Like there are tools like gdb, purify etc. to analyze problems in other languages.
Regards,
Sameer.

Hi,
Go to ST22, and Double click on the error line, It will show you the detailed analysis.
See the section How to correct the error for details on error correction and the instructions to download the log( you can download in the format you want - HTML would be a nice option).
And there are no tools to analyze errors but ST22 has a large data regarding the location of the error, the reason and the source code which caused. So you need to use the debugger to reproduce the error and check the source code,
Regards
Karthik D

How To Manage Exchange in Office 365 AD Sync Environment

Pisces225x wrote:
So, for example, right now I have no way to manage distribution lists beyond adding and removing members? For example, I can't edit the default configuration on a distribution list to allow it to accept external messages.
You can do that in EAC.
https://technet.microsoft.com/library/bb124513.aspx#deliverymanagement

I implemented AD Sync in our O365 environment a while back. After this I continued to manage Exchange entirely in the O365 admin console. Recently I had a reason to go ahead and extend the AD Schema to include the Exchange attributes. Now the majority of management needs to be done in our local AD. I'm fine with this. My issues are the following:- I initially created and managed all distribution lists in the O365 EAC. They have never existed as objects in our local AD and I have never had on prem Exchange. Is there a way to sync the lists back to our AD? I don't see that they exist anywhere as objects and hence I can't manage them.- Is there anything to be gained by installing Exchange on a local server, even if only to gain access to a local EAC? I'm not interested in trying to set up any kind of hybrid environment.I know someone else...
This topic first appeared in the Spiceworks Community

Error Deploying Mapping in Production Environment

All,
I have 3 locations: APPS (source,) STAGING (target,) and SALES_DM (target.)
I am trying to deploy a mapping, via deployment manager, to my PRODUCTION runtime environment. The mapping is part of the STAGING schema, has two source tables from the STAGING schema, and after a simple join performs a lookup to APPS, STAGING, and SALES_DM tables, and eventually loads to another table in the STAGING schema after various transformations (it is a complicated mapping that deals with invoices and orders for a Sales DataMart.)
I have deployed and executed this exact mapping in several test instances. I have also deployed and executed many other mappings in the STAGING schema in PRODUCTION. However, I am encountering an error when I try to deploy this specific mapping: PL/SQL: ORA-00942: table or view does not exist.
This error occurs 4 times (there are 4 warnings with different line numbers.) When I go to the lines in the code (using the line number + line number where the / in the main is found trick) the same STAGING table is in every line. Since this mapping executes as STAGING, it is a little weird that the error message is indicating a permission issue with one of its own tables. Is it possible that this specific table is not the real issue?
Here is the main difference I can see between my PROD and TEST environments. In TEST, the APPS location is registered to APPS, where as in PROD it is registered to STAGING. However, in both instances I am positive that the appropriate grants on source APPS tables have been given to STAGING, and in PROD I have created synonyms for the source APPS tables in STAGING (i.e. for the Applications order headers table I have created the synonym oe_order_headers_all.)
I have had to do a lot of troubleshooting with apparent permission issues before, but am completely baffled on this one.
Any thoughts or ideas are much appreciated.
Regards,
Ryan

Hello,
Since you have one PRODUCTION runtime, the targets STAGING and SALES_DM runs in the same instance. If you register both locations properly in Deployment Manager, OWB will figure out that you deploy to the same instance and will use schema.table naming in your mapping PL/SQL package for efficiency, not any DB link.
Because of this you/SALES_DM must (manually) GRANT SELECT on SALES_DM.lookup_table TO STAGING in the PRODUCTION instance (you must grant directly to the STAGING user, not to any role held by the user).
I presume you have checked that your lookup tables have been deployed, as reminded by another forum participant earlier...
Regards, Hans Henrik

In Oracle How to migrate .Rdf file from Development to Production Environ..

Hi,
Please explain me step by step how to migrate report(.Rdf) file from development instance to production instance ASAP.
Thanks & Regards,
Raj

Rai,
Please ask your questions in the EBS section, since they are not PeopleSoft related.
Regards,
Hakan

Deploying a new ODI environment

Hi all,
I need to create a new ODI Dev environment.
I have ever developed several projects that I want to retrieve in my new environment.
So first I would like to import all my connections (physical and logical schema) from my old Master repository to my new one.
Could you please give me tips to do this ? What's the easier way, dump ? mimport.bat ? or another way ?
Moreover my architects team ask me if it can be done without client interaction (only API and scripts). Does anyone know a solution without client ?
To import all my dev's objects I think that Work repository import can be done or object by object import with ODI.
Like you can see I'm a bit confused in this subject, if someone know best practices or Oracle's notes.
Thanks in advance.
Brice

Did you go through this on metalink : How To Export Developments And Create An ODI Production Environment? [ID 423815.1]

How to manage one wsp and dll for multiple clients in farm environment

1. There is a product which is developed using C sharp , jquery,CSS and sharepoint object models which have been packaged into .wsp file. Whenever we introduce new functionality to the product we used to branch the
previous code as a version , say Version 1.0 and new functionality of the product will in another solution. This is how we are managing the code in TFS as versions. Each newer version will have new functionalities. We do not give latest functionality for all
the clients. Each client is having its own version of functionality. Technically in order to access the functionality, the wsp solution should be present in the solution repository which is available in SharePoint central administrator site. This solution
will be deployed on the client’s site. We are following the above process in SharePoint standalone installation where we used to purchase dedicated server per client and installed sql, SharePoint foundation 2010 as standalone installation and adding the client
related version of the code to the solution repository. Later host on the site which is created for that client purpose. This process is same for all the clients where we purchase individual server for each client .
Now we want to host our product in farm environment of sharepoint foundation 2010 where we are going to try 3 level architecture.
• SQL Server-In this sever we are going to install sql server 2008R2 standard edition. Which should serve the database service for all the web applications/sitecollections which we are going to create in Web front end server.
• Application server- In this server we are going to install the sharepoint as farm and will install search server express for serving search functionality for our product
• Web front end server- In this server we are going to add this server to Sharepoint farm which we have created in application server. Here we are going to create web applications and site collections for all the clients.
In this scenario how to manage multiple versions of same wsp solution?
Another major issue w.r.t the architecture of the product and new approach for client deployment as follow.We have CSS, jquery files for serving the functionality.These files have been mapped to 14 hive folder.If any changes we do one of the jquery file or
css file which is meant for latest version and not for old version, then how to manage this new functionality for that particular css or jquery file in 14 hive folder, since there is only one 14 hive folder. What is the best practice to make this happen? Another
thing is, how to manage dll files for individual client?

It sounds like you have a farm scoped solution at work. In that case you can only have a single instance of it per farm, you'd have to branch each version so they appear to be seperate solutions entirely (thus ruining your clients upgrade process).
Bluntly i don't think a single farm can manage all your user environments.

How to get the debug sqlserver procedure calling from powerbuilder

How to get sqlserver debug while calling the procedure from PowerBuilder. Please can you help
Many Thanks
Pol

You are better off doing this through the native SQL server tools. You can debug your PB code to find the variables being sent to the stored proc (if any) from PB and then use them in SQL Server Management Studio or similar.

2009 SP1 Debug Deployment Only

I've install LabVIEW 2009 SP1 and it works fine but it indicates "Licensed for Debug Deployment only" on the opening screen. We use the Volume License Manager and it correctly checks out a Development License which is correct for me.
Is this something I should be concerned about? It doesn't seem to be constrained in any way, i.e. I can build executables.

Here they are. I'm "DC10020"
Attachments:
VLM_Screenshot.jpg ‏511 KB
NILM_Screenshot.jpg ‏227 KB

Understanding TestStand Debug Deployment License

After reading the License Agreement and the TestStand Help section on licenses I still would like an explanation as to exactly what the license does and does not allow. My understanding is with a TestStand Debug/Deployment license I can install TestStand on a machine, let's call it the development machine, and also install TestStand on another machine, my production machine. The development machine is where I would develop applications to deploy onto my production machine. The production machine is where I would actually test my products. The production machine can also be used as a platform to debug my deployed applications. If this is true then can I develop any additional tests on the production machine, e.g. I found a problem in the sequence so I need to add a new sequence to correct the error? Or I found a problem with a LabVIEW VI and I need to create a new VI to correct it. Can I develop VI's and sequences on the production machine or do I need to develop on the development machine transfer the files over to the production machine and hope it works (this type of process could prove to be very time consuming and tedious)?

Thanks for the info. Now what about LabVIEW. Here are some options I'm considering:
1. Run a LabVIEW Runtime Engine on the production machine and a FDS of LabVIEW on the development machine. In turn run a TestStand Deployment license on the production machine. This seems the most cost effective method. The problem I'm having is some VI's are developed in LabVIEW 6i, 7.0, and 7.1 and the LabVIEW 7.0 RT Engine does not work with TestStand 3.1. It seems only the LabVIEW 7.1 RT Engine will work with TestStand 3.1. But I don't have a LabVIEW 7.1 development license (not sure how the 7.1 VI's came to be, before my time). I've also thought of using standalone LabVIEW applications but the only license I have for Application Builder is from LabVIEW 6i PDS from the Developer's Suite. If TestStand 3.1 is suppose to work with any LabVIEW RT engine then I'm doing something wrong.
2. Run a LabVIEW Development/Deployment license with a TestStand Development/Deployment license. This is the most expensive method but the easiest to implement.
3. Run a LabVIEW FDS and a TestStand Deployment license on the production machine.
A finally question, does NI make available a TestStand Run-time Engine that is available as a free download, similar to the LabVIEW Run-Time Engine?

Compare 'debug deployment' and 'development'

What are the differences between the debug deployment and the development version? I read the short text about the debug deployment version but this isn't enough for me.
Is it possible to do 'skip' and 'run selected steps'?
Or is there somewhere a nice table which compares the three versions, base debug and development?
Cheers Frank
Solved!
Go to Solution.

Hey Frank,
Here's a link: http://www.ni.com/teststand/depcompare.htm
However that still isn't as satisfying as I would like either so let me see if I can explain.
The development and the debug deployment are exactly the same except that you are ONLY supposed to use the debug version to debug your deployed sequences. Basically it allows you to have a sequence editor on the deployment machine for the sole purpose of debugging. That's how I understand it anyway. You can skip and run selected steps with the debug version.
Hope that helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

How many application we can deploy to the integerated weblogic server

Hi ,
How many applications we can deploy to the weblogic server a very small applications containing 5-6 jspx page

827028 wrote:
What is the difference between integerated weblogic and stand alone WebLogic Server?
I think both of them are same?
In short:
No,a stand alone server runs a it's own process and can be started as a service running in the background.
The integrated server needs jdev and is optimized for debugging.
Timo

Configuration manager 2012 Client Deployment settings.

GPO to push config mgr client
i have added The Configuration Manager templates in GPO
Under Configure Configuration manager 2012 Client Deployment settings.
I have enabled it and what is the command line here
CCMSetup.exe SMSSITECODE=COD FSP=sccm.mydomain.com MP=sccm.mydomain.com
or
SMSSITECODE=COD FSP=sccm.mydomain.com MP=sccm.mydomain.com
or
CCMSetup.exe /MP:sccm.mydomain.com /logon SMSSITECODE=COD SMSSLP=sccm.mydomain.com FSP=sccm.mydomain.com
or
/MP:sccm.mydomain.com /logon SMSSITECODE=COD SMSSLP=sccm.mydomain.com FSP=sccm.mydomain.com

You can use the following:
CCMSetup.exe
SMSSITECODE=COD FSP=sccm.mydomain.com MP=sccm.mydomain.com
http://prajwaldesai.com/deploying-configuration-manager-2012-r2-clients-using-group-policy/
http://methmal132.wordpress.com/2013/02/13/how-to-push-the-sccm-agent-via-gpo/
Regards, Ibrahim Hamdy

How to manage a debug deployment in a production environment

Similar Messages

Maybe you are looking for