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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
EDASERVE Logon
 Login/Join
 
Tomsweb
Master
posted
Just last week we upgraded from WF 7.6.1 to 7.6.5. As per most upgrades, there can be issues to iron out...
On friday and today we have experienced this error. We have opened a case with IBI on this, but I wondered if anyone else has experienced this in their environment.

[
Is any one experiencing problems trying to look at tables in EDASERVE. I am getting a log on screen, which prevents me from seeing the table and formats(see below).
]

Thanks! Roll Eyes


Tomsweb
WebFOCUS 8.1.05M, 8.2.x
APP Studio, Developer Studio, InfoAssist, Dashboards, charts & reports
Apache Tomcat/8.0.36
 
Posts: 573 | Location: Baltimore, MD | Registered: July 06, 2006Report This Post
GinnyJakes
Expert
posted Hide Post
Tom,

It sounds like you have OPSYS security set on your reporting server where possibly you didn't before

or

In your previous installation, there were default credentials stored in the WebFOCUS client so that you could connect to a secured reporting server without logging on.

To check the former, use the web console, servername:8121, and look at Workspace/Access Control/Security Mode.

For the latter, look at the client console, servername/ibi_apps/console/webfocusconsole.jsp, Reporting Servers/Remote Services and look at the profile for EDASERVE. You can use IBI_REPORT_USER and IBI_REPORT_PASS to set the default credentials.

If you are not an admin, you can show this to an admin and have them verify the configuration.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
Tomsweb
Master
posted Hide Post
Thanks, Ginny. I will pass it on. Smiler


Tomsweb
WebFOCUS 8.1.05M, 8.2.x
APP Studio, Developer Studio, InfoAssist, Dashboards, charts & reports
Apache Tomcat/8.0.36
 
Posts: 573 | Location: Baltimore, MD | Registered: July 06, 2006Report This Post
Tomsweb
Master
posted Hide Post
Ginny,

Here is the reply I received from our Sys Admin.

"We don't use OPSYS - we use LDAP security. We have also set IBI_REPORT_USER and IBI_REPORT_PASS in the custom settings. (I double checked that both settings were still in place.) One note about your post just for future reference - we actually upgraded from 7.1.3 to 7.6.6 (not 7.6.1 to 7.6.6)"

Any ideas?

Thanks,


Tomsweb
WebFOCUS 8.1.05M, 8.2.x
APP Studio, Developer Studio, InfoAssist, Dashboards, charts & reports
Apache Tomcat/8.0.36
 
Posts: 573 | Location: Baltimore, MD | Registered: July 06, 2006Report This Post
Darin Lee
Virtuoso
posted Hide Post
Are you sure that the LDAP security is working properly? There is a test function in the server console. You can also see the security setting in the log files where ther server startup occurs. There is an additional setting EDAEXTSEC=ON that must be present for LDAP to work properly. Also (to double check the obvious) the IBI_REPORT_USER parm value should be a valid user for LDAP.


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders