Anybody knows about audit feature of the Worklight Server 6.2 Administration console?
What are the audit details stored by worklight server?
Where is it stored?
How long the data will be stored?
How to purge these data?
Again could not find any relevant information on info center.
This question is about the Audit log available to download at the footer in Worklight Console.
What are the audit details stored by Worklight Server?
The audit log contains every action done in the Worklight console and that was written to the database. This includes: the action timestamp, action type, action status, user role, artifact type.
Where is it stored?
In the Worklight Server database.
By default, the Worklight Development Server uses a file-based database (HSQL). You cannot access this file while the server is running (when not running, the file can be accessed by some tools. You can google for them; not especially recommended to touch it).
How long the data will be stored?
The data is stored for as long as the database is not cleared.
How to purge these data?
Manually delete the your_workspace\WorklightServerConfig folder.
From the documentation:
Audit log for administration operations
Worklight Console stores an audit log for login, logout, and for all administration operations, such as deploying apps or adapters or locking apps.
The audit log can be disabled by setting the JNDI property ibm.worklight.admin.audit on the web application of the Worklight Administration service (worklightadmin.war) to false.
When the audit log is enabled, you can download it from Worklight Console by clicking the Audit log link in the footer of the page.
Related
Can i make some changes in MFP Admin console like changing the user >permissions, roles and so on ..., using IBM MobileFirst v7.1
The source for the console is available in the admin .war file you have deployed to your application server. However note that this operation is not supported by IBM. If you encounter any errors, you're on your own.
We are developing a small application that needs to have a local database installed on each users computer that will then sync up to the main database, via web services etc...
Anyways when we deploy the application on the users computer we want to use clickonce deployment. Now I have used this before but not attaching a SQL Server database. I know you can go to prerequisites in clickonce properties and click SQL Server Express.
Now the question is, when you have created your .mdf database file including stored procedures and all - how do you get this attached and setup automatically in the local database that is just installed through clickonce?
Also once this is finished in the future we may want to run updates to the database on the clients machines. We would like to use clickonce for this to publish database updates. Obviously we don't want to overwrite the database and just publish the latest updates based on if they already have the database or not and what version they have.
How could this be achieved using clickonce? Thanks
I'm trying to deploy a MobileFirst server to a local Liberty server configured with an LDAP server.
When I try and deploy my server configuration the admin task fails due to lack of attributes for connecting to Liberty.
BUILD FAILED
C:\Users\Administrator\Documents\IBM MobileFirst Platform Server Data\Server Configuration Tool\Configuration_Hello MobileFirst Server\Hello MobileFirst Server.xml:88: The element <installWorklightAdmin>, <jmx libertyAdminUser=".." libertyAdminPassword="..."/> is missing. A default user cannot be created for this server.
I have tried updating the server configuration file manually before deploying, but the server configuration tool is just saving over the changes.
How can I resolve this problem from within the Server Configuration Tool?
The Server Configuration Tool in MFP 7.0 can't be used to make an install on a Liberty server that is configured with LDAP.
In the simplified install process of the Server Configuration Tool, it automatically creates a Liberty Administrator in a basic registry and this is not possible if Liberty is configured with LDAP.
If you don't want to create ant files manually, you can:
Export the ant files that you created with the Server Configuration Tool (Menu File/Export Configuration as Ant files...)
Edit them so that they have the right attributes in the jmx element (you need to provide the login of password of a user that will be used as Liberty Administrator and that the apps will use to perform JMX calls)
Run the ant files as described here
For the admin: https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.installconfig.doc/install_config/r_wlconsole_ant_tasks.html
For the runtime: https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.deploy.doc/devref/c_project_war_file_ant_tasks.html
You may encrypt the password of the JMX user with the Liberty securityUtility program (in LibertyInstallDir/bin)
I am a total newbie in SQL/SQL server stuff, and I am using SSRS to make a new reporting server/service and upload some .rdl files to it
I have a reporting server on a machine, which has a lot of reports and data sources uploaded to it's database.
I created a new reporting server with a fresh database on another machine, and what I want to do is to copy the old database content to the fresh one (the reports and the datasources..etc)
I have no copy of the individual reports to upload them to the new server using localhost/reports
is there's a fast solution to what i am having? please do it in detail because I never worked with SQL before.
Different ways to do this:
Report Server Databases
Use the detach/attach or backup/restore instructions here. Both of these methods require a backup of encryption keys on the existing instance, which are then restored to the new report server instance. Instructions on backup/restore of encryption keys here. Migrating the ReportServer and ReportServerTempdb databases is the easiest way to ensure all content is available on the new server.
Report Object Scripting
Reporting Services Scripter is an older (but still working with SSRS 2008R2, not sure about 2012) tool that can be used to transfer objects (folders, shared data sources, shared data sets, reports, etc) between report servers. Good choice if you want to pick and choose what is migrated.
If you are receiving an error regarding unsupported scale-out deployment, this means you are running Standard edition and need to remove the old report server entry from the database in the new location. It can be done using Reporting Services Configuration Manager, or by using rskeymgmt at command line.
Reporting Services Configuration Manager
Open Reporting Services Configuration Manager and connect to the new report server instance.
Click on Scale-out Deployment to view registered report servers.
Select the old report server instance and click the Remove Server button.
Command line and rskeymgmt
Browse to the Tools\Binn folder of your SQL Server client installation.
Run the following to list registered report servers
rskeymgmt -l -i
Using the installation ID (GUID) of the old report server, remove it
rskeymgmt -r -i
More info on scale-out deployments and rskeymgmt here.
To migrate Reporting Services, use migration manual from MSDN (https://msdn.microsoft.com/en-us/library/ms143724(v=sql.120).aspx). If you encounter "the feature: scale-out deployment is not supported in this edition of reporting services. (rsoperation notsupported)" error, go to ReportServer database and remove the old encryption key from table dbo.Keys.
I have an ASP.NET MVC 4 web application. I need to be able to log controller logic.
Now i have created a Windows Azure project and added a web role and added this web application as a web-role.
How can I log when the the website is running as a cloud service?
Windows Azure Diagnostics enables you to collect diagnostic data from a worker role or web role running in Windows Azure.
The Windows Azure diagnostic monitor runs in Windows Azure and in the compute emulator to collect diagnostic data for a role instance. Log data will be periodically saved to a storage account where it can be examined.
For step-by-step instructions refer to Enabling Diagnostics in Windows Azure.
For additional information refer to Collect Logging Data by Using Windows Azure Diagnostics, Diagnostics and Debugging in Windows Azure and Windows Azure Diagnostics–From the Ground Up.
For advanced dianostic management features check Azure Diagnostics Manager (free trial available).