A Better Way to Uninstall Photo Media Universe Network 2.03 with Added Benefits. There is a much easier and safer way to uninstall Photo Media Universe Network 2.03 completely. A third party uninstaller can automatically help you uninstall any unwanted programs and completely remove all of its files and free up your hard disk space.
Skip to end of metadataGo to start of metadataProduct versions:
HANA 1.0
BI Platform and Information Design Tool 4.0
HANA 1.0
BI Platform and Information Design Tool 4.0
For years, the BusinessObjects products have been demonstrated with the eFashion sample data set. It came in the format of a Microsoft Access database on top of which a pre-built universe was running using an ODBC connection. From there, numerous sample reports or dashboards could be built and illustrate key features of the Semantic Layer and BI client tools.
This article presents the steps to set up the same data set within HANA and BI 4.0, therefore put together a demo environment for BI 4.0 on HANA.
This article presents the steps to set up the same data set within HANA and BI 4.0, therefore put together a demo environment for BI 4.0 on HANA.
Highlights of this sample
- the universe is a relational universe of the new format (.UNX) that was released with BI 4.0
- the data set does not contain the aggregate tables anymore, it has the master data tables and one fact table (SHOP_FACTS). The aggregates are defined by Analytic Views to be imported into HANA after the tables were loaded.
- the universe is still leveraging the aggregate_aware function to decide at runtime which aggregate to report off
- The files required for this project are available from here : http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/006b8dda-602e-2f10-7688-9a2283b76264
- Extract the archive file into a local folder accessible from HANA Studio and Information Design Tool
- From the local folder where you extracted the files, use an FTP client tool to copy the folder dataset/index into the work directory of your HANA instance on the HANA appliance. It would typically be /usr/sap/<SID>/HDB00/work.
- Open the HANA DB Studio and log on with the SYSTEM user to the HANA Instance you will work with
- From the navigator pane, expand the system and right click on 'Catalog' to select 'Import...'
- Specify the location on the HANA appliance where you copied the files, typically the work directory
- Use the following list of tables and click 'Add' :
EFASHION_TUTORIAL.ARTICLE_LOOKUP,EFASHION_TUTORIAL.ARTICLE_COLOR_LOOKUP,
EFASHION_TUTORIAL.CALENDAR_YEAR_LOOKUP,EFASHION_TUTORIAL.OUTLET_LOOKUP,
EFASHION_TUTORIAL.SHOP_FACTS - Select 'Catalog + Data' and set the number of parallel Threads to 4 (should not be higher than the number of cores on your HANA appliance)
- Click on Finish. The job should execute in a few seconds. From the navigator pane, right click on 'Catalog' and select 'Refresh'. The new schema 'EFASHION_TUTORIAL' should now appear.
Alternative method: if the steps below fail for some unknown reason, run the SQL statements below from an SQL Editor window. Before you execute it, you will need to update the path to the .ctl files in each 'IMPORT FROM' statement
- From the Quick Launch screen of HANA Studio, click on Import
- Select Information Modeler / Information Models
- Select the system you want to import the models into
- Browse to the folder where you copied the project files and select the 'R12' folder. Expand the efashion and tutorial package, and select the three attribute views and one analytic view that are listed. Add them to the selection and click Finish
- A new package 'efashion.tutorial' should now appear under the information models and contains three attribute views and one analytic view
- Select the views you just imported (CTRL+click for a multi selection), right click on the selection and select 'Activate'
- The activation process will take a few seconds and upon completion a 'Activation Successful' message should appear in the Deployment Log.
- Verify the activation process created the column views under the _SYS_BIC schema.
- The data is now imported and one analytic view active for consumption. You can now do some reporting on top that information model.
- Launch Information Design Tool
- File / Open Project...
- Browse to the local folder where you extracted the project files, click OK, then Finish
- You should now see a new project called 'efashion on HANA'
- Open and Edit the connection object 'efashion on HANA'. Edit the connection details to your HANA server : username, password, server host and port number.
- Click Finish, then save the object.
- You will now make this connection secured by publishing it to the BI 4.x system.
- Right click on the connection object and select 'Publish Connection to Repository'
- Enter your credentials to the BI 4.x system, click Connect, then Next and select a folder where the Connection object will be stored
- Open the Data Foundation object 'efashion on HANA.dfx' and click on the Connection pane
- Click on the Change Connection icon at the top left corner
- Select the secured connection (the one you just published to the repository)
- When prompted to update the tables qualifier and owner, click on No
- Save the data foundation object. The universe is now ready to be published to the repository.
- Before you publish it, you can test a few queries from the Queries pane. Use the example 'yearly sales revenue per line' or build your own.
- Right click on the Business Layer, and select Publish / To a repository...
- Perform an integrity check
- You should get a few errors and warnings that can be ignored. The isolated tables and missing primary keys on the aggregate tables are not real problems.
- Click Next, then select a folder in the repository for the universe and click Finish
- That is all ! The universe is ready for consumption.
Plug-ins are small software modules—with filename extensions such as .aex, .pbk, .pbg, and .8bi—that add functionality to an application. Effects in After Effects are implemented as plug-ins, as are some features for importing and working with certain file formats. The Photoshop Camera Raw plug-in, for example, provides After Effects with its ability to work with Camera Raw files.
You can obtain plug-ins for After Effects and other Adobeproducts from Adobe or other vendors. For specific instructionsfor installing a plug-in, see its documentation.
When After Effects starts, it loads plug-ins from several folder,including the Plug-ins folder. If a plug-in doesn’t come with aninstaller or with specific instructions for its installation, thenyou can usually install the plug-in by placing it in the Plug-insfolder.
By default, the Plug-ins folder is in the following location:
- (Windows) Program FilesAdobeAdobe After Effects <version>SupportFiles
- (Mac OS) Applications/Adobe After Effects <version>
Several plug-ins come with After Effects and are automaticallyinstalled in the Plug-ins folder.
Note:
When loading plug-ins, After Effects ignoresthe contents of folders with names that begin and end in parentheses;for example, the contents of the folder (archived_effects) are notloaded.
After Effects also loads plug-ins from a MediaCore folder, which is intended to hold plug-ins shared between After Effects and Premiere Pro. Some third-party plug-in installers install their plug-ins in this folder. In general, unless specifically instructed to do so, don’t install plug-ins in the MediaCore folder. If you install a plug-in in this folder that is not supported by one or more of the applications that read from this folder, you may encounter errors or other problems.
Note:
(Mac OS) Some third-party plug-in installers incorrectly installtheir plug-ins into the Mac OS X Package for After Effects. To revealthese plug-ins, Control-click the After Effects application iconin the Finder and choose Show Package Contents. You can then movethe plug-ins into the After Effects Plug-ins folder.
When exchanging After Effects projects between computer systems, make sure that the plug-ins that the project depends on are installed on both systems. Similarly, if you're rendering a composition with multiple computers on a network, make sure that all plug-ins used in the composition are installed on all rendering computers.
Note:
On Mac OS, press Command+Option+Shift+Help togenerate a list of all plug-ins loaded into After Effects (includingversion numbers). For information on using this command on Windowsor with a Macintosh keyboard that doesn't have a Help button, seeTodd Kopriva’s blog on the Adobe website.
After Effects comes with several third-party plug-ins.
Keylight installs its documentation in the plug-in’s subfolder inthe Plug-ins folder. For more information, see Keyingeffects, including Keylight.
Color Finesse installs its documentation in the plug-in’s subfolder in the Plug-ins folder. For more information, see Resources for Synthetic Aperture Color Finesse.
Documentation for ProEXR plug-ins is available in a PDF document on the fnord website. For more information, see About 3D Channel effects, including ProEXR effects.
CycoreFX HD is included in the installation of After Effects CC. There is 16-bpc support in all effects, and 32-bpc (float) support in the effects. ICycoreFX HD plug-ins have support for motion blur, lights, more controls, and options.
For more information, see Resources for Cycore FX (CC) effects.
Documentation for the mocha shape for After Effects (mocha shape AE) plug-in is available on the Imagineer website.
Note:
Unlike the similarly named mocha shape for After Effects (mochashape AE), Imagineer mocha-AE is not a plug-in; it is a separate,standalone planar tracker application. For more information, see Resourcesfor mocha for After Effects (mocha-AE).
Many plug-ins for After Effects are written in the C/C++ programming language using the After Effects SDK. Effect plug-ins written with C/C++ have the filename extension .aex. For information on developing plug-ins for After Effects with the C/C++ SDK, go to the After Effects Developer Center section of the Adobe website.
Kas Thomas provides a tutorial on the MacTech website that shows step by step how to write an After Effects plug-in.
To ask questions about writing plug-ins with the C/C++ SDK for After Effects, go to the After Effects SDK user-to-user forum.
For information on plug-ins available for After Effects, go to the After Effects plug-in page on the Adobe website and the Toolfarm website.
To find plug-ins, scripts, projects, and other useful items, go to the Adobe Add-ons page.
For other sources of plug-ins, see After Effects community resources on the Adobe website.
More like this
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
Legal Notices | Online Privacy Policy