I have imported metadata on IBM Metadata Asset Manager that contains over 15,000 tables distributed among 4 schemas. However, I do not require all of them to be shared to the repository. Trying to share all the tables is causing my server to (obviously and reasonably) choke up. Is there any way I can select specific tables from the different imported schemas in the metadata, to share to the repository?
This problem was only resolved when I created a new Import Area. Once the table are selected, only those are visible unless a new table is added to the directory.
Related
What is the correct approach to delete custom doctype in Frappe? How to migrate the same in other servers and also what about database tables? Do we need to manually drop them?
Currently for me the deleted doctype’s still persist in the server after bench migrate. Please can someone help me in this?
When you delete a custom doctype, it will just delete the entry from doctype table. Also, there is a doctype called Deleted Document. All the deleted doctypes will be tracked here automatically.
By default, Frappe doesn't drop the tables from database. If you are sure that you don't need that data, you can manually drop those changes.
In my experience you best don't bother with the tables in the database. Let Frappe keep track of this, don't interfere by dropping tables or altering tables.
Look at it like this:
If you are using a database system you don't bother what the database system does on the filesystem to organize itself.
If you are using Frappe you don't bother what Frappe does in the database system to organize itself.
When it comes to deploying your Doctypes on the next stage (QS, Production) you use "bench export-fixtures" to export and "bench migrate" to import your changes into your targeted Stage.
Don't create your own SQL-Scripts!
I am trying to create database like metamodel in IGC using Bundles which will be having Tables, Columns, Physical and logical models, Primary and Foreign Keys. How can I create relationship with Key and Columns using custom assets like we have existing one in IGC?
IGC allows you to extend the Catalog and introduce new types of Assets, where you can manage their structure and display. The management of such new Assets is via the supported IGC REST, and you may use the IGC REST Explorer to initially test and publish bundles and post details of such Assets. The default URL for the IGC REST Explorer is: https://YOURSERVER:9443/ibm/iis/igc-rest-explorer/
If you expand the section Bundles - you can use the action: post /bundles/ to create a new set of Assets - Terminal Applications. Use the attached bundle archive.
Additionally - you can use the action: post /bundles/assets to create the instances of such Assets. Copy the contents of the attached file.
I was wondering if there are any options to export entities / configuration from Jasper. As Jasper doesn’t have an option to disable data sources, I am considering the possibility of backing up / exporting selected entities from Jasper and then delete them.
Later I can use the backup to import the entities if required in future.
I am considering the following items.
Data source
Ad-hoc Views
Ad-hoc Reports
Basically, I want to backup everything under an organization.
I think from Jasperserver 6.3.0(maybe some earlier version) jasperadmin can export entire organization.
This is from the doc:
To export organizations:
Log in as an administrator that has access to the organizations you want to export. For example, to move an organization, you must log in as the administrator of the parent organization.
Select Manage > Organizations to display the hierarchy of organizations.
In the left-hand panel, right-click the organization you want to export and select Export from the context menu.
I'm new to Alfresco. What i'm trying to do is to upload a file through REST API in a folder that i have created using Alfresco Web Administration Interface. I have a few problems:
1) I can see a set of folders, but how are them managed by Alfresco? As far as i know, those folders doesn't really exists physically, they are virtual. How does Alfresco manage the folders structure and files?
2) I have seen many examples on the _REST API use to upload a file. Anyway, the destination is set by something like this
workspace://SpacesStore/aae3b33fd-23d4-4091-ae64-44a8e332091341
I can't understand: What exactly is a SpaceStore? And, does the last-part-code refers to a specific folder? How can i get those codes relative to the folder i see in the Alfresco Web Admin Interface?
1) I can see a set of folders, but how are them managed by Alfresco?
As far as i know, those folders doesn't really exists physically, they
are virtual. How does Alfresco manage the folders structure and files?
Alfresco is an implementation of the Java Content Repository (JCR), this means that all the contents are managed using a logic structure similar to a graph of nodes. Storing and manipolating content must be done using the repository API, that's why you don't see anything at a storage level.
Each content in Alfresco is a node connected to at least another node: the parent.
The storage of Alfresco is based on two components:
File system for storing binaries and search indexes
Database for storing the backup of metadata and associations
The way how Alfresco stores contents is not important for you because you typically want to access using the Alfresco API. You can create your own logic structure in the repository using any type of folders tree and content associations.
2) I have seen many examples on the _REST API use to upload a file.
Anyway, the destination is set by something like this
workspace://SpacesStore/aae3b33fd-23d4-4091-ae64-44a8e332091341 I
can't understand: What exactly is a SpaceStore? And, does the
last-part-code refers to a specific folder?
A repository typically consists of a set of JCR workspaces, the SpacesStore is one of the workspaces in Alfresco and it is the logic partition of contents in their latest version.
Alfresco also contains other workspaces:
userStore: contains person nodes
archiveStore: contains removed nodes
version2Store: contains the version history of nodes
How can i get those codes relative to the folder i see in the Alfresco
Web Admin Interface?
That code is the node reference that is the unique identifier for each node in the repository and as you can see it consists of three parts:
workspace: the store protocol
SpacesStore: the store identifier
uuid: the UUID related to the node
The store reference consists of the store protocol appended with the store identifier and it is the identifier of the workspace where the node lives. The UUID specify the content inside the workspace.
These node references are the ID for nodes and you can see all these informations using the Node Browser inside the Alfresco Explorer | Administration Console trying to navigate your repository starting from the Company Home.
Hope this helps.
I'm trying to figure out where does webistrano keep its custom recipes (I want to copy them), and I can't seem to locate them. I've scoured the installation folder on the server to no avail.
Does anyone know where they are kept?
They were stored in its backend database.
Recipes created inside the admin interface are stored in the database. The recipes table holds the information for the recipe and the revision to be executed on, include the actual code for the current version. The recipe_versions holds a complete copy of each version of the recipe.
The project types (templates) are created inside the repository at lib/webistrano/template/