fnLogProperties = function(name) {
			return {
				type: "sap.ui.component",
				name: name
			};
		}
Creates a new instance of a <code>Component</code> or returns the instance
of an existing <code>Component</code>.

If you want to look up an existing <code>Component</code> you can call
this function with a Component ID as parameter:
<pre>
  var oComponent = sap.ui.component(sComponentId);
</pre>

To create a new instance of a component you pass a component configuration
object into this function:
<pre>
  var oComponent = sap.ui.component({
    name: "my.Component",
    url: "my/component/location",
    id: "myCompId1"
  });
</pre>

@param {string|object} vConfig ID of an existing Component or the configuration object to create the Component
@param {string} vConfig.name Name of the Component to load, as a dot-separated name;
             Even when an alternative location is specified from which the manifest should be loaded (e.g.
             <code>vConfig.manifest</code> is set to a non-empty string), then the name specified in that
             manifest will be ignored and this name will be used instead to determine the module to be loaded.
@param {string} [vConfig.url] Alternative location from where to load the Component. If a <code>manifestUrl</code> is given, this URL specifies the location of the final component defined via that manifest, otherwise it specifies the location of the component defined via its name <code>vConfig.name</code>.
@param {object} [vConfig.componentData] Initial data of the Component, see {@link sap.ui.core.Component#getComponentData}
@param {string} [vConfig.id] sId of the new Component
@param {object} [vConfig.settings] Settings of the new Component
@param {string[]} [vConfig.activeTerminologies] List of active terminologies.
             The order of the given active terminologies is significant. The {@link module:sap/base/i18n/ResourceBundle ResourceBundle} API
             documentation describes the processing behavior in more detail.
             Please also have a look at this dev-guide chapter for general usage instructions: {@link topic:eba8d25a31ef416ead876e091e67824e Text Verticalization}.
@param {boolean} [vConfig.async] Indicates whether the Component creation should be done asynchronously; defaults to true when using the manifest property with a truthy value otherwise the default is false (experimental setting)
@param {object} [vConfig.asyncHints] @since 1.27.0 Hints for the asynchronous loading.
    <b>Beware:</b> This parameter is only used internally by the UI5 framework and compatibility cannot be guaranteed.
    The parameter must not be used in productive code, except in code delivered by the UI5 teams.
@param {string[]} [vConfig.asyncHints.libs] Libraries that should be (pre-)loaded before the Component (experimental setting)
@param {string[]} [vConfig.asyncHints.components] Components that should be (pre-)loaded before the Component (experimental setting)
@param {Promise|Promise[]} [vConfig.asyncHints.waitFor] @since 1.37.0 a <code>Promise</code> or and array of <code>Promise</code>s for which the Component instantiation should wait (experimental setting)
@param {boolean|string|object} [vConfig.manifest=undefined] @since 1.49.0 Controls when and from where to load the manifest for the Component.
             When set to any truthy value, the manifest will be loaded asynchronously by default and evaluated before the Component controller, if it is set to a falsy value
             other than <code>undefined</code>, the manifest will be loaded after the controller.
             A non-empty string value will be interpreted as the URL location from where to load the manifest.
             A non-null object value will be interpreted as manifest content.
             Setting this property to a value other than <code>undefined</code>, completely deactivates the properties
             <code>manifestUrl</code> and <code>manifestFirst</code>, no matter what their values are.
@param {string} [vConfig.manifestUrl] @since 1.33.0 Specifies the URL from where the manifest should be loaded from
             Using this property implies <code>vConfig.manifestFirst=true</code>.
             <br/><b>DEPRECATED since 1.49.0, use <code>vConfig.manifest=url</code> instead!</b>.
             Note that this property is ignored when <code>vConfig.manifest</code> has a value other than <code>undefined</code>.
@param {boolean} [vConfig.manifestFirst] @since 1.33.0 defines whether the manifest is loaded before or after the
             Component controller. Defaults to <code>sap.ui.getCore().getConfiguration().getManifestFirst()</code>
             <br/><b>DEPRECATED since 1.49.0, use <code>vConfig.manifest=true|false</code> instead!</b>
             Note that this property is ignored when <code>vConfig.manifest</code> has a value other than <code>undefined</code>.
@param {string} [vConfig.handleValidation=false] If set to <code>true</code> validation of the component is handled by the <code>Messaging</code>
@returns {sap.ui.core.Component|Promise} the Component instance or a Promise in case of asynchronous loading

@deprecated Since 1.56, use {@link sap.ui.core.Component.get Component.get} or {@link sap.ui.core.Component.create Component.create} instead.
  Note: {@link sap.ui.core.Component.create Component.create} does not support synchronous loading or the deprecated options <em>manifestFirst</em> and <em>manifestUrl</em>.
@public
@static
@since 1.15.0
@ui5-global-only