Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

On Windows, folders and files cannot start begin or end with spaces. If it is donethis occurs, Windows endpoints cannot be usedwill be unable to function properly, and FlexDeploy on Windows will have may encounter similar issues. Most While most special characters work are supported on Linux, but they can cause failures on Windows are likely. Windows has protected names for files and folders like COM2 and CON. If you use a protected name Additionally, Windows reserves certain file and folder names (e.g., COM2, CON). Using one of these protected names as a folder name , this will also fail on Windows.You can open a support ticket if you find an issue with special characters or have any other issueswill result in failure on Windows.

Starting with FlexDeploy 9.0.0.3, the colon (:) character is handled differently in Folder or File name, if you use any files that contain : character in folder or file names. If your files contain a colon in Oracle BI, OAC, or OTBI projects, you should rediscover them with the inactivate checkbox checked. In "Inactivate Missing Files" checkbox selected. For other projects, the files and packages work the same as before, but and builds that contain those files created earlier than 9.0.0.3 need to be rebuilt before deploymentwill function as they did previously.

The items in the catalog contain metadata, differing for each project type.  If using source control for the project, the items are automatically discovered into the catalog. For some project types, the items are discoverable from the underlying source system (e.g. a development repository).  The files represent metadata only, as the referenced source file is pulled from source control or the source system during the build.

...