I am using IBM Worklight 6 and for auditing purposes would like to know if I it is possible to log the details of tasks performed on the Worklight Console, i.e. log the details when deploying new version of app/adapter?
Regards,
Tom
Worklight, or more specifically, the application server that Worklight Server is deployed to (WAS, WAS Liberty profile, Tomcat), does not have the ability to filter logs into seperate files, for example for the purpose you have mentioned.
What you might be able to do is take the server log, and create your own manual filtering (by script, of course). What you will need to do is to find the prefix for each action done and filter using it.
In Eclipse (or your production environment) open server.xml > Logging and change the Console log level from Audit (default) to Info.
This in turn will produce the following log lines in the sever log:
[INFO ] FWLSE0084I: Adapter 'aaa' was deployed successfully. [project test]
In your script you can now filter for FWLSE0084I for adapters and similar prefixes for other actions, likely. I am not sure if all Worklight Console actions have prefixes, but if they are ones that require a connection to the server, then likely that they do.
http://i.stack.imgur.com/sZ0fj.png
Related
If we need to perform queries in pentaho data integration (IDE), we need to add manually the datasource in simple-jdin/jdbc.properties
MyDatabase/type=javax.sql.DataSource
MyDatabase/driver=org.hsqldb.jdbcDriver
MyDatabase/url=jdbc:hsqldb:hsql://localhost/sampledata
MyDatabase/user=pentaho_admin
MyDatabase/password=password
This works as expected in the ide known as pentaho data integration, spoon or kettle.
But, the same in pentaho server 8.2 does not works.
Steps to reproduce the error
deploy or upload the transformation(.ktr) in the pentaho-server 8.2
add manually the datasource in the server /../pentaho-server/pentaho-solutions/system/simple-jndi/jdbc.properties
executed the transformation using pentaho server web console : run in background or schedule options
error: datasource not found
Alternative
Create the datasource manually using web console of pentaho server instead of manually modification of file : /../pentaho-server/pentaho-solutions/system/simple-jndi/jdbc.properties
Question
simple-jndi/jdbc.properties works in server or is just for development purposes (pdi)?
are the settings available in jdbc.properties file on server can you verify the same by referring to the pentaho data integrator > simple-jndi folder.
also are you able to connect to the database from the server may be using a database client to confirm.
NOTE:whenever you work with databases make sure you relevant library files to connect to the respective database.
From my personal experience, I was not able to make the server pick JNDI connection definitions from the simple-jndi/jdbc.properties file when the Pentaho Server was running with Tomcat.
I was only able to use JNDI on the Pentaho Server by defining JNDI Datasources in the Tomcat configuration files.
After installing and configuring MobileFirst 8 on WebSphere Application Server 8.5.5.10, RedHat Linux 7.3, I am getting error
FWLSE3030E: The runtime "mfp" does not exist in the MobileFirst administration database. The database may be corrupted.
I am using WebSphere SDK 1.7 with FP40
I have checked the Database, and all tables are present.
In the SystemOut.log, I am getting exceptions and it is as below:
com.ibm.worklight.admin.common.util.exceptions.SystemException: FWLSE3002E: The resource is not found.
SystemOut.log
Edit1: I have installed MobileFirst 8 using Command line, and configured it using Ant task.
Edit2: WAS Full profile deployed applications.
The symptom you're seeing seems like an open issue that is being tracked as APAR PI71317. Please open a PMR and mention this APAR number; we can give you a test fix to try to help us confirm that it is indeed this issue.
first: go to the WAS ND JDBC data sources section and choose the MFP data source and press the "test connection" button.
look carefully at the DSN definition and make sure you can browse that same DB with other tool and ensure the schema and tables exist.
bare in mind: in WAS ND there should be two entries : one for runtime DB and one for MFP admin DB.
I am trying to deploy the MobileFirst Admin Operational console using Server Configuration Tool. Started the configuration tool as root user. Create a configuration and saved the xml. Pressed the "Deploy" button. Its failed with JVM terminated Exit code -1 error.
MobileFirst Server Version 7.1.0.0-MFPF-Server-IF201510051721
WebSphere 8.5.5.7
Installation Manager JRE:jre_7.0.7001.20140909_1712
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
This is not a solution to the JVM crash you experiment, but a workaround to enable to be able to add the runtime (I understand from the above description that the crash happens after the Server Configuration Tool saved the configuration and deployed it).
Go to (homeDir)/.mobilefirst_platform_server/server-configuration-tool. You should find a directory named after your configuration. In that directory, you should find a file named (ConfigName).xml. Copy this file as (ConfigName).lastdeployed (ie same name as the xml file but change the suffix). The Server Configuration Tool would have created this file after deployment completion (and uses it for later operations such as uninstall) and it uses it as an indicator that the configuration is deployed.
"Install and configure" radio button is disabled for me when installing Reportin Services. Can anybody explain why?
P.S. Using SQL Server 2012, Standard Edition.
The behaviour is explained in Reporting Services Configuration Options (SSRS), though it's really impossible to tell what the specific issue is in your case.
From the article:
Install and configure Installs a report server instance in Native Mode
using the default values for the report server databases, service
account, and URL reservations. When you choose this option, the report
server instance is ready to use when Setup is finished. Setup creates
the report server database using a local Database Engine instance, and
configures a report server to use default values.
This option is available only if the default values used in a report
server installation are valid for your system. This option is
recommended for developers who want to install all components locally,
and for users who are evaluating the software.
(Emphasis added)
So there is something in your environment that is preventing this option. To investigate, the article suggests:
To view information about the default Settings that Setup uses, or to
find out why the default configuration cannot be installed, click
Details.
It also suggests looking at What is the Default Configuration to help get more details.
You will need to review all this information in your own environment to get your specific issue.
I was deploy pentaho bi server on my running tomcat server ref from here.
Now I want to create JNDI bases datasource so I login through pentaho administration console but in that web page nothing to shows users lists, user role. After googling some times I was found that change console.xml then I was changed my console.xml file as below
<?xml version="1.0" encoding="UTF-8"?>
<console>
<solution-path>/home/pc-name/pentaho-solutions</solution-path>
<war-path>/home/pc-name/apache-tomcat-7.0.47/webapps/pentaho</war-path>
<platform-username>joe</platform-username>
<biserver-status-check-period-millis>30000</biserver-status-check-period-millis>
<homepage-url>http://www.pentaho.com/console_home</homepage-url>
<homepage-timeout-millis>15000</homepage-timeout-millis>
<!-- comma separated list of roles (no spaces) -->
<default-roles>Authenticated</default-roles>
<default-server-dir>biserver-ce</default-server-dir>
</console>
then I was stopped administration console and then again start but still it not shows me any user lists, role lists. After that I hard coded start-pac.sh as below
DIR_REL=`dirname $0`
cd $DIR_REL
DIR=`/home/pc-name/apache-tomcat-7.0.47`
cd -
. "$DIR/set-pentaho-env.sh"
setPentahoEnv "$DIR/../biserver-ce/jre"
but running at start-pac.sh it shows set-pentaho-env.sh not found but in my first steps deploying pentaho bi server on existing tomcat it not mentioned anything about set-pentaho-env.sh where to copy or set. Can any one knows how to solve this problem?
Short answer: Pentaho 5.0 doesn't have an admin console because both user roles and database connections are easily configured in the user console. It seems you just started to deploy your biserver so I suggest you upgrade to the new version and leave admin console behind. Trust me. You will like it.
Long answer: If you still wish to stay with 4.8 for some strange reason:
Don't change anything in Pac-start.bat, revert to the original version before your changes. If you need to change the default URL or port, then
find biserver-ce\tomcat\conf\server.xml
the default for pentaho user console is 8080, and the default admin console port is 8443. Change those to your preference. Once done,
find biserver-ce\tomcat\webapps\pentaho\WEB-INF\web.xml
change here:
<context-param>
<param-name>fully-qualified-server-url</param-name>
<param-value>http://localhost:8080/pentaho/</param-value>
</context-param>
then find the list of trusted Ip's and add additional trusted IP's here (this is somewhere around line 133)
<param-name>TrustedIpAddrs</param-name>
<param-value>127.0.0.1,0\:0\:0\:0\:0\:0\:0\:1(%.+)*$</param-value>
<description>Comma separated list of IP addresses of a trusted hosts.</description>
(Also covered in this article: http://wiki.pentaho.com/display/ServerDoc2x/Setting+up+trust+between+Administration+Console+and+BI+Server)
Make sure when you start the admin console, pentaho biserver is running already. Admin console will not work if the biserver is not running.
Make sure you use the correct JDK, because a wrong java configuration, or wrong java_home_path can also cause admin console to not stand up.
Really, just go with Pentaho 5.0.1.