Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Unchangeable && in edasprof

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Unchangeable && in edasprof
 Login/Join
 
Silver Member
posted
Hello,

I want to be able to copy master files from DEV to PROD without changing anything in them and appears I can do this but I want to stop the users being able to change the && variable values.

Is it possible to set an && variable in edasprof and not allow the user to change it?

Background :
I want to set &&DB and use it in the master file and acx for the SQL Server database name (&&DB.dbo.tablename one database is DEV, one is PROD (both databases within the same SQL Server instance if that makes sense)), database tablenames are the same in DEV and PROD.

I think I will want to use a similar method for the CONNECTION within the acx via a variable from the master file and give the adapters different names in PROD and DEV (again the &&CONN names will be set in edasprof)

Hope this makes sense, if any other suggestions for acheiving the same or better result happy to hear them.

Regards

This message has been edited. Last edited by: FP Mod Chuck,


WF 8201, Windows Server 2012 R2, SQL Server 2014, HTML, PDF, Excel, Powerpoint, Active Report
 
Posts: 34 | Location: All over Europe | Registered: October 23, 2009Report This Post
Virtuoso
posted Hide Post
I wouldn't mix environments honestly. You're opening up a can of worms you'll wish you hadn't in time. I promise. lol


8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
 
Posts: 1113 | Location: USA | Registered: January 27, 2015Report This Post
Virtuoso
posted Hide Post
Otto

A lot of customers will have a separate fex where global amper variables are set and then do a -INCLUDE of that fex in the edasprof. I have seen the use of using them for the CONNECTION and DB but as Cool Guy has cautioned be careful to not mix the environments.


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
 
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005Report This Post
Silver Member
posted Hide Post
Hello,

Thanks for input.

I will try to clarify what I am saying. I am in the situation where we have one SQL Server instance (think this is correct terminology here) and have one database called Dev and one called Prod. As far as I can see when I copy a master file / acx from Dev to Prod (these are separate environments I think you would term them, totally different boxes I believe) then I will have to go into the master file and acx's in Prod (after they have been copied across) and change the reference in the acx to the Database(Prod rather than Dev), just checking if what I am saying looks correct.

Regards


WF 8201, Windows Server 2012 R2, SQL Server 2014, HTML, PDF, Excel, Powerpoint, Active Report
 
Posts: 34 | Location: All over Europe | Registered: October 23, 2009Report This Post
Guru
posted Hide Post
Normally an acx is pointing to a adapter, let's say "datawarehouse". On the reporting server this adapter points to a database. So on your DEV environment to a DEV database, on Prod to a Prod database. If you use the same schema, you can freely copy mas and acx to other environments without any changes.

There is ineed a possibility to set everything in the acx and mas dynamic and populate with &&. You can protect parameters in the client with:
 <SET> variable_name (protect)
but this only works for parameters that are send from the browser.

In your case I would try to keep same schemanames. If you want to have flexibility in the schema, db table, or db type, then use the && parameters and set them in a mfd profile, don't feed them from the client.


Test: WF 8.2
Prod: WF 8.2
DB: Progress, REST, IBM UniVerse/UniData, SQLServer, MySQL, PostgreSQL, Oracle, Greenplum, Athena.
 
Posts: 454 | Location: Europe | Registered: February 05, 2007Report This Post
Silver Member
posted Hide Post
If you use the same Connection Name in the adapter properties in both Dev and Prod (e.g., SERVER_A) then the CONNECTION information in the .acx file won't need to be edited after copying over the .mas and .acx files and there would be no need to set &&DB.


8.8.09 - z/Linux (WF, Report Caster, Report Library).
Iway FFS on MVS (HFS)
 
Posts: 36 | Location: Oklahoma City | Registered: December 05, 2006Report This Post
Silver Member
posted Hide Post
Sounds like a good approach Craig, thanks for your help.

Frans thanks for your advice too, I appreciate it.

I think what has confused me a bit is that I am trying to copy master files to Dev (that are copies of Prod master files, people want to work on changing them and the data structures in the database and testing results).If I just copy a master file from prod to Dev that should work fine using Craigs methodology I think.

But some of the Dev master files should be pointable to Prod data (to save us setting up routines to copy data every day as well). I guess I will set up an adapter in Dev pointing to Prod and change the connection in the acx for those master files. It is probably a no-no to do that some people will say, I thought I might be able to do it with the Database name in our scenario.

I am trying to tie this in with planning how to limit access to end users so they cannot access data they shouldn't so will raise a focal point on that now but for this one thanks for your help, I reckon you have answered my question.

Regards


WF 8201, Windows Server 2012 R2, SQL Server 2014, HTML, PDF, Excel, Powerpoint, Active Report
 
Posts: 34 | Location: All over Europe | Registered: October 23, 2009Report This Post
Master
posted Hide Post
otto,

my advice is to not connect dev to prod. There should never be any reason to do this. It is a security risk for one, not to mention the possibility of run away queries and other issues that arise when developing off of production data.

I don't understand why you would need a routine to copy data to dev. ever. This seems to me to be just a bad design. At that point, you might as well not have a dev environment at all and just work directly in prod. Also something I don't recommend by the way.


Eric Woerle
8.1.05M Gen 913- Reporting Server Unix
8.1.05 Client Unix
Oracle 11.2.0.2
 
Posts: 750 | Location: Warrenville, IL | Registered: January 08, 2013Report This Post
Gold member
posted Hide Post
The question of which WebFocus instances connect to which databases could depend on who is doing the development in your environment. For my first 10+ years in WebFocus we had only one WebFocus instance, so naturally it connected to both development and production databases.

We now have a development WebFocus instance, which is also able to access both development and production databases. This allows us to run reports off of live data in the later stages of the development process, so that users can evaluate the report against live data. The same idea applies during WebFocus upgrades. I wouldn't want it any other way!

In our case, we don't have non-tech people developing reports to cause problems with production database performance. . .


WebFocus 8201m on Windows; App Studio 8201; Procedures: WebFocus with SQL; HTML Parameter Pages & Dashboard; Output: Excel, HTML, & PDF.
 
Posts: 88 | Location: MI | Registered: July 23, 2009Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Unchangeable && in edasprof

Copyright © 1996-2020 Information Builders