- #BUSINESS INTELLIGENCE FOR VISUAL STUDIO 2012 SOFTWARE#
- #BUSINESS INTELLIGENCE FOR VISUAL STUDIO 2012 PASSWORD#
- #BUSINESS INTELLIGENCE FOR VISUAL STUDIO 2012 WINDOWS#
■ Allows you to add a read-only user account to the Microsoft Dynamics AX 2012 database for processing cubes (you should specify a domain account whose password does not expire).
This step is required to enable AXADOMD data extensions to operate without the use of Kerberos ■ Adds the Business Connector (BC) proxy user as an administrator of the SSAS server. ■ Ensures that the SSAS server has all of the necessary prerequisites to host Microsoft Dynamics AX 2012 cubes. Running the configuration step should take you a few minutes. To do so, run the Configure Analysis Extensions step in the Microsoft Dynamics AX Setup wizard on the SSAS server that hosts Microsoft Dynamics AX 2012 cubes. This step configures a given SSAS server for the Microsoft Dynamics AX 2012 analytic components. You need to configure the clustering or Network Load Balancing (NLB) solution before you implement the Production system, you may want to implement a redundancy or load balancing infrastructure. However, if you are implementing these components in a If you are implementing the analytic components on a development or test instance, you might not implement a scale-out architecture. ■ The Enterprise Portal web client must be configured.
#BUSINESS INTELLIGENCE FOR VISUAL STUDIO 2012 WINDOWS#
■ The Microsoft Dynamics AX Windows client must be implemented, and the initialization checklist must be completed. ■ At least one AOS instance must be implemented. The following sections describe each step in further detail.īefore you implement the analytic components in the prebuilt BI solution, the following Microsoft Dynamics AX core components should be in place: Provision users so that they can access the analytic data. Implementing the prebuilt BI solution consists of the following steps:ĥ. If you have any customizations at higher levels, they are also displayed. If you examine the Visual Studio Projects node in the AOT, will see the default SSAS project that is included with Microsoft Dynamics AX 2012, as shown in Figure below. When you deploy a project by using the SQL Server Analysis Services Project Wizard, which is new in Microsoft Dynamics AX 2012, the wizard selects the project in the highest layer for deployment. ■ SSAS projects respect the version control capabilities offered by AOT-based artifacts. ■ You can import and export SSAS projects to and from different environments as part of a model (by using models or.
#BUSINESS INTELLIGENCE FOR VISUAL STUDIO 2012 SOFTWARE#
This means that an independent software vendor (ISV) or partner can distribute a customized version of an SSAS project that adds additional analytic components to the solution that is included in the SYS layer. ■ SSAS projects respect the layering concept.
This means that SSAS projects derive all of the benefits of being residents of AOT. In Microsoft Dynamics AX 2012, the default SQL Server Analysis Services (SSAS) project is aįirst- class citizen of the Application Object Tree (AOT), as are other SSAS projects that you create in the AOT.
Microsoft Dynamics AX 2012 simplifies the implementation of a BI solution, so that all Microsoft Dynamics AX 2012 partners and customers (regardless of whether they have access to BI specialists) can implement the prebuilt BI solution when they implement the ERP functionality. All of these factors contribute to postponing the BI implementation. Often, implementation of the BI solution involves engaging a different partner or consultants. Also, the skill set required to implement a BI solution is distinctly different from the skill set required to implement an ERP system. BI implementation is complex and involves the integration of many components. Needless to say, project fatigue sets in (and the budget gets exhausted), and subsequent phases are postponed or delayed. Traditionally, BI solutions are implemented during the second or third phase of an Enterprise Resource Planning (ERP) implementation project.
0 kommentar(er)
