In this section: |
Developer Studio allows local (stand-alone) development and development against a remote development. From the Explorers Projects folder, you can develop projects locally on your machine or against a remote WebFOCUS environment. From the WebFOCUS Environments folder of the Explorer, you develop directly against environments that are configured remotely.
In Developer Studio, you start building a reporting application as a Project consisting of different kinds of files. You can create the project as a stand-alone application in the development environment or as a web-based self-service application that you can deploy.
With a full Developer Studio installation, you can:
Stand-alone Project-based development and deployment requires installation of a Reporting Server on the same machine as Developer Studio. A WebFOCUS Client is also required for Project-based development. The files that you create for a local project reside in a subdirectory under APPROOT as described earlier. The Application Root directories (APPROOT directories) attribute must point to the same directory for Project-based development.
If you do not have a Reporting Server and the WebFOCUS Client on your development machine, for example if you have installed the Managed Reporting Developer edition of Developer Studio, your environment allows the last two capabilities.
For details, see the WebFOCUS Developer Studio Installation and Configuration manual.
Reference: |
Developer Studio supports two configurations for Project-based development:
Note: When configuring a WebFOCUS Environment, provide a full domain for the host name, including top-level domain name, second-level domain, and sub-domains as specified by your organization (for example, hostname.companyname.com). This format is recommended to ensure that requests are properly resolved and redirected. In this environment, the project files that you create reside in a subdirectory under the Application Root directory (APPROOT directory).
See the Developer Studio Installation and Configuration manual for information about other required components that you must install, such as Java SDK and a servlet engine. All required components are packaged with Developer Studio.
Use of a remote environment for Project-based development requires the following:
For more information on APPROOT, see the Developing Reporting Applications manual.
To create a new project:
For details, see the Developer Studio Installation and Configuration manual.
For Microsoft IIS or Apache Tomcat, configuration of the web server and/or Application server is performed automatically for you during installation of Developer Studio. For other web servers, manual configuration is necessary.
For details, see the Developer Studio Installation and Configuration manual.
For details, see the Developer Studio Installation and Configuration manual.
Sample projects are provided for editions that allow local/standalone development. When working against a remote WebFOCUS environment you will not see any sample projects by default.
For more information, see Creating a Reporting Application in the Creating Reporting Applications With Developer Studio manual.
While working in the Projects area and performing local project development, files refresh automatically when you are updating your application files without requiring a manual refresh.
Refresh in other areas of the product will occur when operations, such as Create or Delete, are performed. From the Window Options dialog, a time interval can be set to perform an automatic Refresh every number of minutes and this will apply to all active development environments.
Developer Studio provides the following scenarios for remote development:
To create a new application on a server platform:
For details, see the Developer Studio Installation and Configuration manual.
For details, see How to Add a WebFOCUS Environment.
If you have more than one available WebFOCUS environment, you can select which one to use for your Developer Studio projects.
If you want to add a WebFOCUS Environment first, see How to Add a WebFOCUS Environment.
The Environments List dialog box opens.
The current development environment appears in the Development environment field.
The Status column on the Environments List dialog box displays current information about each WebFOCUS environment. The status types are:
Failed to access the Web server
Object not found URL: http(s)://host_name:port/...
Indicates that the environment is not available or not configured properly. This occurs if the web server is not functioning or is unavailable. The environment icon is marked with a red "x" if it is unavailable.
The Data Servers feature gives you access to file resources on all Reporting Servers in your environment. Using Data Servers, you can create and manage metadata, stored procedures, HTML files, and WebFOCUS StyleSheets. You can also perform operations on GIF images and other files, such as FOCUS data sources. Data Servers has access to all the applications on your configured servers and gives you the ability to create and delete applications.
You can copy and paste files between applications on one server or between servers. Data Servers allows you to move files between servers on different operating systems, which is useful, for example, when upsizing an application from Windows to z/OS. You can also use Data Servers to access certain files that you wish to copy to a Managed Reporting domain, such as a procedure.
Note: When copying files between different areas, code changes may be required to allow procedures to run.
The Data Servers area can be hidden based on user privileges defined in the security database.
Applications in this area support subfolders.
When you are developing a Managed Reporting application, you are working with files that are controlled by the WebFOCUS Client and stored in a centralized location called the Managed Reporting Repository. The Managed Reporting Repository is stored in a database configured with WebFOCUS. There is no decentralized local development copy of this Repository or of Managed Reporting files. Regardless of whether the developer is using a web browser-based tool or Developer Studio tools, the process entails retrieving a copy of the files, making changes to the files, and saving the files back to the Repository.
All Managed Reporting developers work in a common repository simultaneously and move their application components to a common test environment. The Managed Reporting concept enables two or more developers to work on different parts of the application simultaneously, without affecting each other. However, when two or more developers are working on files in a single Domain, the responsibility is on the developers to coordinate their changes. For example, if two developers are working on the same report file at the same time, the last one saving the file overwrites any changes the first developer may have made. To avoid such issues, Source Control is available in the Managed Reporting area.
The applications visible depend on your user privileges. Users see their own applications and files that are published. Administrators see all files and folders.
Folders can have multiple levels of sub folders and are used to build your Managed Reporting applications. The option to create a New Folder can be restricted for specific users or groups of users and in this case this option will not be visible.
When a new folder is created, the Server property check box is not selected, and the drop-down list of Reporting Server nodes is disabled. The default server detected for your session is displayed in the list box. All reports and reporting objects in this folder will inherit the server setting shown in this list box.
The Application Path property check box is not selected by default. This means that requests will be processed by the Reporting Servers default search path. The servers search path is generally determined by the settings in its profile but can also be overridden by user and group profiles, depending on the platform.
For more information about server search path behavior, see the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.
To override the default search path behavior of the server for reports run from this folder or for a specific file, check the Application Path property. Select applications from the available area and add them to the selected area to customize the search path for the folder or file.
The Application Path property sends the APP PATH values command to the server, where values contains the applications added to the selected area. A supplied value overrides the servers default search path (it does not append to it). Domain properties are inherited by the reports under it and can be overridden at the report level.
The following table describes the available operations for folders when selecting the New option.
You can do the following:
Note:
The Explorer Toolbar contains buttons that are primarily used to change the display of items in your Explorer window. Depending upon your location in the Explorer, certain toolbar buttons may be inactive or unavailable. The following table describes the buttons on the Explorer toolbar while working in the Projects area.
Button |
Operation |
---|---|
|
Moves up one level in the hierarchical file structure. |
|
Toggles between the double pane Explorer view and the single right pane Explorer view. |
|
Displays properties of the selected item. |
|
Displays the current deployment scenario. Click the down arrow and select New Deploy Scenario to create a deployment scenario. Note: Developer Studio supplies a deployment scenario named Local Deploy, which it uses to prepare files to run on a local server. Do not modify or remove Local Deploy. You can set up a default scenario in the Deployment tab in the Properties dialog box of the project. For details, see Partitioning and Deploying Project Files in the Creating Reporting Applications With Developer Studio manual. |
|
Provides deployment options for the current scenario that allow you to either deploy, deploy and run, or run the current scenario. |
|
Displays available items in the path of the project. Note that this button is not available when you have selected the Deploy folder. |
|
Adds the selected item to a project. Note that this button is not available when you have selected the Deploy folder.
|
|
Removes the selected item from a project. |
|
This button is visible when you are at a project level. It launches the Edit Filters dialog box, where you can set filters for items you want to display in the selected project. If you add or remove filters, the project filter list will change. |
|
This button is visible when you are at the virtual folder level. It launches the Edit Filters dialog box, where you can set filters for items you want to display in the selected project. If you add or remove filters, the project filter list will change. Click the down arrow to display a list that shows available files and their properties. You can also filter folders in the list. |
|
Deletes the selected item from the hard drive. |
|
Displays items in the view as large icons, small icons, or in a list. It can also display the item details. |
|
Indicates that source control is enabled. See the Creating Reporting Applications With Developer Studio manual for more information. |
The WebFOCUS Environments toolbar accesses other WebFOCUS application development and deployment tools. This toolbar becomes active when you click a server or environment name under the WebFOCUS Environments area.
Button |
Operation |
---|---|
|
Moves up one level in the hierarchical file structure. |
|
Toggles between the double pane Explorer view and the single right pane Explorer view. |
|
Displays the Deferred Report Status Interface in a new browser window. This option is only available in Managed Reporting. |
|
Accesses the Security Center. Used to manage users and permissions applied to groups and resources. |
|
Accesses the Business Intelligence Portal (BI Portal). Use the BI Portal to build complete, modern websites. |
|
Launches the View Builder, where you can create and manage public views (general and custom) and group views. This option is only available in Managed Reporting if you have installed the Business Intelligence Dashboard. |
|
Accesses the Business Intelligence Dashboard, an HTML-based thin client that allows you to create a customized user interface for access to WebFOCUS Managed Reporting. Note that you must use the View Builder to customize the Dashboard. |
|
Accesses ReportCaster Explorer if ReportCaster is installed on the Reporting Server. For more information, see the ReportCaster manual. |
|
Accesses the ReportCaster Console if ReportCaster is installed on the Reporting Server. For more information, see the ReportCaster manual. |
|
Launches the Server Console for the selected Reporting Server, which you use to configure and manage Reporting Servers. Note that the Server Console is sometimes referred to as the Web Console. |
|
Launches the WebFOCUS Administration Console, which you use to administer the WebFOCUS Client and perform tasks, such as add remote Reporting Servers. |
|
Displays properties of the selected item. |
|
Deletes the selected item from the file system. |
|
Displays items in the view as large icons, small icons, or in a list which also displays item details. |
Note: Tools enabled in the Explorer toolbar are controlled by the Security Center.
WebFOCUS |