Right-click the link and select Properties. Open the Package Explorer view, expand the MagicDraw project and edit the MAGIC_DRAW_INSTALL_DIRECTORY link: 3.1. Select projects you need and click Finish. The project list appears in the Projects box.
Copy the java project location to the Select archive file box or browse to the java projects and click Browse. In the Select an import source list, select General > Existing Projects into Workspace and click Next.
If you close theApplication Settingsor theCSS Settingsviews and need to access them again, go toWindow->Show View, and select the appropriate view.ĭebugging Java Code used in a J2EE Environmentĭebugging Java Code used in a. Note that a new MicroStrategy menu is added to the default Eclipse menu. The Web Customization Editor is launched with two views open- Application Settings and CSS Settings. Go to Window-> Open Perspective-> Other, select MicroStrategy Web Customization Editor and click OK. NET SDK installation-for example, D:\.NET\SDK\v2.0\Bin. NET SDK location needs a valid value if you chose. Browse to the JAR file for the Axis2 kernel-for example, D:\axis2\lib\axis2-kernel.jar. The Axis2 kernel jar file field is active if you chose Axis2 as the web services container. Refer to the MicroStrategy SDK Readme for the currently supported version of Axis 2. If you plan to convert MicroStrategy tasks to a web service using the Web Services Deployment Wizard and then generate a web services stub class for that web service using the Web Services Client Stubs Wizard, you must use the version of Axis 2 that is supported for the Web Services Client Stubs Wizard. Net or Axis2 (for J2EE).įor the Ant root directory, browse to the root folder for the Apache Ant installation-for example, D:\apache-ant-1.7.1.įor the Web Services Deployment Location, browse to the location where you want the files generated by the wizard to be saved.įor the Axis2 Location, browse to the root folder for the Axis2 installation-for example, D:\axis2. NET SDK.įor the Web Services Container, choose. Refer to the MicroStrategy SDK Readme for the supported versions of Axis2 and the.
These settings are determined by where you installed the software needed for Web Services when you set up the Web Customization Editor. J2EE: webserver /MicroStrategy/servlet/mstrWebĬlick the Web Services preference under MicroStrategy on the left and make the following settings on the right. NET: webserver /MicroStrategy/asp/Main.aspx In the MicroStrategy Web URL field under MicroStrategy location and URL settings, enter the URL for launching MicroStrategy Web. In the Application Root field under MicroStrategy location and URL settings, browse to the root folder where MicroStrategy Web is installed.
Launch the Preferences dialog from Window-> Preferences and do the following:Ĭlick the MicroStrategy preference on the left and make the following settings on the right. Navigate to the Eclipse installation folder, and double-click on eclipse.exe to launch Eclipse. The plug-in will be extracted to whichever subfolder exists in your version of Eclipse. In newer versions of Eclipse, the plug-in is extracted to the eclipse\dropins subfolder. In older versions of Eclipse, the plug-in is extracted to the eclipse\plugins subfolder. This extracts the JAR file, .webcustomization.jar, into the eclipse\dropins subfolder inside the Eclipse installation folder. Unzip and extract .webcustomization.zip to the eclipse subfolder inside your Eclipse installation folder.
If you have not already done so, download the latest MicroStrategy Web SDK zip file to your local machine.
This topic illustrates how to deploy and configure the Web Customization Editor. Once you have downloaded and installed Eclipse, you must deploy and configure the Web Configuration Editor.
Deploying and Configuring the Web Customization Editor