Hi,You have to fetch the languages with ConfigBuilder from your archive (only languages is possible), and then build a delivery with the missing language(s).This delivery should then be compiled as a normal delivery, and installed on your <ifs_home>.The missing language will be imported to the database and refreshed, and the language ddls for the client will be installed on your <ifs_home>.
Hi,I hope someone in ALE team can confirm this, but depending on the database used to create the delivery, the component will be Fresh Install, VersionUpToDate or an upgrade.
Hi,I looked at APPS10 documentation but could find type Cust there as well, and I can’t remember I have ever seen it. As explained in the documentation Trans type had a special handling in IFS Configuration Builder, but that tool is not used in IFS_Cloud. Also in the IFS Configuration Builder this information was shown in the tool, per component, but it was only informative.So you can use Cust as before.When running ifs_build with credentials given (if no credentials, creation of build home defaults to fresh install, creation of delivery defaults to VersionUpToDate), the logic is to connect to the database and check for the component and the version of the component. If the component doesn’t exist in the db, it will be a fresh install, calling cre scripts and the rest of the files.If component exist, the version will be matched against the version in the [<component>Upgrade] section and defined upg file will be called.Check the deploy.ini documentation about the [<component>
.\installer.cmd --values E:\SND\ifsroot\config\ifscloud-values.yaml --set action=fileexec --set dbInstaller.fileName=E:\SND\ifsroot\deliveries\build-home\database\_utils\prepare.sql --set dbInstaller.userName=SYS --set dbInstaller.password=aaaaaaaaa --set dbInstaller.connectRole=SYSDBAThe only change I have done to your example that I have changed the dbInstaller.sysPassword to dbInstaller.password. This is like the example in the documentation..\installer.cmd --values E:\SND\ifsroot\config\ifscloud-values.yaml --set action=dbinstaller --set dbInstaller.connectRole=SYSDBA This will run the prepare.sql as well, because in this scenario, installer will find that sysPassword is defined in you ifscloud-values.yaml and therefor will login as SYS and execute the file.The connectRole can be left out, because SYSDBA is the default for SYSI hope this explains how the commands are working.
Correction to above:According to documentation, in you example, the password should be sent as --set dbInstaller.password=aaaaaaaaanot as I wrote--set dbInstaller.Password=aaaaaaaaa
According to documentation, in you example, the password should be sent as --set dbInstaller.Password=aaaaaaaaanot--set dbInstaller.sysPassword=aaaaaaaaaIn your second example, when running action dbinstaller, the content of the delivery or build_home (depending on where installer.cmd was execute) is analyzed, and if prepare.sql exist in database\_utils folder, and if dbInstaller.sysPassword=aaaaaaaaa is sent, prepare.sql will be called run SYS/aaaaaaaaa (as SYSDBA), if the dbInstaller.sysPassword is given, otherwise the call to prepare.sql will be skipped and logged in the log as skipped
These files can be imported in IEE client to be able to do translations, same place where you tried the export.
Hi,The RWC, among some other files, are not imported and installed into the database by the installer in APPS10.The installer only imports the files needed for runtime.The RWC are not needed in the database, these are used when compiling the client code, and when the satellite assemblies for the languages are created.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.