Hello everyone. Here I bring a video on how to download libraries for Automation Studio. I hope you have been helpful, here I leave the link of the page: http://www.
Compatible with Windows 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall
Overview of Br.as.symbols.dll
What Is Br.as.symbols.dll?
Br.as.symbols.dll is a type of DLL file associated with Automation Studio developed by Bernecker + Rainer, Industrie-Elektronik Ges.m.b.H. for the Windows Operating System. The latest known version of Br.as.symbols.dll is 1.0, which was produced for Windows 7. This DLL file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'.
What Are DLL Files?
DLL ('dynamic link library') files such as br.as.symbols.dll are small programs, similar to EXE ('executable') files, which allow multiple software programs to share the same functionality (eg. printing).
For example, let's say you are running Windows 7 and editing a document in Microsoft Word. The DLL file that controls printing does not need to load unless it's function is needed - eg. you decide to print your document. When you select 'Print', Microsoft Word calls the printer DLL file, and it is loaded into memory (RAM) at that time. If you want to print a document in another program, Adobe Acrobat for example, that same printer DLL file will be used as well.
Why Do I Have DLL Errors?
Because they are shared files, DLL files exist outside of the software application itself. Although this provides many benefits for software developers, this separation also provides an opportunity for problems to occur.
Quite simply, if Windows cannot properly load your br.as.symbols.dll file, you will encounter an error message. Please see 'Causes of br.as.symbols.dll Errors' below for more information.
When Do DLL Errors Occur?
DLL errors, such as those associated with br.as.symbols.dll, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).
Common Br.as.symbols.dll Error Messages
The most common br.as.symbols.dll errors that can appear on a Windows-based computer are:
'Cannot start Automation Studio. A required component is missing: br.as.symbols.dll. Please install Automation Studio again.'
'This application failed to start because br.as.symbols.dll was not found. Re-installing the application may fix this problem.'
These DLL error messages can appear during program installation, while a br.as.symbols.dll-related software program (eg. Automation Studio) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your br.as.symbols.dll error occurs is a critical piece of information in troubleshooting the problem.
IBM Cognos Proven Practices
Nature of Document: Tip or Technique; Product(s): Event Studio, Cognos Connection; Area of Interest: Upgrade/Migration
Content series:
This content is part # of # in the series: IBM Cognos Proven Practices
This content is part of the series:IBM Cognos Proven Practices
Stay tuned for additional content in this series.
Abstract
In stabilized IBM Cognos environments, deployment of IBM Cognos artifacts from one IBM Cognos environment to another IBM Cognos environment (e.g. development to quality assurance) can be automated to minimize the time and effort involved in the code migration process for the IBM Cognos administrators and to provide flexibility to the IBM Cognos report developers to promote their code.
This approach involves providing a common deployment location in the IBM Cognos Content Manager configuration in the source and target IBM Cognos environments. The export of the IBM Cognos artifacts (Archive file) from the source environment will be placed in this common deployment location and the Import to the target environment will pick the artifacts (Archive File) from the same common deployment location.
Using this approach, the user just needs to run an Event Studio agent in the source IBM Cognos environment for the code to be promoted to the target IBM Cognos environment. The Event Studio agent run by the user in the source environment will perform the “export of IBM Cognos Content” operation and trigger an Event Studio agent in the target IBM Cognos environment by way of the “Trigger.bat” utility. The triggered agent in the target environment will perform the “import of IBM Cognos Content” task. The IBM Cognos administrators and the respective user community will be notified by an email on the status of the code deployment.
A specific agent needs to be designed for each application in such a way that the application specified code is considered for code deployment. Each application architect can run their own Event Studio agent in the source environment for their code to be deployed in the target environment.
The organizations using IBM Cognos 8 BI for reporting have development, quality assurance and production environments where the IBM Cognos artifacts needs to be promoted from one IBM Cognos environment to another IBM Cognos environment based on the requirements.
Components Used
IBM Cognos 8 Configuration
IBM Cognos 8 BI Event Studio
IBM Cognos 8 Framework Manager
Trigger. bat Utility
Database Server
Architecture
The figure depicts a sample environment which uses a common deployment location in the source and target environments to deploy to.
Prerequisites
The following are required in order to make this technique work successfully.
A common location (shared drive) within the network which is accessible from the IBM Cognos content manager.
A mail server configured in the IBM Cognos Instances (source and target).
A database server preferably owned by IBM Cognos administration team.
The following capabilities need to be provided for the application architects to run the Event Studio export tasks in source environment.
Execute permission to the administration tasks secured feature.
Traverse permission to the administration secured function.
Execute and traverse permission to the content administration page.
Automation and Status Updation
The Steps in the Automation approach include:
INITIAL SETUP
Configuring shared drive in IBM Cognos configuration of Content Mangers.
Setting up IBM Cognos Trigger.bat utility
Creating stored procedure to run the trigger
EVENT STUDIO AGENT SETUP
Export deployment strategy (creating Event Studio export agent)
Import deployment strategy (creating Event Studio import agent)
Configuring Shared Drive in IBM Cognos Configuration of Content Managers
The “Deployment files location” of Environment properties in IBM Cognos Configuration of both the environments (source and target) is modified to a shared location. After modification IBM Cognos Services are restarted.
This shared location should be in the same network of the Content Manager servers in environments and the service account running the IBM Cognos Service should have access permissions to this shared location.
If the IBM Cognos environments are configured with multiple Content Managers, then the “Deployment files location” needs to be modified in each of the IBM Cognos Configurations for each of the Content Manager servers.
SETTING UP IBM COGNOS TRIGGER.BAT UTILITY
The IBM Cognos utility called Trigger.bat is required for this process. This utility is used to trigger an Event from a remote location (e.g. a database server) where a set of IBM Cognos Jar files are available. In the current approach, the Trigger.bat utility is used to trigger the import operation in the target environment from the Event Studio Agent that the user runs in the source environment.
This utility is deployed in a database server (which is preferably owned by the IBM Cognos administration team).
The following screen shot shows the Trigger.bat utility files that are placed in a server location where a SQL Server Database is installed.(these files can be placed anywhere in the physical location of the server where the service account running the database server has access permissions).
Of the above files “GoDatawarehouse.bat” and “Gosales.bat” are the files created for this process. These files each represent two different applications. All other files are part of the Trigger.bat utility. The batch file content would be as shown below. The “GoDatawarehouse.bat” file will call the “Trigger.bat” file.
The Dispatcher URI of the Target Environment, user ID and password which has traverse permissions to IBM Cognos Administrator and the corresponding namespace and a trigger name are passed as parameters to the Trigger.bat through this batch file. GoDatwarehouse is the Trigger name mentioned in this batch file which is the name of the trigger used to setup trigger schedule for “Event Studio Import Agent”. This is explained in the upcoming section 7.5.6. To know more about Trigger.bat utility, please refer Appendix B.
STORED PROCEDURE CREATION TO RUN THE TRIGGER
The purpose of this stored procedure is to automate the batch file execution,. In order to accomplish this a stored Procedure is created in the Database. Below is an example of a Stored Procedure for Microsoft SQL Server 2005.
As shown in the screen shot, this stored procedure basically executes the “GoDatawarehouse.bat” in the provided location, and this batch file in turn would run the Trigger.bat utility with the supplied parameters. The Trigger.bat utility will trigger the required “Event Studio Import Agent” in the target environment that will run the export and import of the deployment. The batch files and stored procedures need to be created specifically for each of the application for their respective code deployment. The respective stored procedures can be referred to in the agents created for the corresponding applications. e.g. GoDatwarehouse, Gosales. The following conditions are required to leverage the stored procedure.
An IBM Cognos data source is created with the database containing the stored procedure as a source in the IBM Cognos administration page.
A package is created from this datasource with a “Stored Procedure” imported for each of the applications.
The IBM Cognos package is then published to IBM Cognos Connection.
EXPORT DEPLOYMENT STRATEGY
EXPORT CONTENT TASK CREATION
The content which needs to be exported to the target environment is done for the first time from the IBM Cognos Administration page to use the corresponding export task for the automation. The Event Studio agent can not be created until the export task exists, so an initial export must be configured. Make note of the name of the export in IBM Cognos Administration as it will be required in Event Studio
EVENT STUDIO AGENT CREATION-EXPORT
The Event Studio agent is designed in the source environment where the deployment is to be taken. Below are the steps required to build this agent.
The IBM Cognos Package published in the previous step is used as the Source package for the Event Studio Agent.
An always succeeding event is created in the first step of the event. This event is created to make sure as the tasks defined in the agent should be executed successfully without checking for any condition whenever the agent is run.
CREATING THE EXPORT DEPLOYMENT
Insert a “Run an export” task to the agent.
The export was created previously in the IBM Cognos Administration portal is used here. Select the appropriate export to include in the agent.
TRIGGERING THE IMPORT TASK
Insert an ‘Update a database’ task to the agent.
The package published and the corresponding stored procedure created in the Step 6.3 is configured in this task.
The data modification stored procedure will run the “Trigger.bat” utility on the database server which in turn triggers the import deployment agent in the target environment.
EMAIL NOTIFICATION ON SUCCESS
The “Send an email...” task is added to the agent to send an email notification for the successful completion of export task and successful trigger of import deployment in target environment.
The email body content and the recipients list are added as required notifying the successful completion of tasks. The recipients list can include IBM Cognos administrators and application architects who would run this agent as and when required for deployment.
EMAIL NOTIFICATION ON FAILURE
The “Send an email...” task is added to the agent to send an email notification if any of the tasks in this agent failed.
The email body content and the recipients list are added as required notifying of the failure of tasks. The recipients list can include IBM Cognos administrators and application architects who would run this agent as and when required for deployment.
The execution rule for this email task is defined via “Manage the task execution rules”.
The task execution rule for this task is configured to “When the agent or any of it’s tasks fail” and defined in such a way that this task will be executed only if the agent itself fails or any of its tasks fail.
When completed the agent should resemble the one shown below. There should be four tasks, one to export the deployment, one to execute the batch file, and then one to e-mail notification for either success or failure of the agent or any of the previous tasks.
IMPORT DEPLOYMENT STRATEGY
IMPORT CONTENT TASK CREATION
The content which needs to be imported into the target environment is done for the first time from the IBM Cognos administration page to use the corresponding import task for the automation. The Event Studio agent can not be created until the import task exists, so an initial import must be configured. Make note of the name of the import in IBM Cognos Administration as it will be required in Event Studio
EVENT STUDIO AGENT CREATION
The Agent is designed as follows in the target IBM Cognos BI environment to which the IBM Cognos content is to be deployed. Any IBM Cognos package can be used as a source package for this Event Studio agent since the stored procedures created earlier are not used in this agent. To maintain integrity, the package used for the Event Studio agent for the export task in the source IBM Cognos environment can be used here after publishing the same deployment in the target environment.
An always succeeding event is created in the first step of the agent. This event is created to make sure as the tasks defined in the agent should be executed successfully without checking for any condition whenever the agent is run. The agent further consists of three tasks after the always succeeding event.
IMPORT DEPLOYMENT
The Advanced task, “Run an import” is added in the agent.
This task requires that the user select a deployment to import. Choose the deployment that corresponds to the export run in the previous steps, that is also the import deployment that was configured in step 6.5.1.
EMAIL NOTIFICATION ON SUCCESS
The “Send an email” task is added to the agent to send an email notification for the successful completion of import task in the agent.
The email body content and the recipients list are added as required notifying of the successful completion of tasks. The recipients list can include IBM Cognos administrators and application architects who would run this agent when required for deployment.
EMAIL NOTIFICATION ON FAILURE
The “Send an email” task is added to the agent to send an email notification if any of the tasks in this agent fails.
The email body Content and the recipients list are added as required notifying the failure of tasks. The recipients list can include IBM Cognos administrators and application architects who would run this agent as and when required for deployment.
The execution rule for this email task is defined via “Manage the task execution rules”.
The task execution rule for this task is configured to “When the agent or any of it’s tasks fail” and defined in such a way that this task will be executed only if the agent itself fails or any of its tasks fail.
The Event Studio import agent should now look like.
SCHEDULE THE EVENT BASED ON TRIGGER
The Event Studio Import Agent needs to be scheduled based on Trigger. This well allow the agent to be launched by the trigger.bat utility. The Trigger name mentioned here as “GoDatwarehouse” is the Trigger name passed as the parameter to the IBM Cognos “Trigger.bat” Utility.(as shown in Figure:5.0).
BENEFITS
This one time activity highly reduces the manual effort involved by the IBM Cognos administrators in code migration process.
This approach provides flexibility for the IBM Cognos architects to perform the code deployment themselves by just running the Event Studio agent in the source IBM Cognos environment.
The architecture is defined in such a way that the deployment would be successful, even in case of Content Manager Fail-overs’ in any of the configured IBM cognos environments.
The emails triggered after the tasks completion provides the status of the deployment.
Usage of the above technique will remove the dependency of using other third party tools which are specifically used for IBM Cognos code migration by the developers and this provides full control of the environment to the IBM Cognos administrators.
CONCLUSION
This approach can be further enhanced by integrating with the audit reports and the history of code deployment performed by the users. This automated process will save time and provides the flexibility to the application users to migrate their artifacts on their own schedule.
Appendix
A. Cognos Administration and Security Guide: Chapter 18, Deployment
B. KB 1022042: How to fire a trigger using the Trigger.bat utility
Downloadable resources
Comments
Sign in or register to add and subscribe to comments.